Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Tue, 3 May 2016 05:45:13 +0000 (UTC)
From: "Mike Tutkowski (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12964530.1462254284000.94330.1462254313332@Atlassian.JIRA>
In-Reply-To: <JIRA.12964530.1462254284000@Atlassian.JIRA>
References: <JIRA.12964530.1462254284000@Atlassian.JIRA> <JIRA.12964530.1462254284365@arcas>
Subject: [jira] [Created] (CLOUDSTACK-9374) Replace timer.sleep in
 host-delete method to correct timing problem
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 03 May 2016 05:45:15 -0000

Mike Tutkowski created CLOUDSTACK-9374:
------------------------------------------

             Summary: 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
             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)