yahoo-eng-team team mailing list archive

[Russell Bryant <1273292@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

This is a spin-off of bug 1254890.  That bug was originally covering
failures for both timing out waiting for an instance to become ACTIVE,
as well as waiting for a volume to become in-use or available.

It seems valuable to split out the cases of waiting for volumes to
become in-use or available into its own bug.

message:"Details: Timed out waiting for thing" AND message:"to become"
AND (message:"in-use" OR message:"available")

** Affects: cinder
     Importance: Undecided
         Status: New

** Affects: nova
     Importance: Critical
         Status: Confirmed


** Tags: testing volumes

** Changed in: nova
       Status: New => Confirmed

** Also affects: cinder
   Importance: Undecided
       Status: New

** Changed in: nova
   Importance: Undecided => High

** Changed in: nova
   Importance: High => Critical

** Changed in: nova
    Milestone: None => icehouse-3

** Description changed:

  This is a spin-off of bug 1254890.  That bug was originally covering
  failures for both timing out waiting for an instance to become ACTIVE,
  as well as waiting for a volume to become in-use or available.
  
  It seems valuable to split out the cases of waiting for volumes to
- become in-use into its own bug.
+ become in-use or available into its own bug.
  
  message:"Details: Timed out waiting for thing" AND message:"to become"
- AND  message:"in-use"
+ AND (message:"in-use" OR message:"available")

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1273292

Title:
  "Timed out waiting for thing ... to become in-use" causes tempest-
  dsvm-* failures

Status in Cinder:
  New
Status in OpenStack Compute (Nova):
  Confirmed

Bug description:
  This is a spin-off of bug 1254890.  That bug was originally covering
  failures for both timing out waiting for an instance to become ACTIVE,
  as well as waiting for a volume to become in-use or available.

  It seems valuable to split out the cases of waiting for volumes to
  become in-use or available into its own bug.

  message:"Details: Timed out waiting for thing" AND message:"to become"
  AND (message:"in-use" OR message:"available")

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1273292/+subscriptions