yahoo-eng-team team mailing list archive

[Lee Yarwood <1908075@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Description
===========
$subject, this is an odd little corner case but if an admin resets the state of an attached volume to available there are no checks within n-api stopping a user from attaching the volume to another instance, regardless of the original bdm record.

Steps to reproduce
==================
1. Attach a volume to an instance.
2. Reset the state of the volume to available.
3. Attach the volume to another instance.

Expected result
===============
The second request to attach a volume should be rejected by Nova until the attachment is removed.

Actual result
=============
The volume is attached to both instances in Nova but a single instance in Cinder.

Environment
===========
1. Exact version of OpenStack you are running. See the following
  list for all releases: http://docs.openstack.org/releases/

   master

2. Which hypervisor did you use?
   (For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)
   What's the version of that?

   N/A

2. Which storage type did you use?
   (For example: Ceph, LVM, GPFS, ...)
   What's the version of that?

   N/A

3. Which networking type did you use?
   (For example: nova-network, Neutron with OpenVSwitch, ...)

   N/A

Logs & Configs
==============

** Affects: nova
     Importance: Undecided
     Assignee: Lee Yarwood (lyarwood)
         Status: New


** Tags: volumes

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

Title:
  Nova allows a non-multiattach volume to be attached to multiple
  instances *if* its volume state is reset by an admin

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========
  $subject, this is an odd little corner case but if an admin resets the state of an attached volume to available there are no checks within n-api stopping a user from attaching the volume to another instance, regardless of the original bdm record.

  Steps to reproduce
  ==================
  1. Attach a volume to an instance.
  2. Reset the state of the volume to available.
  3. Attach the volume to another instance.

  Expected result
  ===============
  The second request to attach a volume should be rejected by Nova until the attachment is removed.

  Actual result
  =============
  The volume is attached to both instances in Nova but a single instance in Cinder.

  Environment
  ===========
  1. Exact version of OpenStack you are running. See the following
    list for all releases: http://docs.openstack.org/releases/

     master

  2. Which hypervisor did you use?
     (For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)
     What's the version of that?

     N/A

  2. Which storage type did you use?
     (For example: Ceph, LVM, GPFS, ...)
     What's the version of that?

     N/A

  3. Which networking type did you use?
     (For example: nova-network, Neutron with OpenVSwitch, ...)

     N/A

  Logs & Configs
  ==============

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