← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1302774] [NEW] Failed to detach volume because of volume not found error prevents vm teardown

 

Public bug reported:

When running the boto tests in the gate we get a periodic race on Cinder
volumes that can be seen as follows:

Attach the volume (vdh) - http://logs.openstack.org/29/84829/6/check
/check-dg-tempest-dsvm-full-
reexec/7e595ac/logs/screen-n-cpu.txt.gz?level=INFO#_2014-04-04_11_38_35_995

Detach the volume (vdh) - http://logs.openstack.org/29/84829/6/check
/check-dg-tempest-dsvm-full-
reexec/7e595ac/logs/screen-n-cpu.txt.gz?level=INFO#_2014-04-04_11_38_41_477

Stack trace horribly because the volume is not found -
http://logs.openstack.org/29/84829/6/check/check-dg-tempest-dsvm-full-
reexec/7e595ac/logs/screen-n-cpu.txt.gz?level=INFO#_2014-04-04_11_38_43_866

Stack trace horribly because we try again? -
http://logs.openstack.org/29/84829/6/check/check-dg-tempest-dsvm-full-
reexec/7e595ac/logs/screen-n-cpu.txt.gz?level=INFO#_2014-04-04_11_42_29_353

Because of this we end up with a volume in an undeletable state, and the
tests fail in making it go away (it remains marked in-use even though
the guest that was using it is gone) -
http://logs.openstack.org/29/84829/6/check/check-dg-tempest-dsvm-full-
reexec/7e595ac/console.html#_2014-04-04_11_42_47_940

Logstash for these results is:
http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiRGlza05vdEZvdW5kOiBObyBkaXNrIGF0XCIgQU5EIHRhZ3M6c2NyZWVuLW4tY3B1LnR4dCIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTM5NjYzNDM5MjIyOX0=

** Affects: cinder
     Importance: Undecided
         Status: New

** Affects: nova
     Importance: Undecided
         Status: New

** Affects: tempest
     Importance: Undecided
         Status: New

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

-- 
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/1302774

Title:
  Failed to detach volume because of volume not found error prevents vm
  teardown

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

Bug description:
  When running the boto tests in the gate we get a periodic race on
  Cinder volumes that can be seen as follows:

  Attach the volume (vdh) - http://logs.openstack.org/29/84829/6/check
  /check-dg-tempest-dsvm-full-
  reexec/7e595ac/logs/screen-n-cpu.txt.gz?level=INFO#_2014-04-04_11_38_35_995

  Detach the volume (vdh) - http://logs.openstack.org/29/84829/6/check
  /check-dg-tempest-dsvm-full-
  reexec/7e595ac/logs/screen-n-cpu.txt.gz?level=INFO#_2014-04-04_11_38_41_477

  Stack trace horribly because the volume is not found -
  http://logs.openstack.org/29/84829/6/check/check-dg-tempest-dsvm-full-
  reexec/7e595ac/logs/screen-n-cpu.txt.gz?level=INFO#_2014-04-04_11_38_43_866

  Stack trace horribly because we try again? -
  http://logs.openstack.org/29/84829/6/check/check-dg-tempest-dsvm-full-
  reexec/7e595ac/logs/screen-n-cpu.txt.gz?level=INFO#_2014-04-04_11_42_29_353

  Because of this we end up with a volume in an undeletable state, and
  the tests fail in making it go away (it remains marked in-use even
  though the guest that was using it is gone) -
  http://logs.openstack.org/29/84829/6/check/check-dg-tempest-dsvm-full-
  reexec/7e595ac/console.html#_2014-04-04_11_42_47_940

  Logstash for these results is:
  http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiRGlza05vdEZvdW5kOiBObyBkaXNrIGF0XCIgQU5EIHRhZ3M6c2NyZWVuLW4tY3B1LnR4dCIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTM5NjYzNDM5MjIyOX0=

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


Follow ups

References