Skip to content

[release-4.19] OCPBUGS-56829: Only update boot disks during GCP boot image updates tests #29878

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
Merged
openshift-merge-bot merged 1 commit into from
Jun 4, 2025
Merged

[release-4.19] OCPBUGS-56829: Only update boot disks during GCP boot image updates tests #29878

openshift-merge-bot merged 1 commit into from
Jun 4, 2025

Conversation

@openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented Jun 2, 2025

This is an automated cherry-pick of #29869

/assign djoshy

/cherrypick release-4.18

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Jun 2, 2025
Merged
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 2, 2025

@openshift-cherrypick-robot: Detected clone of Jira Issue OCPBUGS-55830 with correct target version. Will retitle the PR to link to the clone.
/retitle [release-4.19] OCPBUGS-56829: Only update boot disks during GCP boot image updates tests

Details

In response to this:

This is an automated cherry-pick of #29869

/assign djoshy

/cherrypick release-4.18

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.19] OCPBUGS-55830: Only update boot disks during GCP boot image updates tests [release-4.19] OCPBUGS-56829: Only update boot disks during GCP boot image updates tests Jun 2, 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 Jun 2, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 2, 2025

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-56829, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified 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.

Details

In response to this:

This is an automated cherry-pick of #29869

/assign djoshy

/cherrypick release-4.18

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

openshift-ci bot commented Jun 2, 2025 •
edited
Loading

@openshift-cherrypick-robot: 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-openstack-ovn 0ab7bc4 link false /test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-cgroupsv2 0ab7bc4 link false /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-aws-ovn-single-node 0ab7bc4 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-techpreview 0ab7bc4 link false /test e2e-metal-ipi-ovn-dualstack-bgp-techpreview
ci/prow/e2e-aws-ovn-single-node-upgrade 0ab7bc4 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-metal-ipi-ovn 0ab7bc4 link false /test e2e-metal-ipi-ovn

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

@djoshy
Copy link
Contributor

djoshy commented Jun 4, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 4, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 4, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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:

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 Jun 4, 2025
@djoshy
Copy link
Contributor

djoshy commented Jun 4, 2025

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

openshift-ci-robot commented Jun 4, 2025

@djoshy: This pull request references Jira Issue OCPBUGS-56829, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-55830 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-55830 targets the "4.20.0" version, which is one of the valid target versions: 4.20.0
  • bug has dependents

Requesting review from QA contact:
/cc @miyadav

Details

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 bot requested a review from miyadav June 4, 2025 16:42
@stbenjam
Copy link
Member

stbenjam commented Jun 4, 2025

/label backport-risk-assessed
/label cherry-pick-approved

@openshift-ci openshift-ci bot added 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. labels Jun 4, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 4, 2025

/retest-required

Remaining retests: 0 against base HEAD 58eaf4b and 2 for PR HEAD 0ab7bc4 in total

@openshift-merge-bot openshift-merge-bot bot merged commit 72252f9 into openshift:release-4.19 Jun 4, 2025
27 of 33 checks passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 4, 2025

@openshift-cherrypick-robot: Jira Issue OCPBUGS-56829: All pull requests linked via external trackers have merged:

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

Details

In response to this:

This is an automated cherry-pick of #29869

/assign djoshy

/cherrypick release-4.18

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-cherrypick-robot
Copy link
Author

openshift-cherrypick-robot commented Jun 4, 2025

@openshift-cherrypick-robot: new pull request created: #29894

Details

In response to this:

This is an automated cherry-pick of #29869

/assign djoshy

/cherrypick release-4.18

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-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Jun 4, 2025
Merged
@openshift-bot
Copy link
Contributor

openshift-bot commented Jun 5, 2025

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-tests
This PR has been included in build openshift-enterprise-tests-container-v4.19.0-202506050047.p0.g72252f9.assembly.stream.el9.
All builds following this will include this PR.

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

Reviewers

@cheesesashimi cheesesashimi Awaiting requested review from cheesesashimi

@dkhater-redhat dkhater-redhat Awaiting requested review from dkhater-redhat

@miyadav miyadav Awaiting requested review from miyadav

Assignees

@dgoodwin dgoodwin

@adambkaplan adambkaplan

@djoshy djoshy

@kasturinarra kasturinarra

@Moebasim Moebasim

@jadhaj jadhaj

@pamoedom pamoedom

@prietyc123 prietyc123

@gangwgr gangwgr

@prabhapa prabhapa

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.