RosiKyu opened a new issue, #14514:
URL: https://github.com/apache/cloudstack/issues/14514

   ### problem
   
   The device id fixes on 4.22 and main reserve the device ids of the CD-ROMs 
and the config drive ISO for new data volumes. Volumes that already use one of 
these device ids (created on an earlier version) are not changed, as noted in 
both fixes. On q35 these VMs still fail to start with `XML error: target '...' 
duplicated` after the upgrade, until the volume is detached and attached again. 
These VMs could not start before the upgrade either (on 4.23.0.0 a config drive 
VM with a data volume on 5 also fails with vm.iso.max.count=2), so this is not 
a regression of the fixes.
   
   
   ### versions
   
   The versions of ACS, hypervisors, storage, network etc..The VMs already fail 
on the old version (4.22.1.0, 4.23.0.0). They still fail after the upgrade to a 
build that includes the fix:
   - 4.22.1.0 upgraded to the 4.22 build with the device id fix 
(4.22.2.0-SNAPSHOT): q35 config drive VM with a data volume on deviceid 4 
(`target 'sde' duplicated`).
   - 4.23.0.0 upgraded to main (24.0.0-SNAPSHOT): q35 VMs with a data volume on 
deviceid 4, with and without config drive (`target 'sde' duplicated`). A q35 
config drive VM with a data volume on deviceid 5 starts with vm.iso.max.count=1 
and fails with vm.iso.max.count=2 (`target 'sdf' duplicated`).
   
   **Environment:** 
   
   KVM on Oracle Linux 9, qemu-kvm 7.2.0, libvirt 9.0.0, machine type 
pc-q35-rhel9.2.0 (template settings rootDiskController=scsi, 
kvm.guest.os.machine.type=pc-q35-rhel9.2.0, UEFI=LEGACY), host.cdrom.max.count 
2. NFS primary storage.
   
   ### The steps to reproduce the bug
   
   1. On the earlier version (4.22.1.0 or 4.23.0.0), create an L2 network with 
DefaultL2NetworkOfferingConfigDrive.
   2. Deploy a q35 scsi VM on it (stopped) and attach 3 data volumes. The 3rd 
gets deviceid 4.
   3. Upgrade the management server and the KVM agents to the version with the 
fix.
   4. Start the VM. It fails with 530 "Unable to orchestrate the start of VM 
instance", and the management server log has "Unable to start VM on Host ... 
XML error: target 'sde' duplicated" for each host.
   5. Detach the volume on deviceid 4 and attach it again: it gets 5 (4.22) or 
6 (main), and the VM starts.
   
   
   ### What to do about it?
   
   **Expected:** after the upgrade, VMs with data volumes on the reserved 
device ids start without a manual detach and attach.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to