[AMBARI-21832] Reject PATCH VDFs with Services that are not Included in the Cluster

• Type: Task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 2.6.0
• Component/s: ambari-server
• Assignee: Dmitry Lysnichenko
• Reporter: Dmitry Lysnichenko
• Created: 28/Aug/17 16:01
• Updated: 04/Sep/17 17:15
• Resolved: 04/Sep/17 16:36

Description

Currently there is an odd scenario which can occur when patch repositories are registered which have services not yet installed. Consider the following scenario:

• Install ZooKeeper, Storm on HDP 2.6.0.0-1234
• Register/patch a PATCH VDF for Storm and Accumulo for 2.6.0.1-9999
• Install Accumulo

Which version does Accumulo use - the STANDARD repository or the PATCH? If the PATCH repository is chosen, this will now prevent reversion of the patch since there's no prior version for Accumulo to revert back to.

If Accumulo uses the STANDARD repo, then there needs to be a lot of design and UX flow work provided to indicate that a PATCH which was previously applied can be re-applied for the new service. This also causes problems for patch reversion since now there would be two upgrades which need to be reverted to "get rid" of the patch.

For the timeframe for Ambari 2.6, we should reject VDFs that include services which are not installed. This will prevent the problem.

Issue Links

• links to: review_request_