ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-20401) HOU wizard wrongly shows hosts with only client components at the start of 'Upgrade Hosts' group
Date Sat, 11 Mar 2017 01:26:04 GMT

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

Jonathan Hurley updated AMBARI-20401:
-------------------------------------
    Description: 
# Deploy HDP-2.5.3 cluster with Ambari-2.5 (cluster topology is: 2 hosts with only masters,
2 hosts with only slaves, 1 host with only clients)
# Issued below call to start Host Ordered Upgrade to HDP-2.5.4 (note that host named 'bugbash-cluster-2-2.openstacklocal'
- third in the list has only client components)

In the HOU wizard in Ambari web UI, when the upgrade reaches 'Upgrade All Hosts' group, there
is already an entry for 'Stop on bugbash-cluster-2-2.openstacklocal'

Looks like the issue is that since host bugbash-cluster-2-2.openstacklocal does not have any
master/slave components it is already considered that components are stopped on this host
and the entry shows up in wizard.

Likewise From API, I checked that the Upgrade item appears as COMPLETED, even though earlier
Upgrades items are still Pending.

Thanks to [~shavi71] for finding this...

  was:
# Deploy HDP-2.5.3 cluster with Ambari-2.5.0.1 (cluster topology is: 2 hosts with only masters,
2 hosts with only slaves, 1 host with only clients)
# Issued below call to start Host Ordered Upgrade to HDP-2.5.4 (note that host named 'bugbash-cluster-2-2.openstacklocal'
- third in the list has only client components)

In the HOU wizard in Ambari web UI, when the upgrade reaches 'Upgrade All Hosts' group, there
is already an entry for 'Stop on bugbash-cluster-2-2.openstacklocal'

Looks like the issue is that since host bugbash-cluster-2-2.openstacklocal does not have any
master/slave components it is already considered that components are stopped on this host
and the entry shows up in wizard.

Likewise From API, I checked that the Upgrade item appears as COMPLETED, even though earlier
Upgrades items are still Pending.

Thanks to [~shavi71] for finding this...


> HOU wizard wrongly shows hosts with only client components at the start of 'Upgrade Hosts'
group
> ------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-20401
>                 URL: https://issues.apache.org/jira/browse/AMBARI-20401
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-20401.patch
>
>
> # Deploy HDP-2.5.3 cluster with Ambari-2.5 (cluster topology is: 2 hosts with only masters,
2 hosts with only slaves, 1 host with only clients)
> # Issued below call to start Host Ordered Upgrade to HDP-2.5.4 (note that host named
'bugbash-cluster-2-2.openstacklocal' - third in the list has only client components)
> In the HOU wizard in Ambari web UI, when the upgrade reaches 'Upgrade All Hosts' group,
there is already an entry for 'Stop on bugbash-cluster-2-2.openstacklocal'
> Looks like the issue is that since host bugbash-cluster-2-2.openstacklocal does not have
any master/slave components it is already considered that components are stopped on this host
and the entry shows up in wizard.
> Likewise From API, I checked that the Upgrade item appears as COMPLETED, even though
earlier Upgrades items are still Pending.
> Thanks to [~shavi71] for finding this...



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message