You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Prachi Damle (JIRA)" <ji...@apache.org> on 2013/05/15 23:25:15 UTC

[jira] [Created] (CLOUDSTACK-2522) While processing agents behind on ping, we may fail to process a host that is already in 'Down' state

Prachi Damle created CLOUDSTACK-2522:
----------------------------------------

             Summary: While processing agents behind on ping, we may fail to process a host that is already in 'Down' state
                 Key: CLOUDSTACK-2522
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2522
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server
            Reporter: Prachi Damle
            Assignee: Prachi Damle
             Fix For: 4.2.0


>From the code I see that there is no transition for hosts from DOWN state with event PING
timeout. This causes an error when AgentMonitor does a delayed processing of the ping, for a host that has gone to DOWN  state. As a result the host state never gets updated in our DB.

Only when host state transition happens then is the mgmt_server_id made null by
HostDaoImpl:: Update code.

Since state transition never happens, mgmt_server_id remains non-null causing
reconnect of this host not to trigger.

I think this can be fixed by introducing state transition for DOWN state on
ping timeout.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira