OCPBUGS-60668: Update RHCOS-release-4.16 bootimage metadata to 416.94.202601221345-0

[coreosbot-releng]

Update RHCOS release-4.16 bootimage metadata to 416.94.202601221345-0

The changes done here will update the RHCOS release-4.16 bootimage metadata and address the following issues:

RHEL-135348 Backport coreos/coreos-installer#1699 [rhel-9.4.z]
COS-3518 [coreos/coreos-installer] Args passed via --firstboot-args are lost if also using --config-file

This change was generated using:

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

[openshift-ci-robot]

@coreosbot-releng: This pull request references Jira Issue OCPBUGS-60668, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-67206 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead
• expected dependent Jira Issue OCPBUGS-67206 to target a version in 4.17.0, 4.17.z, but it targets "4.16.z" instead
• dependent bug RHEL-135348 is not in the required OCPBUGS project
• dependent bug COS-3518 is not in the required OCPBUGS project

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Update RHCOS release-4.16 bootimage metadata to 416.94.202601221345-0

The changes done here will update the RHCOS release-4.16 bootimage metadata and address the following issues:

RHEL-135348 Backport coreos/coreos-installer#1699 [rhel-9.4.z]
COS-3518 [coreos/coreos-installer] Args passed via --firstboot-args are lost if also using --config-file

This change was generated using:

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

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Hi @coreosbot-releng. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign gursewak1997 for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• data/data/coreos/OWNERS

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