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.

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

OCPBUGS-44327: Update RHCOS 4.18 bootimage metadata to 418.94.202411221729-0 #9237

Open
wants to merge 1 commit into
base: release-4.18
Choose a base branch
from

Conversation

mike-nguyen
Copy link
Member

@mike-nguyen mike-nguyen commented Nov 25, 2024

The changes done here will update the RHCOS 4.18 bootimage metadata and address the following issues:

OCPBUGS-44310 - Request to update RHCOS bootimage for nmstate COS-2993 - Stop publishing Alibaba RHCOS images

This change was generated using

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

The changes done here will update the RHCOS 4.18 bootimage metadata
and address the following issues:

OCPBUGS-44310 - Request to update RHCOS bootimage for nmstate
COS-2993 - Stop publishing Alibaba RHCOS images

This change was generated using

```
plume cosa2stream --target data/data/coreos/rhcos.json                \
    --distro rhcos --no-signatures --name 4.18-9.4                    \
    --url https://rhcos.mirror.openshift.com/art/storage/prod/streams \
    x86_64=418.94.202411221729-0                                      \
    aarch64=418.94.202411221729-0                                     \
    s390x=418.94.202411221729-0                                       \
    ppc64le=418.94.202411221729-0
```
@mike-nguyen mike-nguyen changed the title Update RHCOS 4.18 bootimage metadata to 418.94.202411221729-0 OCPBUGS-44327: Update RHCOS 4.18 bootimage metadata to 418.94.202411221729-0 Nov 25, 2024
@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. labels Nov 25, 2024
@openshift-ci-robot
Copy link
Contributor

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

  • expected the bug to target either version "4.19." or "openshift-4.19.", but it targets "4.18.0" instead

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:

The changes done here will update the RHCOS 4.18 bootimage metadata and address the following issues:

OCPBUGS-44310 - Request to update RHCOS bootimage for nmstate COS-2993 - Stop publishing Alibaba RHCOS images

This change was generated using

plume cosa2stream --target data/data/coreos/rhcos.json                \
   --distro rhcos --no-signatures --name 4.18-9.4                    \
   --url https://rhcos.mirror.openshift.com/art/storage/prod/streams \
   x86_64=418.94.202411221729-0                                      \
   aarch64=418.94.202411221729-0                                     \
   s390x=418.94.202411221729-0                                       \
   ppc64le=418.94.202411221729-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-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Nov 25, 2024
Copy link
Member

@dustymabe dustymabe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

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

openshift-ci bot commented Nov 25, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dustymabe

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 Nov 25, 2024
@mike-nguyen mike-nguyen changed the base branch from master to release-4.18 November 25, 2024 17:58
@openshift-ci-robot
Copy link
Contributor

@mike-nguyen: This pull request references Jira Issue OCPBUGS-44327, 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 Jira Issue OCPBUGS-44327 to depend on a bug targeting a version in 4.19.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, 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.

In response to this:

The changes done here will update the RHCOS 4.18 bootimage metadata and address the following issues:

OCPBUGS-44310 - Request to update RHCOS bootimage for nmstate COS-2993 - Stop publishing Alibaba RHCOS images

This change was generated using

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

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 Nov 25, 2024
@openshift-ci-robot
Copy link
Contributor

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

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-44977 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-44977 targets the "4.19.0" version, which is one of the valid target versions: 4.19.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.

Copy link
Contributor

openshift-ci bot commented Nov 25, 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-44327, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-44977 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-44977 targets the "4.19.0" version, which is one of the valid target versions: 4.19.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-sigs/prow 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 Nov 25, 2024
@mike-nguyen
Copy link
Member Author

@gpei can I get a cherry-pick-approved label on this bootimage bump?

@gpei
Copy link
Contributor

gpei commented Nov 26, 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 Nov 26, 2024
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

2 similar comments
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

24 similar comments
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

Copy link
Contributor

openshift-ci bot commented Nov 29, 2024

@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/okd-scos-e2e-aws-ovn 7badb5d link false /test okd-scos-e2e-aws-ovn
ci/prow/okd-e2e-aws-ovn-upgrade 7badb5d link false /test okd-e2e-aws-ovn-upgrade
ci/prow/e2e-openstack-ovn 7badb5d link true /test e2e-openstack-ovn
ci/prow/okd-images 7badb5d link true /test okd-images

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-sigs/prow repository. I understand the commands that are listed here.

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

3 similar comments
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2ec0039 and 2 for PR HEAD 7badb5d in total

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

Successfully merging this pull request may close these issues.

4 participants