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] [Created] (AMBARI-13563) Upgrade: UI should determine the ongoing upgrade type based on Upgrade/upgrade_type from the API
Date Mon, 26 Oct 2015 16:41:27 GMT
Andrii Tkach created AMBARI-13563:
-------------------------------------

             Summary: Upgrade: UI should determine the ongoing upgrade type based on Upgrade/upgrade_type
from the API
                 Key: AMBARI-13563
                 URL: https://issues.apache.org/jira/browse/AMBARI-13563
             Project: Ambari
          Issue Type: Task
          Components: ambari-web
    Affects Versions: 2.1.3
            Reporter: Andrii Tkach
            Assignee: Andrii Tkach
            Priority: Critical
             Fix For: 2.1.3


Currently, we are using localDB/persist to rely on what the upgrade type (ROLLING vs NON_ROLLING)
is. This should be changed now that GET on the upgrade endpoint provides this info, since
relying on localDB/persist can be unreliable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message