[Openstack-qa-team] wait_for_server_status and Compute API

2012-06-18 Thread David Kranz
There are a few tempest tests, and many in the old kong suite that is still there, that wait for a server status that is something other than ACTIVE or VERIFY_RESIZE. These other states, such as BUILD or REBOOT, are transient so I don't understand why it is correct for code to poll for those

Re: [Openstack-qa-team] wait_for_server_status and Compute API

2012-06-18 Thread Daryl Walleck
I can verify that rescue is a non-race state. The transition is active to rescue on setting rescue, and rescue to active when leaving rescue. Original message Subject: Re: [Openstack-qa-team] wait_for_server_status and Compute API From: Jay Pipes jaypi...@gmail.com

Re: [Openstack-qa-team] wait_for_server_status and Compute API

2012-06-18 Thread David Kranz
On 6/18/2012 1:07 PM, Jay Pipes wrote: On 06/18/2012 12:49 PM, Daryl Walleck wrote: I can verify that rescue is a non-race state. The transition is active to rescue on setting rescue, and rescue to active when leaving rescue. I don't see a RESCUE state. I see a RESCUED state. Is that what you

Re: [Openstack-qa-team] wait_for_server_status and Compute API

2012-06-18 Thread Daryl Walleck
I'm not sure I agree with causing a failure based on what the user inputs to a function. I feel like this is something we should enforce through standards and not in code. Daryl On Jun 18, 2012, at 12:34 PM, David Kranz wrote: On 6/18/2012 1:07 PM, Jay Pipes wrote: On 06/18/2012 12:49 PM,