kladderadeng opened a new issue, #10588: URL: https://github.com/apache/cloudstack/issues/10588
### problem We killed a bunch of our VMs due to this and I am pretty sure that this behavior cannot be intended, so I post it as a bug. I hope this is the correct way. We created a bunch of (Windows) VM Instances by uploading the Windows ISO file, setting the OS Type to Windows Server 2022 and then creating instances based on that ISO (create a new instance, boot the ISO, install Windows...). After the installation we usually disconnect the ISO from the instance. Now to test various OS types, we changed the OS type on the ISO file and found out that all VMs that originated from that ISO got their OS type changed too. This lead to all the affected VMs to boot into a BSOD (Bluescreen) and we could not fix them, so we had to recreate those instances from scratch. It is a test environment, so no harm was done. ### versions OS Ubuntu 24.04 Apache Cloudstack 4.20.0.0 installed via the ACS Quickstart guide, so not compiled from source here! Hypervisor KVM QEMU emulator version 8.2.2 Libvirtd v 10.0.0 ### The steps to reproduce the bug 1. Upload a ISO (Windows Server 2022 Evaluation in our case) and set the OS Type to Windows Server 2022 2. Create a new instance based on that ISO and turn it on, install Windows etc. 3. Disconnect the ISO from the Instance 4. Create as many Instances that way as you want 5. Go back to the ISO Image and change the OS Type to for example Other PV 64 Bit 6. In the ISO Image click on Instances to see which Instances are connected to this ISO. If you disconnected the ISO after the Instance creation / Windows installation, this list will be empty. No visible connection to an instance exists. 7. Check your instances and observe that the OS type changed for all of them from Windows Server 2022 to Other PV 64 Bit 8. You can repeat steps 5-6 as often as you want, the OS type of the instances that do not seem to have any connection to the ISO are always changing. ### What to do about it? I do not know. I suspect that there is a reference in the Database somewhere telling ACS that all instances that where installed from a particular ISO / Image still get the OS Type passed down. In my point of view, an ISO Image should never have any reference to an Instance when it is not connected anymore. And it for sure should not affect the OS Type of an instance when I change the OS type of an ISO Image. The OS Type of a Instance should only be changed when changing it on the instance. The way it behaves currently is not obvious, unpredictable (you do not know which instances will be affected if you have hundreds) and dangerous if you have production workload. The big issue here is, that with the change of the OS type from an ISO, you can basically kill all your VMs at once and there is no warning / nothing you can do about it. -- 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: commits-unsubscr...@cloudstack.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
