Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
2.2.2
-
None
Description
Deploy a cluster using blueprint when all nodes are in HEARTBEAT_LOST state (e.g. nodes already registered with Ambari server once but than all were stopped prior posting the blueprint/cluster creation template to the server).
The blueprint and cluster creation succeeded and UI looked good with all the hosts in heartbeat-lost state.
Then start the agents one by one. Expected behaviour is that as soon as all required nodes are up Ambari to start scheduling tasks on the connected nodes to install the cluster.
However the hosts were stuck in host_status: UNKNOWN state and Ambari did not start scheduling any tasks to the connected hosts.
Attachments
Attachments
Issue Links
- is related to
-
AMBARI-16225 Blueprint Deployed Clusters Throw Exceptions On Startup
- Resolved
- links to