Bug 1797496 - Add RHCOS os to osinfo - for compatability API between 4.3 to 4.4
Summary: Add RHCOS os to osinfo - for compatability API between 4.3 to 4.4
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.3.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ovirt-4.3.9
: 4.3.9
Assignee: Liran Rotenberg
QA Contact: Nisim Simsolo
Depends On: 1726907
TreeView+ depends on / blocked
Reported: 2020-02-03 09:56 UTC by Roy Golan
Modified: 2022-07-09 15:01 UTC (History)
7 users (show)

Fixed In Version: ovirt-engine-
Doc Type: Enhancement
Doc Text:
The current release adds support for Red Hat CoreOS (RHCOS), a single-purpose container operating system. This support enables you to create virtual machines that run RHCOS. These virtual machines are also backward compatible with RHV 4.3 clusters.
Clone Of:
Last Closed: 2020-04-02 16:32:17 UTC
oVirt Team: Virt
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-47487 0 None None None 2022-07-09 15:01:01 UTC
Red Hat Product Errata RHSA-2020:1308 0 None None None 2020-04-02 16:32:58 UTC
oVirt gerrit 106719 0 ovirt-engine-4.3 MERGED core+packaging: introduce rhcos OS type 2020-04-07 20:44:35 UTC

Description Roy Golan 2020-02-03 09:56:54 UTC
Description of problem:

The RHCOS support is bit different between 4.3 to 4.4.

4.3 - create a VM with a valid ignition file in initialization.custom_script
4.3 - create a VM with vm.os.type=rhcos_x86_64

To make it compatible between versions we need to add RHCOS OS to 4.3 and change usages to add os.type=rhcos_x86_64 i.e openshift/installer[1] and ovirt-terraform-provider [2]

[1] https://github.com/openshift/installer/blob/master/data/data/ovirt/masters/main.tf

Version-Release number of selected component (if applicable):
4.7.2 - when RHCOS support was added

How reproducible:

Steps to Reproduce:
1. Have an RHCOS VM with ignition in custom_script
2. Start VM 

Actual results:
RHCOS uses ignition in 4.3 but not in 4.4

Expected results:
To start ignition on both

Additional info:

both openshift/install and terraform-provider-ovirt are missing support for os property and issues will be opened against them as well.

Comment 2 Roy Golan 2020-02-05 11:26:17 UTC
We have a problem with the api now - how to run vm + and init, back compat way.

on 4.3  - vmService.start().useCloudInit(true).send()

on 4.4  - vmService.start().useIgnition(true).send()

I'm expecting vmService.start().Initialize(true) and let the engine pick the right type based on os.

Comment 3 Ryan Barry 2020-02-05 12:19:02 UTC
Sure, but no need to clear keywords or milestones just yet ;)

It's not a bug which FailedQA with no time to fix it.

Comment 7 Nisim Simsolo 2020-03-09 14:56:30 UTC
Verification builds:

Verification scenario:
1. Create new VM, Set OS type to RHCOS, attach rhcos qcow image to VM. 
2. From edit VM dialog -> initial run, check "use cloud-init/sysprep" checkbox, change VM hostname and add ignition script in custom script textbox.
3. Run VM.
4. Verify hostname change and ignition script configuration is applied on the VM.

Comment 11 errata-xmlrpc 2020-04-02 16:32:17 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.