← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 2099651] [NEW] Attach volume doesn't work with SHELVED_OFFLOADED VM

 

Public bug reported:

When an instance with a volume is shelved (shelved_offloaded), the
availability zone (AZ) of the instance is not correctly handled when
attempting to attach the volume. The bug occurs because the AZ check is
not being performed properly when an instance does not have a pinned
availability zone.

1. I did create volume
$ openstack volume create test_volume --image 73d2c491-9970-476c-9fdf-751a60b07ed1 --size 20 --availability-zone az1

2. I did create instance
$ openstack server create test_instance --network e6addcac-5ea8-427b-94b5-1a9cf6767ad7 --volume test_volume --availability-zone az1 --flavor <some_flavor> 

3. I did shelve instance
$ openstack server shelve test_instance

4. I did create volume for attach
$ openstack volume create attach_volume --size 1 --type <type> --availability-zone az1

5. I did attach volume to shelved_offloaded instance
$ openstack server --os-compute-api-version='2.20' add volume test_instance attach_volume


Links:
- bug discussion at IRC (read from 18-00) https://meetings.opendev.org/irclogs/%23openstack-nova/%23openstack-nova.2025-02-19.log.html
- probably this changes broke function https://github.com/openstack/nova/commit/07a24dcef7ce6767b4b5bab0c8d3166cbe5b39c0

** Affects: nova
     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/2099651

Title:
  Attach volume doesn't work with SHELVED_OFFLOADED VM

Status in OpenStack Compute (nova):
  New

Bug description:
  When an instance with a volume is shelved (shelved_offloaded), the
  availability zone (AZ) of the instance is not correctly handled when
  attempting to attach the volume. The bug occurs because the AZ check
  is not being performed properly when an instance does not have a
  pinned availability zone.

  1. I did create volume
  $ openstack volume create test_volume --image 73d2c491-9970-476c-9fdf-751a60b07ed1 --size 20 --availability-zone az1

  2. I did create instance
  $ openstack server create test_instance --network e6addcac-5ea8-427b-94b5-1a9cf6767ad7 --volume test_volume --availability-zone az1 --flavor <some_flavor> 

  3. I did shelve instance
  $ openstack server shelve test_instance

  4. I did create volume for attach
  $ openstack volume create attach_volume --size 1 --type <type> --availability-zone az1

  5. I did attach volume to shelved_offloaded instance
  $ openstack server --os-compute-api-version='2.20' add volume test_instance attach_volume

  
  Links:
  - bug discussion at IRC (read from 18-00) https://meetings.opendev.org/irclogs/%23openstack-nova/%23openstack-nova.2025-02-19.log.html
  - probably this changes broke function https://github.com/openstack/nova/commit/07a24dcef7ce6767b4b5bab0c8d3166cbe5b39c0

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