Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

OCPBUGS-29626: update RHCOS 4.14 bootimage metadata to 414.92.202402130420-0 #8037

Merged
merged 1 commit into from Feb 21, 2024
Merged

OCPBUGS-29626: update RHCOS 4.14 bootimage metadata to 414.92.202402130420-0 #8037

merged 1 commit into from Feb 21, 2024

Conversation

mike-nguyen
Copy link
Member

These changes will update the RHCOS 4.14 boot image metadata. Issues fixed in this bootimage are:

OCPBUGS-29252 - Backport fix for unexpected Azure IMDS status codes

This change was generated using:

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

@mike-nguyen
update RHCOS 4.14 bootimage metadata to 414.92.202402130420-0
d23a0e4 
These changes will update the RHCOS 4.14 boot image metadata. Issues
fixed in this bootimage are:

OCPBUGS-29252 - Backport fix for unexpected Azure IMDS status codes

This change was generated using:
```
plume cosa2stream --target data/data/coreos/rhcos.json                \
    --distro rhcos --no-signatures --name 4.14-9.2                    \
    --url https://rhcos.mirror.openshift.com/art/storage/prod/streams \
    x86_64=414.92.202402130420-0                                     \
    aarch64=414.92.202402130420-0                                    \
    s390x=414.92.202402130420-0                                      \
    ppc64le=414.92.202402130420-0
```
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 16, 2024
@openshift-ci-robot
Copy link
Contributor

@mike-nguyen: This pull request references Jira Issue OCPBUGS-29626, which is invalid:

  • expected Jira Issue OCPBUGS-29626 to depend on a bug targeting a version in 4.15.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

In response to this:

These changes will update the RHCOS 4.14 boot image metadata. Issues fixed in this bootimage are:

OCPBUGS-29252 - Backport fix for unexpected Azure IMDS status codes

This change was generated using:

plume cosa2stream --target data/data/coreos/rhcos.json                \
   --distro rhcos --no-signatures --name 4.14-9.2                    \
   --url https://rhcos.mirror.openshift.com/art/storage/prod/streams \
   x86_64=414.92.202402130420-0                                     \
   aarch64=414.92.202402130420-0                                    \
   s390x=414.92.202402130420-0                                      \
   ppc64le=414.92.202402130420-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.

@mike-nguyen
Copy link
Member Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@mike-nguyen: This pull request references Jira Issue OCPBUGS-29626, which is invalid:

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.

In response to this:

/jira refresh

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.

@mike-nguyen
Copy link
Member Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 16, 2024
@openshift-ci-robot
Copy link
Contributor

@mike-nguyen: This pull request references Jira Issue OCPBUGS-29626, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.z) matches configured target version for branch (4.14.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-29442 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-29442 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
  • bug has dependents

Requesting review from QA contact:
/cc @mike-nguyen

In response to this:

/jira refresh

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 OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 16, 2024

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: mike-nguyen.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

@mike-nguyen: This pull request references Jira Issue OCPBUGS-29626, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.z) matches configured target version for branch (4.14.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-29442 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-29442 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
  • bug has dependents

Requesting review from QA contact:
/cc @mike-nguyen

In response to this:

/jira refresh

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.

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.

@mike-nguyen
Copy link
Member Author

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Feb 16, 2024
@mike-nguyen
Copy link
Member Author

@gpei can I get a cherry-pick-approved label for this RHCOS boot image bump?

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 16, 2024 •
edited

@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-aws-ovn-workers-rhel8 d23a0e4 link false /test e2e-aws-ovn-workers-rhel8
ci/prow/okd-scos-e2e-gcp d23a0e4 link false /test okd-scos-e2e-gcp
ci/prow/e2e-aws-ovn-upgrade d23a0e4 link false /test e2e-aws-ovn-upgrade
ci/prow/okd-e2e-aws-ovn-upgrade d23a0e4 link false /test okd-e2e-aws-ovn-upgrade
ci/prow/okd-e2e-aws-ovn d23a0e4 link false /test okd-e2e-aws-ovn
ci/prow/okd-scos-e2e-aws-ovn d23a0e4 link false /test okd-scos-e2e-aws-ovn
ci/prow/okd-scos-e2e-aws-upgrade d23a0e4 link false /test okd-scos-e2e-aws-upgrade
ci/prow/okd-scos-e2e-vsphere d23a0e4 link false /test okd-scos-e2e-vsphere
ci/prow/okd-scos-e2e-gcp-ovn-upgrade d23a0e4 link false /test okd-scos-e2e-gcp-ovn-upgrade

Full PR test history. Your PR dashboard.

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.

@gpei
Copy link
Contributor

gpei commented Feb 17, 2024

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Feb 17, 2024
@jmarrero
Copy link
Member

/lgtm
/approve

@jmarrero
Copy link
Member

/retest-required

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 21, 2024
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 21, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jmarrero

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 21, 2024
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 21, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jmarrero

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@openshift-merge-bot openshift-merge-bot bot merged commit 6ee6900 into openshift:release-4.14 Feb 21, 2024
21 of 30 checks passed
@openshift-ci-robot
Copy link
Contributor

@mike-nguyen: Jira Issue OCPBUGS-29626: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-29626 has been moved to the MODIFIED state.

In response to this:

These changes will update the RHCOS 4.14 boot image metadata. Issues fixed in this bootimage are:

OCPBUGS-29252 - Backport fix for unexpected Azure IMDS status codes

This change was generated using:

plume cosa2stream --target data/data/coreos/rhcos.json                \
   --distro rhcos --no-signatures --name 4.14-9.2                    \
   --url https://rhcos.mirror.openshift.com/art/storage/prod/streams \
   x86_64=414.92.202402130420-0                                     \
   aarch64=414.92.202402130420-0                                    \
   s390x=414.92.202402130420-0                                      \
   ppc64le=414.92.202402130420-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-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-installer-container-v4.14.0-202402210539.p0.g6ee6900.assembly.stream.el8 for distgit ose-installer.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.14.0-0.nightly-2024-02-21-181159

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jmarrero jmarrero jmarrero approved these changes

@marmijo marmijo Awaiting requested review from marmijo

Assignees

@jmarrero jmarrero

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
6 participants
@mike-nguyen @openshift-ci-robot @gpei @jmarrero @openshift-bot @openshift-merge-robot