Description of problem: An RHCOS VM has no payload device (for the ignition file) when running the VM as run-once - and the operating system gets stuck while booting. Version-Release number of selected component (if applicable): - RHV 4.4.0-0.33.master.el8ev - rhcos-44.81.202004250133-0-openstack - libvirt-6.0.0-17.module+el8.2.0+6257+0d066c28.x86_64 - vdsm-4.40.13-1.el8ev.x86_64 How reproducible: 100% Steps to Reproduce: 1. Create an RHCOS VM (make sure RHCOS configured under 'Edit > General > Operation System') 2. Start the VM as run-once and check the 'Ignition 2.3.0' checkbox under 'Initial Run'. Actual results: No payload device attached to the VM and the VM gets stuck while booting dumpxml result (empty): # virsh -r dumpxml <rhcos_vm> | sed -n '/ovirt-vm:vmPayload/,/\/ovirt-vm:vmPayload/p' Expected results: Payload device is attached to the VM and RHCOS is up and running dumpxml should result something like: # virsh -r dumpxml <rhcos_vm> | sed -n '/ovirt-vm:vmPayload/,/\/ovirt-vm:vmPayload/p' <ovirt-vm:vmPayload> <ovirt-vm:volId>config-2</ovirt-vm:volId> <ovirt-vm:file path="openstack/latest/meta_data.json">ewogICJhdmFpbGFiaWxpdHlfem9uZSIgOiAibm92YSIsCiAgImxhdW5jaF9pbmRleCIgOiAiMCIsCiAgIm1ldGEiIDogewogICAgInJvbGUiIDogInNlcnZlciIsCiAgICAiZHNtb2RlIiA6ICJsb2NhbCIsCiAgICAiZXNzZW50aWFsIiA6ICJmYWxzZSIKICB9LAogICJ1dWlkIiA6ICIxYTkwNTA3Zi03MzllLTRmNWMtOWI5NS1mNWEzODk4ZmJiZGIiCn0=</ovirt-vm:file> <ovirt-vm:file path="openstack/latest/user_data">eyJpZ25pdGlvbiI6eyJ2ZXJzaW9uIjoiMi4zLjAifX0=</ovirt-vm:file> </ovirt-vm:vmPayload> Additional info: The VM works as expected when 'Ignition 2.3.0' is checked under 'Edit > Initial Run' and the VM runs in standard mode (not run-once)
Created attachment 1682038 [details] RHCOS gets stuck on the boot
Verified with: - ovirt-engine-4.4.1.1-0.5.el8ev.noarch - libvirt-6.0.0-17.module+el8.2.0+6257+0d066c28.x86_64 - vdsm-4.40.18-1.el8ev.x86_64 Verification steps: 1. Create an RHCOS VM (rhcos-44.81.202004250133-0-openstack in my case) 2. Start the VM as run-once and check the 'Ignition 2.3.0' checkbox under 'Initial Run'. Result: - VM is up and running.
This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.