OCP version: 4.11.0-0.nightly-2022-05-05-015322 Platform: RHV 4.5.0.6-0.7.el8ev IPI When installing OCP with "clone: false" specified for worker nodes in the install-config.yaml, the workers created are cloned (Clone/Independent flag in the RHV engine). Expected behavior: The created workers should not be cloned (Thin/Dependent flag in the RHV engine) How to reproduce: 1. Use Openshift installer to create install config: $ ./openshift-install create install-config --dir=resources 2. Specify clone as 'false' for the worker nodes in the install config: compute: platform: ovirt: clone: false 3. Install cluster $ ./openshift-install create cluster --dir=resources --log-level=debug 4. Check the Template flag of the worker node(s) in the RHV engine web console.
OCP version: 4.11.0-0.nightly-2022-05-18-053037 Platform: RHV 4.5.0.6-0.7.el8ev IPI Verification steps: 1. Used Openshift installer to create install config: $ ./openshift-install create install-config --dir=resources 2. Specified clone as 'false' for the worker nodes in the install config: compute: platform: ovirt: clone: false 3. Installed cluster $ ./openshift-install create cluster --dir=resources --log-level=debug 4. Checked the Template flag of the worker node(s) in the RHV engine web console. Expected result: Workers are not cloned (have (Thin/Dependent) flag) Actual results: Workers are not cloned (have (Thin/Dependent) flag)
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5069