yahoo-eng-team team mailing list archive

[Prateek Arora <parora@xxxxxxxxxx>]

I tried reproducing this

Here are my observations

[stack@controller devstack]$ nova suspend test
[stack@controller devstack]$ nova list
+--------------------------------------+------+-----------+------------+-------------+-------------------------------------------------------+
| ID                                   | Name | Status    | Task State | Power State | Networks                                              |
+--------------------------------------+------+-----------+------------+-------------+-------------------------------------------------------+
| a3e5e950-a51f-483a-ac48-85203bdb0bc9 | test | SUSPENDED | -          | Shutdown    | private=10.0.0.3, 2001:db8:8000:0:f816:3eff:fe0b:f50c |
+--------------------------------------+------+-----------+------------+-------------+-------------------------------------------------------+
[stack@controller devstack]$ nova resume test && nova volume-detach a3e5e950-a51f-483a-ac48-85203bdb0bc9 29dd9434-7559-404b-9c61-9d943936c2bf
ERROR (Conflict): Cannot 'detach_volume' instance a3e5e950-a51f-483a-ac48-85203bdb0bc9 while it is in vm_state suspended (HTTP 409) (Request-ID: req-8049116f-3e4c-476e-a475-9e67c874e65f)


As you can see that in this case the detach_volume did not go through because of the state suspended.

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

** Changed in: nova
     Assignee: Prateek Arora (parora) => (unassigned)

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

Title:
  detach volume just then starting instance success but not in the
  instance， rbd backend

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  1、Version
  root@controller:~# dpkg -l | grep nova
  ii  nova-api                            1:2015.1.0-0ubuntu1~cloud0            all          OpenStack Compute - API frontend
  ii  nova-cert                           1:2015.1.0-0ubuntu1~cloud0            all          OpenStack Compute - certificate management
  ii  nova-common                         1:2015.1.0-0ubuntu1~cloud0            all          OpenStack Compute - common files
  ii  nova-conductor                      1:2015.1.0-0ubuntu1~cloud0            all          OpenStack Compute - conductor service
  ii  nova-consoleauth                    1:2015.1.0-0ubuntu1~cloud0            all          OpenStack Compute - Console Authenticator
  ii  nova-novncproxy                     1:2015.1.0-0ubuntu1~cloud0            all          OpenStack Compute - NoVNC proxy
  ii  nova-scheduler                      1:2015.1.0-0ubuntu1~cloud0            all          OpenStack Compute - virtual machine scheduler
  ii  python-nova                         1:2015.1.0-0ubuntu1~cloud0            all          OpenStack Compute Python libraries
  ii  python-novaclient                   1:2.22.0-0ubuntu1~cloud0              all          client library for OpenStack Compute API

  vms / glance / volume backend storage all use ceph rbd

  
  2、Reproduce steps:
  a) Boot an instance
  b) attach an volume to the instance
  c) shut off the instance
  d) start the instance and detach the volume quickly until return success
  e) login the instance find the  volume of vdb is still exsit and can be used.
  f) show the volume status have been from in-used to avaiable

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