Skip to content

[release-4.15] OCPBUGS-57136: aws/edge: prevent test using unschedulable nodes #29897

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
merged 1 commit into from
Jun 23, 2025
Merged

[release-4.15] OCPBUGS-57136: aws/edge: prevent test using unschedulable nodes #29897

merged 1 commit into from
Jun 23, 2025

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #29847

/assign openshift-cherrypick-robot

@mtulio
OCPBUGS-54700: aws/edge: prevent test using unschedulable nodes
7d2a1e1 
This fix prevents the test to select invalid worker nodes - nodes which
have taint added.
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Jun 5, 2025
Merged
@openshift-ci-robot
Copy link

@openshift-cherrypick-robot: Jira Issue OCPBUGS-56704 has been cloned as Jira Issue OCPBUGS-57136. Will retitle bug to link to clone.
/retitle [release-4.15] OCPBUGS-57136: aws/edge: prevent test using unschedulable nodes

In response to this:

This is an automated cherry-pick of #29847

/assign openshift-cherrypick-robot

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.15] OCPBUGS-56704: aws/edge: prevent test using unschedulable nodes [release-4.15] OCPBUGS-57136: aws/edge: prevent test using unschedulable nodes Jun 5, 2025
@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 Jun 5, 2025
@openshift-ci-robot
Copy link

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

  • expected dependent Jira Issue OCPBUGS-56704 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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 #29847

/assign openshift-cherrypick-robot

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 review from danwinship and trozet June 5, 2025 22:50
@mtulio
Copy link
Contributor

mtulio commented Jun 5, 2025

/test ?

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jun 5, 2025

@mtulio: The following commands are available to trigger required jobs:

/test e2e-aws-jenkins

/test e2e-aws-ovn-fips

/test e2e-aws-ovn-image-registry

/test e2e-aws-ovn-serial

/test e2e-gcp-ovn

/test e2e-gcp-ovn-builds

/test e2e-gcp-ovn-image-ecosystem

/test e2e-gcp-ovn-upgrade

/test e2e-metal-ipi-ovn-ipv6

/test images

/test lint

/test unit

/test verify

/test verify-deps

The following commands are available to trigger optional jobs:

/test e2e-agnostic-ovn-cmd

/test e2e-aws

/test e2e-aws-csi

/test e2e-aws-disruptive

/test e2e-aws-etcd-recovery

/test e2e-aws-multitenant

/test e2e-aws-ovn

/test e2e-aws-ovn-cgroupsv2

/test e2e-aws-ovn-etcd-scaling

/test e2e-aws-ovn-kubevirt

/test e2e-aws-ovn-single-node

/test e2e-aws-ovn-single-node-serial

/test e2e-aws-ovn-single-node-upgrade

/test e2e-aws-ovn-upgrade

/test e2e-aws-ovn-upi

/test e2e-aws-proxy

/test e2e-azure

/test e2e-azure-ovn-etcd-scaling

/test e2e-baremetalds-kubevirt

/test e2e-gcp-csi

/test e2e-gcp-disruptive

/test e2e-gcp-fips-serial

/test e2e-gcp-ovn-etcd-scaling

/test e2e-gcp-ovn-rt-upgrade

/test e2e-gcp-ovn-techpreview

/test e2e-gcp-ovn-techpreview-serial

/test e2e-metal-ipi-ovn-dualstack

/test e2e-metal-ipi-sdn

/test e2e-metal-ipi-serial

/test e2e-metal-ipi-serial-ovn-ipv6

/test e2e-metal-ipi-virtualmedia

/test e2e-openstack-ovn

/test e2e-openstack-serial

/test e2e-vsphere

/test e2e-vsphere-ovn-etcd-scaling

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-origin-release-4.15-e2e-agnostic-ovn-cmd

pull-ci-openshift-origin-release-4.15-e2e-aws-csi

pull-ci-openshift-origin-release-4.15-e2e-aws-etcd-recovery

pull-ci-openshift-origin-release-4.15-e2e-aws-ovn-cgroupsv2

pull-ci-openshift-origin-release-4.15-e2e-aws-ovn-fips

pull-ci-openshift-origin-release-4.15-e2e-aws-ovn-serial

pull-ci-openshift-origin-release-4.15-e2e-aws-ovn-single-node

pull-ci-openshift-origin-release-4.15-e2e-aws-ovn-single-node-serial

pull-ci-openshift-origin-release-4.15-e2e-aws-ovn-single-node-upgrade

pull-ci-openshift-origin-release-4.15-e2e-aws-ovn-upgrade

pull-ci-openshift-origin-release-4.15-e2e-gcp-csi

pull-ci-openshift-origin-release-4.15-e2e-gcp-ovn

pull-ci-openshift-origin-release-4.15-e2e-gcp-ovn-rt-upgrade

pull-ci-openshift-origin-release-4.15-e2e-gcp-ovn-upgrade

pull-ci-openshift-origin-release-4.15-e2e-metal-ipi-ovn-ipv6

pull-ci-openshift-origin-release-4.15-e2e-metal-ipi-sdn

pull-ci-openshift-origin-release-4.15-e2e-openstack-ovn

pull-ci-openshift-origin-release-4.15-images

pull-ci-openshift-origin-release-4.15-lint

pull-ci-openshift-origin-release-4.15-unit

pull-ci-openshift-origin-release-4.15-verify

pull-ci-openshift-origin-release-4.15-verify-deps

In response to this:

/test ?

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.

@mtulio
Copy link
Contributor

mtulio commented Jun 9, 2025

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

@mtulio: This pull request references Jira Issue OCPBUGS-57136, 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.15.z) matches configured target version for branch (4.15.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-56704 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-56704 targets the "4.16.z" version, which is one of the valid target versions: 4.16.0, 4.16.z
  • bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

In response to this:

/retest-required
/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 Jun 9, 2025
@openshift-ci openshift-ci bot requested a review from anuragthehatter June 9, 2025 13:51
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jun 9, 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-aws-ovn-single-node-upgrade 7d2a1e1 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-etcd-recovery 7d2a1e1 link false /test e2e-aws-etcd-recovery
ci/prow/e2e-aws-ovn-single-node-serial 7d2a1e1 link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-aws-ovn-single-node 7d2a1e1 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-openstack-ovn 7d2a1e1 link false /test e2e-openstack-ovn

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.

@mtulio
Copy link
Contributor

mtulio commented Jun 11, 2025

/test e2e-gcp-ovn-upgrade

@rvanderp3
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 16, 2025
@jupierce jupierce added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels Jun 20, 2025
@knobunc
Copy link
Contributor

knobunc commented Jun 23, 2025

/approve

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jun 23, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Jun 23, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 4a51fe9 into openshift:release-4.15 Jun 23, 2025
18 of 23 checks passed
@openshift-ci-robot
Copy link

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

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

In response to this:

This is an automated cherry-pick of #29847

/assign openshift-cherrypick-robot

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]

Distgit: openshift-enterprise-tests
This PR has been included in build openshift-enterprise-tests-container-v4.15.0-202506231606.p0.g4a51fe9.assembly.stream.el8.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.15.0-0.nightly-2025-06-23-215731

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

@danwinship danwinship Awaiting requested review from danwinship

@trozet trozet Awaiting requested review from trozet

@anuragthehatter anuragthehatter Awaiting requested review from anuragthehatter

Assignees

@dgoodwin dgoodwin

@adambkaplan adambkaplan

@kasturinarra kasturinarra

@Moebasim Moebasim

@openshift-cherrypick-robot openshift-cherrypick-robot

@jadhaj jadhaj

@pamoedom pamoedom

@rvanderp3 rvanderp3

@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-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.