[
https://issues.apache.org/jira/browse/AMBARI-20401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905776#comment-15905776
]
Jonathan Hurley edited comment on AMBARI-20401 at 3/10/17 10:08 PM:
--------------------------------------------------------------------
- There is a bug deep in the ambari orchestration logic which causes a request
to hang in a {{PENDING}} state if the stage numbers are not directly sequential
(ie 1, 2, 3 vs 1, 3)
- HOU is exposing this bug by trying to schedule a stage with no tasks (which
is wrong anyway)
It's way to dangerous to fix the first problem. The 2nd problem is now fixed
and I'm putting it up for review. Therefore, I think this bug should remain
scoped for 2.5.0 and I can open a new bug for 2.5.1 for the deeper issue.
was (Author: jonathan.hurley):
- There is a bug deep in the ambari orchestration logic which causes a request
to hang in a {{PENDING}} state if the stage numbers are not directly sequential
(ie 1, 2, 3 vs 1, 3)
- HOU is exposing this bug by trying to schedule a stage with no tasks (which
is wrong anyway)
It's way to dangerous to fix the first problem. The 2nd problem is now fixed
and I'm putting it up for review. Therefore, I think this bug should remain
scoped for 2.5.0.1 and I can open a new bug for 2.5.1 for the deeper issue.
> 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
>
>
> # 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...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
