Description of problem:
On RHV 4.3.9 we have change the ignition handling and API, to recognize an ignition is passed to the VM we need to specify the os_type as RHCOS.
During the installation the installer creates a ovirt templates to be used by the nodes, so we need to:
1. create the template with os_type = "rchos".
2. update the version of terraform-provider-ovirt.
Also tracked in https://issues.redhat.com/browse/OCPRHV-58
Just a heads up:
We need this bug as verified as upstream request:
This pull request references Bugzilla bug 1821638, which is invalid:
expected dependent Bugzilla bug 1821151 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA instead
Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.
1. Deploy OCP4.5 using this install-config.yaml (some customizations have been applied): http://pastebin.test.redhat.com/868393
2. Check the OS type of template once created
OS type of both the template and VMs created from it is "Other OS". I checked that there is OS type "Red Hat Enterprise Linux CoreOS" available in my engine.
(In reply to Jan Zmeskal from comment #4)
> Tested with:
> Verification steps:
> 1. Deploy OCP4.5 using this install-config.yaml (some customizations have
> been applied): http://pastebin.test.redhat.com/868393
> 2. Check the OS type of template once created
> OS type of both the template and VMs created from it is "Other OS". I
> checked that there is OS type "Red Hat Enterprise Linux CoreOS" available in
> my engine.
Fix on 4.5 was merged on: https://github.com/openshift/installer/pull/3654
Added the fix to 4.4 as well
Verified with: openshift-install-linux-4.5.0-0.nightly-2020-05-27-071521
1. openshift install create cluster
2. Once the template is created, verify that its OS type is Red Hat Enterprise Linux Core OS
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.