Description of problem: In order to keep going with RHCOS support after rgolan's ignition support, let's add RHCOS to to the list also, so users can see whether guests are running this. It's ok to use the same virtual hardware as EL8. QEMU Guest Agent support is still being worked on, and is out of scope for this
when picking that RHCOS or FCOS from the list then we change the label to "Ignition v2" instead of cloud-init under "Initial Run", and hide all the non-supported cloud-init specific fields. Also the "custom script" label to be changed to "Ignition v2 configuration" or something similar.
Roy, can you look into this?
Ryan, Liran can you please clone to 4.3 as well?
I can clone, but, in general, we don't clone unless it's MODIFIED. I'd rather wait to for a solution which is closer than a custom runonce script first
*** Bug 1787232 has been marked as a duplicate of this bug. ***
Verified: ovirt-engine-4.4.1.7-0.3.el8ev vdsm-4.40.22-1.el8ev.x86_64 qemu-kvm-4.2.0-28.module+el8.2.1+7211+16dfe810.x86_64 libvirt-daemon-6.0.0-25.module+el8.2.1+7154+47ffd890.x86_64 Verification scenario: Polarion test plan added to bugzilla external trackers.
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 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.