Skip to content

Conversation

@djoshy
Copy link
Contributor

@djoshy djoshy commented Jan 22, 2026

Manual cherry pick of #5568 due to:

  • The node sizing test doesn't exist in 4.20
  • The os streams feature gate doesn't exist in 4.20 and so doesn't need to be excluded
  • ClusterImagePolicy feature didn't exist yet(or atleast wasn't a load bearing feature), so it did not need to have a manifest
  • The ulimit generated MCs were mistakenly being created within the test case, so I removed these calls; the bootstrap process automatically makes them. It uses a "marker" configmap method that wasn't being cleaned up between test cases, so added that clean-up too.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 22, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 22, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@djoshy
Copy link
Contributor Author

djoshy commented Jan 22, 2026

/jira cherry-pick OCPBUGS-74237

@openshift-ci-robot
Copy link
Contributor

@djoshy: Jira Issue OCPBUGS-74237 has been cloned as Jira Issue OCPBUGS-74297. Will retitle bug to link to clone.
/retitle OCPBUGS-74297: e2e-bootstrap: reconcile CRD updates

Details

In response to this:

/jira cherry-pick OCPBUGS-74237

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 e2e-bootstrap: reconcile CRD updates OCPBUGS-74297: e2e-bootstrap: reconcile CRD updates Jan 22, 2026
@djoshy
Copy link
Contributor Author

djoshy commented Jan 22, 2026

/test bootstrap-unit

@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 Jan 22, 2026
@openshift-ci-robot
Copy link
Contributor

@djoshy: This pull request references Jira Issue OCPBUGS-74297, 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-74237 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead
  • expected dependent Jira Issue OCPBUGS-74237 to target a version in 4.21.0, but it targets "4.22.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.

Details

In response to this:

Manual cherry pick of #5568 due to:

  • The node sizing test doesn't exist in 4.20
  • The os streams feature gate doesn't exist in 4.20 and so doesn't need to be excluded

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 Jan 22, 2026

@djoshy: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test e2e-aws-ovn
/test e2e-aws-ovn-upgrade
/test e2e-gcp-op-1of2
/test e2e-gcp-op-2of2
/test e2e-gcp-op-single-node
/test e2e-hypershift
/test images
/test okd-scos-images
/test periodics-images
/test unit
/test verify
/test verify-deps

The following commands are available to trigger optional jobs:

/test bootstrap-unit
/test e2e-agent-compact-ipv4
/test e2e-aws-disruptive
/test e2e-aws-mco-disruptive
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-fips-op
/test e2e-aws-ovn-ocb-techpreview
/test e2e-aws-ovn-serial-ipsec
/test e2e-aws-ovn-upgrade-ipsec
/test e2e-aws-ovn-upgrade-ocb-techpreview
/test e2e-aws-ovn-upgrade-out-of-change
/test e2e-aws-ovn-windows
/test e2e-aws-ovn-workers-rhel8
/test e2e-aws-proxy
/test e2e-aws-serial
/test e2e-aws-single-node
/test e2e-aws-upgrade-single-node
/test e2e-aws-workers-rhel8
/test e2e-azure
/test e2e-azure-ovn-upgrade
/test e2e-azure-ovn-upgrade-out-of-change
/test e2e-azure-upgrade
/test e2e-gcp-mco-disruptive
/test e2e-gcp-op
/test e2e-gcp-op-ocl
/test e2e-gcp-op-techpreview
/test e2e-gcp-ovn-rt-upgrade
/test e2e-gcp-rt
/test e2e-gcp-rt-op
/test e2e-gcp-single-node
/test e2e-gcp-upgrade
/test e2e-hypershift-techpreview
/test e2e-metal-assisted
/test e2e-metal-ipi-ovn-dualstack
/test e2e-metal-ipi-ovn-ipv6
/test e2e-metal-ovn-two-node-arbiter
/test e2e-metal-ovn-two-node-fencing
/test e2e-openstack
/test e2e-openstack-dualstack
/test e2e-openstack-externallb
/test e2e-openstack-hypershift
/test e2e-openstack-parallel
/test e2e-openstack-singlestackv6
/test e2e-ovirt
/test e2e-ovirt-upgrade
/test e2e-ovn-step-registry
/test e2e-vsphere
/test e2e-vsphere-ovn-upi
/test e2e-vsphere-ovn-upi-zones
/test e2e-vsphere-ovn-zones
/test e2e-vsphere-upgrade
/test okd-scos-e2e-aws-ovn
/test security

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

pull-ci-openshift-machine-config-operator-release-4.20-bootstrap-unit
pull-ci-openshift-machine-config-operator-release-4.20-e2e-aws-ovn
pull-ci-openshift-machine-config-operator-release-4.20-e2e-aws-ovn-upgrade
pull-ci-openshift-machine-config-operator-release-4.20-e2e-gcp-op-1of2
pull-ci-openshift-machine-config-operator-release-4.20-e2e-gcp-op-2of2
pull-ci-openshift-machine-config-operator-release-4.20-e2e-gcp-op-ocl
pull-ci-openshift-machine-config-operator-release-4.20-e2e-gcp-op-single-node
pull-ci-openshift-machine-config-operator-release-4.20-e2e-hypershift
pull-ci-openshift-machine-config-operator-release-4.20-images
pull-ci-openshift-machine-config-operator-release-4.20-okd-scos-images
pull-ci-openshift-machine-config-operator-release-4.20-periodics-images
pull-ci-openshift-machine-config-operator-release-4.20-security
pull-ci-openshift-machine-config-operator-release-4.20-unit
pull-ci-openshift-machine-config-operator-release-4.20-verify
pull-ci-openshift-machine-config-operator-release-4.20-verify-deps
Details

In response to this:

/test bootstrap-e2e

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-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 22, 2026
@djoshy
Copy link
Contributor Author

djoshy commented Jan 22, 2026

/jira cherry-pick OCPBUGS-74103

@openshift-ci-robot
Copy link
Contributor

@djoshy: Jira Issue OCPBUGS-74103 has been cloned as Jira Issue OCPBUGS-74298. Will retitle bug to link to clone.
/retitle OCPBUGS-74298: OCPBUGS-74297: e2e-bootstrap: reconcile CRD updates

Details

In response to this:

/jira cherry-pick OCPBUGS-74103

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 OCPBUGS-74297: e2e-bootstrap: reconcile CRD updates OCPBUGS-74298: OCPBUGS-74297: e2e-bootstrap: reconcile CRD updates Jan 22, 2026
@openshift-ci-robot openshift-ci-robot removed the jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. label Jan 22, 2026
@openshift-ci-robot
Copy link
Contributor

@djoshy: This pull request references Jira Issue OCPBUGS-74298, which is invalid:

  • expected dependent Jira Issue OCPBUGS-74103 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.

Details

In response to this:

Manual cherry pick of #5568 due to:

  • The node sizing test doesn't exist in 4.20
  • The os streams feature gate doesn't exist in 4.20 and so doesn't need to be excluded

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.

@djoshy djoshy changed the title OCPBUGS-74298: OCPBUGS-74297: e2e-bootstrap: reconcile CRD updates [release-4.20] OCPBUGS-74298: Fix up bootstrap-e2e Jan 22, 2026
@djoshy djoshy force-pushed the release-4.20-bootstrap-e2e-fix branch from 23f1ae6 to 0bb00db Compare January 26, 2026 22:36
@djoshy
Copy link
Contributor Author

djoshy commented Jan 26, 2026

/test bootstrap-unit

@djoshy djoshy marked this pull request as ready for review January 26, 2026 22:44
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 26, 2026
@djoshy
Copy link
Contributor Author

djoshy commented Jan 27, 2026

/jira refresh

/test all

/verified by e2es

@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 Jan 27, 2026
@openshift-ci-robot
Copy link
Contributor

@djoshy: This pull request references Jira Issue OCPBUGS-74298, 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.20.z) matches configured target version for branch (4.20.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-74103 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-74103 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0
  • bug has dependents

Requesting review from QA contact:
/cc @sergiordlr

Details

In response to this:

/jira refresh

/test all

/verified by e2es

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 sergiordlr January 27, 2026 13:58
@djoshy
Copy link
Contributor Author

djoshy commented Jan 27, 2026

/verified by e2es

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 27, 2026
@openshift-ci-robot
Copy link
Contributor

@djoshy: This PR has been marked as verified by e2es.

Details

In response to this:

/verified by e2es

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
Member

@isabella-janssen isabella-janssen left a comment

Choose a reason for hiding this comment

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

/label backport-risk-assessed
/lgtm

It looks like the bootstrap e2e is passing and these changes look clean.

@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 Jan 27, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 27, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 27, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: djoshy, isabella-janssen

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:
  • OWNERS [djoshy,isabella-janssen]

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

@isabella-janssen
Copy link
Member

/test e2e-hypershift

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 27, 2026

@djoshy: 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-gcp-op-ocl 0bb00db link false /test e2e-gcp-op-ocl

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 035a7f3 into openshift:release-4.20 Jan 27, 2026
15 of 16 checks passed
@openshift-ci-robot
Copy link
Contributor

@djoshy: Jira Issue Verification Checks: Jira Issue OCPBUGS-74298
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-74298 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Manual cherry pick of #5568 due to:

  • The node sizing test doesn't exist in 4.20
  • The os streams feature gate doesn't exist in 4.20 and so doesn't need to be excluded
  • ClusterImagePolicy feature didn't exist yet(or atleast wasn't a load bearing feature), so it did not need to have a manifest
  • The ulimit generated MCs were mistakenly being created within the test case, so I removed these calls; the bootstrap process automatically makes them. It uses a "marker" configmap method that wasn't being cleaned up between test cases, so added that clean-up too.

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

Fix included in accepted release 4.20.0-0.nightly-2026-01-28-090316

@djoshy djoshy deleted the release-4.20-bootstrap-e2e-fix branch January 28, 2026 20:50
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. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.