yahoo-eng-team team mailing list archive

[Xi Wenhao <2099852@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Hi everyone,

When a virtual machine is created with a system disk and a data disk A,
and after creation, data disk A is unmounted, any attempt to mount
another data disk results in an error. The logs indicate that the target
device already exists.

The actual reason is that when a virtual machine is created with a data
disk, the CD-ROM occupies one device name. At this point, the device
mapping of the virtual machine is as follows:

- sda: root disk
- sdb: data disk
- sdc: cdrom

After unmounting data disk A (sdb), the remaining devices are 2 (sda and
sdc).

When trying to mount a new data disk, nova assigns the device name "sdc"
to the new disk. However, "sdc" is already occupied by the CD-ROM,
resulting in a mount failure.

The version of nova we used is 2024.1

** 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/2099852

Title:
  The CD-ROM occupying the device location prevents the data volume from
  being mounted.

Status in OpenStack Compute (nova):
  New

Bug description:
  Hi everyone,

  When a virtual machine is created with a system disk and a data disk
  A, and after creation, data disk A is unmounted, any attempt to mount
  another data disk results in an error. The logs indicate that the
  target device already exists.

  The actual reason is that when a virtual machine is created with a
  data disk, the CD-ROM occupies one device name. At this point, the
  device mapping of the virtual machine is as follows:

  - sda: root disk
  - sdb: data disk
  - sdc: cdrom

  After unmounting data disk A (sdb), the remaining devices are 2 (sda
  and sdc).

  When trying to mount a new data disk, nova assigns the device name
  "sdc" to the new disk. However, "sdc" is already occupied by the CD-
  ROM, resulting in a mount failure.

  The version of nova we used is 2024.1

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