ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrii Tkach (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (AMBARI-13054) Pre-Req Endpoint Should Be Used For Determining Upgrade Button Visibility
Date Fri, 18 Sep 2015 09:58:04 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-13054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrii Tkach reopened AMBARI-13054:
-----------------------------------

Upgrade button not shown when version in OUT_OF_SYNC state

> 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.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)

Mime
View raw message