Skip to content

[release-4.18] OCPBUGS-55158: Add the afterburn package into the openshift_node_packages list #12530

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
Open
wants to merge 1 commit into
base: release-4.18
Choose a base branch
from
Open

[release-4.18] OCPBUGS-55158: Add the afterburn package into the openshift_node_packages list #12530

wants to merge 1 commit into from

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #12529

/assign gpei

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Apr 19, 2025
Merged
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-54955 has been cloned as Jira Issue OCPBUGS-55158. Will retitle bug to link to clone.
/retitle [release-4.18] OCPBUGS-55158: Add the afterburn package into the openshift_node_packages list

In response to this:

This is an automated cherry-pick of #12529

/assign gpei

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 bot changed the title [release-4.18] OCPBUGS-54955: Add the afterburn package into the openshift_node_packages list [release-4.18] OCPBUGS-55158: Add the afterburn package into the openshift_node_packages list Apr 19, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important 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 Apr 19, 2025
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-55158, 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-54955 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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:

This is an automated cherry-pick of #12529

/assign gpei

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.

@gpei
Copy link
Contributor

gpei commented Apr 21, 2025

/jira refresh

@openshift-ci-robot
Copy link

@gpei: An error was encountered updating to the POST state for bug OCPBUGS-55158 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message. No response returned: Get "https://issues.redhat.com/rest/api/2/issue/16838415/transitions?expand=transitions.fields": GET https://issues.redhat.com/rest/api/2/issue/16838415/transitions?expand=transitions.fields giving up after 5 attempt(s)

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

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.

@gpei
Copy link
Contributor

gpei commented Apr 21, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Apr 21, 2025
@openshift-ci-robot
Copy link

@gpei: This pull request references Jira Issue OCPBUGS-55158, 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.z) matches configured target version for branch (4.18.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-54955 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-54955 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 @gpei

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-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Apr 21, 2025
@openshift-ci openshift-ci bot requested a review from gpei April 21, 2025 05:33
@gpei
Copy link
Contributor

gpei commented Apr 21, 2025

/retest-required

barbacbd
barbacbd reviewed Apr 21, 2025
View reviewed changes
Copy link
Contributor

@barbacbd barbacbd 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 Apr 21, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Apr 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: barbacbd, openshift-cherrypick-robot

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 Apr 21, 2025
@barbacbd
Copy link
Contributor

/retest-required

1 similar comment
@gpei
Copy link
Contributor

gpei commented Apr 22, 2025

/retest-required

@barbacbd
Copy link
Contributor

barbacbd commented May 5, 2025

/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 May 5, 2025
@barbacbd
Copy link
Contributor

barbacbd commented May 5, 2025

/test e2e-aws-workers-rhel8

@barbacbd
Copy link
Contributor

barbacbd commented May 5, 2025

/test e2e-aws-workers-rhel9

@gpei
Copy link
Contributor

gpei commented May 6, 2025

/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 May 6, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 006fe4e and 2 for PR HEAD fe5e1bc in total

@gpei
Copy link
Contributor

gpei commented May 6, 2025

@barbacbd Looks like the e2e-aws-workers-rhel9 test failed for "The key pair 'openshift-dev' does not exist", do you happen to know anything about this SSH key?

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 006fe4e and 2 for PR HEAD fe5e1bc in total

7 similar comments
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 006fe4e and 2 for PR HEAD fe5e1bc in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 006fe4e and 2 for PR HEAD fe5e1bc in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 006fe4e and 2 for PR HEAD fe5e1bc in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 006fe4e and 2 for PR HEAD fe5e1bc in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 006fe4e and 2 for PR HEAD fe5e1bc in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 006fe4e and 2 for PR HEAD fe5e1bc in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 006fe4e and 2 for PR HEAD fe5e1bc in total

@barbacbd
Copy link
Contributor

barbacbd commented May 7, 2025

@barbacbd Looks like the e2e-aws-workers-rhel9 test failed for "The key pair 'openshift-dev' does not exist", do you happen to know anything about this SSH key?

I do not. I would guess this was setup by someone long long ago.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 006fe4e and 2 for PR HEAD fe5e1bc in total

@gpei
Copy link
Contributor

gpei commented May 8, 2025 •
edited
Loading

@barbacbd I think it's caused by the recent cluster_profile change on those AWS jobs. The test e2e-aws-workers-rhel8 using the previous cluster profile aws is working well, so I updated the cluster_profile for those openshift-ansible test in openshift/release#64674 to address this.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 006fe4e and 2 for PR HEAD fe5e1bc in total

3 similar comments
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 006fe4e and 2 for PR HEAD fe5e1bc in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 006fe4e and 2 for PR HEAD fe5e1bc in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 006fe4e and 2 for PR HEAD fe5e1bc in total

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented May 9, 2025

@openshift-cherrypick-robot: The following test 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-workers-rhel9 fe5e1bc link true /test e2e-aws-workers-rhel9

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.

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

@barbacbd barbacbd barbacbd left review comments

@patrickdillon patrickdillon Awaiting requested review from patrickdillon

@gpei gpei Awaiting requested review from gpei

Assignees

@gpei gpei

@barbacbd barbacbd

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-important Referenced Jira bug's severity is important 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.
4 participants
@openshift-cherrypick-robot @openshift-ci-robot @gpei @barbacbd