Bug: Red Hat CoreOS incorrect IBM Cloud OS Image label name

[sean-freeman]

Version

All

Platform:

ibmcloud

Install types impacted:

• ☑️ IPI (automated install with openshift-install)
• ☑️ UPI (semi-manual installation on customised infrastructure)

What happened?

Import of the QCOW2 OS Image file into an IBM Cloud OS Image using incorrect label name, causes technical anomolies (such as not importing to different IaaS Profiles) and will cause report/audit issues for Red Hat.

The OS Image label name used in the code is rhel-coreos-stable-amd64, but it should be red-coreos-amd64-byol. This in two places:

• The main Terraform Resource for creating the OS Image by openshift-install: openshift/installer/data/data/ibmcloud/network/image/main.tf#L44
• The related (and without GH Issues or README note to raise bugs) repository: openshift/release/ci-operator/step-registry/ipi/install/heterogeneous/ipi-install-heterogeneous-commands.sh#L312

The Web GUI shows this distinction in the clearest way:

What you expected to happen?

Correct OS Image label name should be used. If I recall correctly from 18 months ago, Red Hat initiated the request for red-coreos-amd64-byol OS Image label name for correct marketing name purposes and auditing purposes.

How to reproduce it (as minimally and precisely as possible)?

Run any installation to IBM Cloud, and the IBM Cloud OS Image will be imported incorrectly, as shown below in Web GUI (or CLI output):

Anything else we need to know?

When fixed, it should look like this in Web GUI or CLI output:

References

Previous commit where the OS Image label name was updated from Fedora CoreOS: https://github.com/openshift/installer/commit/dcac9ac21248c078925f0d9451c95c4686e37c5c

[prb112]

@cjschaef thoughts?

[sean-freeman]

@cjschaef bump?

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[sean-freeman]

/remove-lifecycle stale

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

[sean-freeman]

/lifecycle frozen