Bug 1726907

Summary:	[RFE] Add RHCOS to the list of operating systems
Product:	[oVirt] ovirt-engine	Reporter:	Ryan Barry <rbarry>
Component:	Backend.Core	Assignee:	Liran Rotenberg <lrotenbe>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nisim Simsolo <nsimsolo>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	future	CC:	bugs, davidmalger, lrotenbe, michal.skrivanek, mtessun, nsimsolo, rgolan, sgoodman
Target Milestone:	ovirt-4.4.0	Keywords:	FutureFeature, Rebase
Target Release:	---	Flags:	rbarry: ovirt-4.4? pm-rhel: planning_ack? rbarry: devel_ack+ pm-rhel: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhv-4.4.0-29	Doc Type:	Enhancement
Doc Text:	With this update, you can select Red Hat CoreOS (RHCOS) as the operating system for a virtual machine. When you do so, the initialization type is set to `ignition`. RHCOS uses ignition to initialize the virtual machine, differentiating it from RHEL.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-08-05 06:10:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1780022
Bug Blocks:	1797496

Description Ryan Barry 2019-07-04 04:09:37 UTC

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

Comment 1 Michal Skrivanek 2019-07-15 09:14:47 UTC

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.

Comment 2 Sandro Bonazzola 2019-11-08 16:06:53 UTC

Roy, can you look into this?

Comment 3 Roy Golan 2019-11-19 09:38:44 UTC

Ryan, Liran can you please clone to 4.3 as well?

Comment 4 Ryan Barry 2019-11-19 12:58:38 UTC

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

Comment 7 Liran Rotenberg 2020-01-08 16:18:22 UTC

*** Bug 1787232 has been marked as a duplicate of this bug. ***

Comment 10 Nisim Simsolo 2020-07-09 07:18:10 UTC

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.

Comment 11 Sandro Bonazzola 2020-08-05 06:10:10 UTC

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.