yahoo-eng-team team mailing list archive

[Wave Wang <1988325@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Description
===========
Using admin user to sign in. When a volume C is attached to instance A, if i try to attach it to another instance B, nova-api will
 raise an error "Invalid volume: Volume xxxx status must be available or downloading (HTTP 400) (Request-ID: xxxxx) (HTTP 400) (Request-ID: xxxxx)".At this time there is a deleted bdm record in nova for this failed attach.But then i delete instance B, the volume C (which is still attached to instance A) turned to available...making instance A can not use this volume.

Steps to reproduce
==================
* Using admin user to log in
* create an volume C
* attach volume C to instance A
* attach volume C to instance B, it failed and left a deleted bdm record in nova
* delete instance B, volume C alse become available and detached from instance A......

Expected result
===============
volume C should not become available and detached from instance A

Actual result
=============
volume C become available and detached from instance A

Environment
===========
rpm -qa|grep nova
openstack-nova-common-18.2.2-1.el7.noarch
openstack-nova-api-18.2.2-1.el7.noarch
python2-novaclient-11.0.0-1.el7.noarch
python-nova-18.2.2-1.el7.noarch

** Affects: nova
     Importance: Undecided
         Status: New

** Description changed:

  Description
  ===========
- Using admin user to sign in. When a volume C is attached to one instance A, if i try to attach it to another instance B, nova-api will 
-  raise an error "Invalid volume: Volume xxxx status must be available or downloading (HTTP 400) (Request-ID: xxxxx) (HTTP 400) (Request-ID: xxxxx)".At this time there is a deleted bdm record in nova for this failed attach.But then i delete instance B, the volume C (which is still attached to instance A) turned to available...making instance A can not use this volume.
+ Using admin user to sign in. When a volume C is attached to instance A, if i try to attach it to another instance B, nova-api will
+  raise an error "Invalid volume: Volume xxxx status must be available or downloading (HTTP 400) (Request-ID: xxxxx) (HTTP 400) (Request-ID: xxxxx)".At this time there is a deleted bdm record in nova for this failed attach.But then i delete instance B, the volume C (which is still attached to instance A) turned to available...making instance A can not use this volume.
  
  Steps to reproduce
  ==================
  * Using admin user to log in
  * create an volume C
  * attach volume C to instance A
  * attach volume C to instance B, it failed and left a deleted bdm record in nova
  * delete instance B, volume C alse become available and detached from instance A......
- 
  
  Expected result
  ===============
  volume C should not become available and detached from instance A
  
  Actual result
  =============
  volume C become available and detached from instance A
  
  Environment
  ===========
  rpm -qa|grep nova
  openstack-nova-common-18.2.2-1.el7.noarch
  openstack-nova-api-18.2.2-1.el7.noarch
  python2-novaclient-11.0.0-1.el7.noarch
  python-nova-18.2.2-1.el7.noarch

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

Title:
  Volume attach failed cause volume turn to available when delete the
  instance

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  Using admin user to sign in. When a volume C is attached to instance A, if i try to attach it to another instance B, nova-api will
   raise an error "Invalid volume: Volume xxxx status must be available or downloading (HTTP 400) (Request-ID: xxxxx) (HTTP 400) (Request-ID: xxxxx)".At this time there is a deleted bdm record in nova for this failed attach.But then i delete instance B, the volume C (which is still attached to instance A) turned to available...making instance A can not use this volume.

  Steps to reproduce
  ==================
  * Using admin user to log in
  * create an volume C
  * attach volume C to instance A
  * attach volume C to instance B, it failed and left a deleted bdm record in nova
  * delete instance B, volume C alse become available and detached from instance A......

  Expected result
  ===============
  volume C should not become available and detached from instance A

  Actual result
  =============
  volume C become available and detached from instance A

  Environment
  ===========
  rpm -qa|grep nova
  openstack-nova-common-18.2.2-1.el7.noarch
  openstack-nova-api-18.2.2-1.el7.noarch
  python2-novaclient-11.0.0-1.el7.noarch
  python-nova-18.2.2-1.el7.noarch

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