yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1018253] Re: No error message prompt during attaching when mountpoint is occupied

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Balazs Gibizer <balazs.gibizer@xxxxxxxx>
Date: Thu, 23 Apr 2020 09:19:17 -0000
Reply-to: Bug 1018253 <1018253@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

I can reproduce the problem on a recent master in devstack with cirros
image.

I detached and re-attached the volume with --device /dev/vdb and in the
guest the block device visible as /dev/vdc . But the libvirt domain xml
shows /dev/vdb

    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='none' io='native'/>
      <source dev='/dev/sdb'/>
      <backingStore/>
      <target dev='vdb' bus='virtio'/>
      <serial>b2834555-b79b-4a08-9f9c-8d4186401b64</serial>
      <alias name='virtio-disk1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </disk>


$ lsblk
NAME    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
vda     253:0    0    1G  0 disk 
|-vda1  253:1    0 1015M  0 part /
`-vda15 253:15   0    8M  0 part 
vdc     253:32   0    1G  0 disk 


So this is not a Nova bug. Nova properly sets the target dev in the libvirt xml.

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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1018253

Title:
  No error message prompt during attaching when mountpoint is occupied

Status in OpenStack Dashboard (Horizon):
  New
Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Correct me if I am wrong.
  When we attach a volume to an instance at the mountpoint /dev/vdb, I expect that there should be a error message prompt in horizon if /dev/vdb is already occupied by, for example, another instance. Currently there is no error message prompt.

  How to create this bug:
  1, Launch one instance.
  2. Create a first volume and a second volume.
  3. Attach the first volume to the instance at the mountpoint /dev/vdb  and succeed.
  3. Attach the second volume to the same instance at the same mountpoint /dev/vdb.

  Expected output:
  A message should tell user that the mountpoint is occupied, not available or something.

  Actual output:
  No message shows. The second volume is still available.

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