prb112
commented
5 months ago @cjschaef thoughts?
Open sean-freeman opened 5 months ago
prb112
commented
5 months ago @cjschaef thoughts?
sean-freeman
commented
4 months ago @cjschaef bump?
openshift-bot
commented
1 month ago 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
commented
1 month ago /remove-lifecycle stale
Version
All
Platform:
ibmcloudInstall types impacted:
openshift-install)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 bered-coreos-amd64-byol. This in two places:openshift-install: openshift/installer/data/data/ibmcloud/network/image/main.tf#L44The 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-byolOS 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