update RHCOS 4.13 bootimage metadata

[mike-nguyen]

These changes will update the RHCOS 4.13 boot image metadata in the installer.

This change was generated using:

plume cosa2stream --target data/data/coreos/rhcos.json --distro rhcos --no-signatures --url https://rhcos.mirror.openshift.com/art/storage/prod/streams x86_64=413.92.202302171914-0 aarch64=413.92.202302171914-0 s390x=413.92.202302171914-0 ppc64le=413.92.202302171914-0

[mike-nguyen]

/retest

[osherdp]

don't mind me :)
/test e2e-metal-assisted

[mike-nguyen]

/retest-required

[jcpowermac]

/test e2e-vsphere-ovn
/test e2e-vsphere-zones

[jcpowermac]

/test e2e-vsphere-upi-zones

[mike-nguyen]

Bumped the boot images to 413.92.202303011445-0. The s390x secure execution artifact is now a part of the boot images.

[sdodson]

While rpm-ostree is awesome and it can probably apply an 8.6 ostree atop 9.2 boot image I'm not sure all of the stack works in that way right now. This PR really needs to be used in conjunction with openshift/machine-config-operator#.

What I've been doing is using cluster bot to build a release payload with both of those and using that. FWIW, that's how I've been producing the release image that I mirror to quay.io/sdodsonrht/rhcos9.2 periodically.

[cgwalters]

I think we can and should do this now.
/retest

[cgwalters]

Can someone from the installer team edit this PR to lift the "WIP"? Mike is out right now I think. Also, add a /approve please!

[cgwalters]

Alternatively, I can just make a new PR with these changes. We'll definitely be bumping again, but I am not aware of a particular reason to respin new bootimages at this time either.
If we hit issues with this PR I'll make a new one.

[jcpowermac]

/retitle update RHCOS 4.13 bootimage metadata

[cgwalters]

/lgtm
/hold
for some manual verification pre-merge - specifically the sanity check is that in e.g. the MCD logs we see that we're booted from rhel9 to rhel9.

[r4f4]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: r4f4

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• data/data/coreos/OWNERS [r4f4]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sdodson]

for some manual verification pre-merge - specifically the sanity check is that in e.g. the MCD logs we see that we're booted from rhel9 to rhel9.

I'd performed a few installs using cluster-bot builds from this PR and the other one together and I was pretty sure we were starting from a 9.2 boot image, but definitely worth checking again. Feel free to unhold whenever you'd like or we can sync up in the morning.

edit: But those were all while we were still on release-4.13, would be good to sanity check on master branch.

[cgwalters]

Yep, LGTM in this log from the e2e-aws-ovn job in this PR

Deployments:
* ostree-unverified-registry:registry.build01.ci.openshift.org/ci-op-ljz54p1j/stable@sha256:cd299b2bf3cc98fb70907f152b4281633064fe33527b5d6a42ddc418ff00eec1
                   Digest: sha256:cd299b2bf3cc98fb70907f152b4281633064fe33527b5d6a42ddc418ff00eec1
                  Version: 413.92.202303061740-0 (2023-03-08T23:50:12Z)

  0cfcd128dac3455bfed389e41f8a2274adaddbbed92ebb808a311c67b9bc9ec1
                  Version: 413.92.202303011445-0 (2023-03-01T14:48:28Z)

/hold cancel

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 44b1b0b and 2 for PR HEAD a551898 in total

[openshift-ci]

@mike-nguyen: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-vsphere-ovn	96e7b41f12d68f10b410767ce2ed9f14a48b2008	link	true	/test e2e-vsphere-ovn
ci/prow/e2e-vsphere-upi-zones	96e7b41f12d68f10b410767ce2ed9f14a48b2008	link	false	/test e2e-vsphere-upi-zones
ci/prow/e2e-aws-ovn-upgrade	a551898	link	false	/test e2e-aws-ovn-upgrade
ci/prow/okd-scos-e2e-aws-ovn	a551898	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/okd-scos-e2e-aws-upgrade	a551898	link	false	/test okd-scos-e2e-aws-upgrade
ci/prow/okd-e2e-aws-ovn-upgrade	a551898	link	false	/test okd-e2e-aws-ovn-upgrade
ci/prow/okd-e2e-aws-ovn	a551898	link	false	/test okd-e2e-aws-ovn
ci/prow/e2e-aws-ovn-workers-rhel8	a551898	link	false	/test e2e-aws-ovn-workers-rhel8

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[sdodson]

/cherry-pick release-4.13

[openshift-cherrypick-robot]

@sdodson: new pull request created: #6955

Details

In response to this:

/cherry-pick release-4.13

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.