[
https://issues.apache.org/jira/browse/AMBARI-13054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940621#comment-14940621
]
Xi Wang commented on AMBARI-13054:
----------------------------------
Attached the third patch. All unit tests passed.
This patch is to fix the issue "I am unable to see the Upgrade button on a
cluster where several hosts are in Maintenance Mode and do not have the stack."
To "Remove the burden on the web client to determine when the button is shown,
the pre-req checks are the real gatekeeper. We basically must always show the
upgrade button; the web client should have no logic that hides it."
> Pre-Req Endpoint Should Be Used For Determining Upgrade Button Visibility
> -------------------------------------------------------------------------
>
> Key: AMBARI-13054
> URL: https://issues.apache.org/jira/browse/AMBARI-13054
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.1.2
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Critical
> Fix For: 2.1.2
>
> Attachments: AMBARI-13054-3.patch, AMBARI-13054.patch,
> AMBARI-13054_2.patch
>
>
> The web client currently uses a combination of host names, host_state, and
> stack versions to determine if an upgrade should be able to be performed for
> a given stack. If any of the hosts are missing the correct stack, then the
> option to upgrade to that stack is not permitted. The upgrade should be
> allowed, however, if the hosts which are missing the required stack are also
> in maintenance mode.
> The web client should begin using the prerequisite check API endpoint in
> order to calculate if the "Upgrade" button is to be visible for a specific
> stack. This allows the logic for calculating whether at stack is ready
> upgrade to remain on the Ambari Server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
