cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Tutkowski (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CLOUDSTACK-9374) Replace timer.sleep in host-delete method to correct timing problem
Date Tue, 03 May 2016 05:45:13 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-9374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mike Tutkowski reassigned CLOUDSTACK-9374:
------------------------------------------

    Assignee: Mike Tutkowski

> Replace timer.sleep in host-delete method to correct timing problem
> -------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9374
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9374
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: marvin
>    Affects Versions: 4.9.0
>         Environment: N/A
>            Reporter: Mike Tutkowski
>            Assignee: Mike Tutkowski
>             Fix For: 4.9.0
>
>
> In the base.py file, there is a Host class with a delete instance method.
> This method first attempts to transition the host into the maintenance resource state.
> The first step in this process is to transition the host into the prepare-for-maintenance
resource state.
> A while later, the host can be transitioned completely into the maintenance resource
state.
> In an attempt to wait for this transition to occur, the delete method has a timer.sleep(30)
call.
> The hope is that the host will have transitioned from the prepare-for-maintenance resource
state to the maintenance resource state within 30 seconds, but this does not always happen.
> We should correct this problem by putting in logic to query the management server for
the resource state of the host. If it's in the expected state, move on; else, sleep for a
bit and try again (up to a certain limit).



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

Mime
View raw message