ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebastian Toader (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-16013) Host_status stuck in UNKNOWN status after blueprint deploy with host in heartbeat-lost
Date Thu, 21 Apr 2016 14:03:25 GMT
Sebastian Toader created AMBARI-16013:
-----------------------------------------

             Summary: Host_status stuck in UNKNOWN status after blueprint deploy with host
in heartbeat-lost
                 Key: AMBARI-16013
                 URL: https://issues.apache.org/jira/browse/AMBARI-16013
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.2.2
            Reporter: Sebastian Toader
            Assignee: Sebastian Toader
            Priority: Blocker
             Fix For: 2.2.2


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.



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

Mime
View raw message