[
https://issues.apache.org/jira/browse/AMBARI-10495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hari Sekhon updated AMBARI-10495:
---------------------------------
Description:
When trying to install the HDP 2.2.4.0 stack in Ambari 2.0 if it fails for any
reason (eg. AMBARI-10494) then the failing nodes are marked as failed but the
stack stays in the "installing" state indefinitely, even after restarting
ambari-server and all agents (I even did this simulatenously in parallel to
make sure one wasn't restoring the state to the other).
I've attached screenshots and the log file from one of the failed nodes to show
the full output.
This is completely blocking upgrade of the cluster and has been stuck in this
state since last week.
Hari Sekhon
http://www.linkedin.com/in/harisekhon
was:
When trying to install the HDP 2.2.4.0 stack in Ambari 2.0 if it fails for any
reason (eg. AMBARI-10494) then the failing nodes are marked as failed but the
stack stays in the "installing" state indefinitely, even after restarting
ambari-server and all agents (I even did this simulatenously in parallel to
make sure one wasn't restoring the state to the other).
I've attached screenshots and the log file from one of the failed nodes to show
the full output.
Hari Sekhon
http://www.linkedin.com/in/harisekhon
> Ambari 2.0 Stack deployment of HDP 2.2.4 stuck after failure
> ------------------------------------------------------------
>
> Key: AMBARI-10495
> URL: https://issues.apache.org/jira/browse/AMBARI-10495
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server, stacks
> Affects Versions: 2.0.0
> Environment: HDP 2.2.0 => HDP 2.2.4
> Reporter: Hari Sekhon
> Priority: Blocker
> Attachments: Ambari_2_installed_4_failed.png,
> Ambari_stuck_installing_stack.png
>
>
> When trying to install the HDP 2.2.4.0 stack in Ambari 2.0 if it fails for
> any reason (eg. AMBARI-10494) then the failing nodes are marked as failed but
> the stack stays in the "installing" state indefinitely, even after restarting
> ambari-server and all agents (I even did this simulatenously in parallel to
> make sure one wasn't restoring the state to the other).
> I've attached screenshots and the log file from one of the failed nodes to
> show the full output.
> This is completely blocking upgrade of the cluster and has been stuck in this
> state since last week.
> Hari Sekhon
> http://www.linkedin.com/in/harisekhon
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
