Skip to content

Conversation

@pablintino
Copy link
Contributor

- What I did

Update Dockerfile and generated Dockerfile.rhel7 to use OpenShift 4.22 builder images and base image instead of 4.21.

- How to verify it

Automated pre-submit e2e is enough.

- Description for the changelog

Update Dockerfile and generated Dockerfile.rhel7 to use OpenShift 4.22 builder images and base image instead of 4.21.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 19, 2025
@openshift-ci-robot
Copy link
Contributor

@pablintino: This pull request explicitly references no jira issue.

Details

In response to this:

- What I did

Update Dockerfile and generated Dockerfile.rhel7 to use OpenShift 4.22 builder images and base image instead of 4.21.

- How to verify it

Automated pre-submit e2e is enough.

- Description for the changelog

Update Dockerfile and generated Dockerfile.rhel7 to use OpenShift 4.22 builder images and base image instead of 4.21.

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 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 19, 2025
Update Dockerfile and generated Dockerfile.rhel7 to use OpenShift
4.22 builder images and base image instead of 4.21.
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.

/lgtm

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

openshift-ci bot commented Dec 22, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [isabella-janssen,pablintino]

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

/retitle OCPBUGS-69910: Bump OpenShift builder images to 4.22

@openshift-ci openshift-ci bot changed the title NO-ISSUE: Bump OpenShift builder images to 4.22 OCPBUGS-69910: Bump OpenShift builder images to 4.22 Dec 22, 2025
@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 Dec 22, 2025
@openshift-ci-robot
Copy link
Contributor

@pablintino: This pull request references Jira Issue OCPBUGS-69910, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.22.0) matches configured target version for branch (4.22.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sergiordlr

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

- What I did

Update Dockerfile and generated Dockerfile.rhel7 to use OpenShift 4.22 builder images and base image instead of 4.21.

- How to verify it

Automated pre-submit e2e is enough.

- Description for the changelog

Update Dockerfile and generated Dockerfile.rhel7 to use OpenShift 4.22 builder images and base image instead of 4.21.

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.

@isabella-janssen
Copy link
Member

isabella-janssen commented Dec 22, 2025

/test okd-scos-images

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 22, 2025

@isabella-janssen: 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 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-multidisk-techpreview
/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-disk-setup-techpreview
/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-main-bootstrap-unit
pull-ci-openshift-machine-config-operator-main-e2e-aws-ovn
pull-ci-openshift-machine-config-operator-main-e2e-aws-ovn-upgrade
pull-ci-openshift-machine-config-operator-main-e2e-gcp-op-1of2
pull-ci-openshift-machine-config-operator-main-e2e-gcp-op-2of2
pull-ci-openshift-machine-config-operator-main-e2e-gcp-op-single-node
pull-ci-openshift-machine-config-operator-main-e2e-hypershift
pull-ci-openshift-machine-config-operator-main-images
pull-ci-openshift-machine-config-operator-main-okd-scos-images
pull-ci-openshift-machine-config-operator-main-security
pull-ci-openshift-machine-config-operator-main-unit
pull-ci-openshift-machine-config-operator-main-verify
pull-ci-openshift-machine-config-operator-main-verify-deps
Details

In response to this:

/test okd-scos-images

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.

@isabella-janssen
Copy link
Member

/test okd-scos-images

1 similar comment
@pablintino
Copy link
Contributor Author

/test okd-scos-images

@pablintino
Copy link
Contributor Author

/override ci/prow/bootstrap-unit

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 26, 2025

@pablintino: Overrode contexts on behalf of pablintino: ci/prow/bootstrap-unit

Details

In response to this:

/override ci/prow/bootstrap-unit

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.

@pablintino
Copy link
Contributor Author

/verified by @pablintino

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Dec 26, 2025
@openshift-ci-robot
Copy link
Contributor

@pablintino: This PR has been marked as verified by @pablintino.

Details

In response to this:

/verified by @pablintino

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.

@pablintino
Copy link
Contributor Author

/override ci/prow/ci/prow/okd-scos-images

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 26, 2025

@pablintino: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • ci/prow/ci/prow/okd-scos-images

Only the following failed contexts/checkruns were expected:

  • ci/prow/bootstrap-unit
  • ci/prow/e2e-aws-ovn
  • ci/prow/e2e-aws-ovn-upgrade
  • ci/prow/e2e-gcp-op-1of2
  • ci/prow/e2e-gcp-op-2of2
  • ci/prow/e2e-gcp-op-single-node
  • ci/prow/e2e-hypershift
  • ci/prow/images
  • ci/prow/okd-scos-images
  • ci/prow/security
  • ci/prow/unit
  • ci/prow/verify
  • ci/prow/verify-deps
  • pull-ci-openshift-machine-config-operator-main-bootstrap-unit
  • pull-ci-openshift-machine-config-operator-main-e2e-aws-ovn
  • pull-ci-openshift-machine-config-operator-main-e2e-aws-ovn-upgrade
  • pull-ci-openshift-machine-config-operator-main-e2e-gcp-op-1of2
  • pull-ci-openshift-machine-config-operator-main-e2e-gcp-op-2of2
  • pull-ci-openshift-machine-config-operator-main-e2e-gcp-op-single-node
  • pull-ci-openshift-machine-config-operator-main-e2e-hypershift
  • pull-ci-openshift-machine-config-operator-main-images
  • pull-ci-openshift-machine-config-operator-main-okd-scos-images
  • pull-ci-openshift-machine-config-operator-main-security
  • pull-ci-openshift-machine-config-operator-main-unit
  • pull-ci-openshift-machine-config-operator-main-verify
  • pull-ci-openshift-machine-config-operator-main-verify-deps
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

/override ci/prow/ci/prow/okd-scos-images

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

/retest-required

Remaining retests: 0 against base HEAD 710f50d and 2 for PR HEAD bfab3ed in total

@pablintino
Copy link
Contributor Author

/override ci/prow/okd-scos-images

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 26, 2025

@pablintino: Overrode contexts on behalf of pablintino: ci/prow/okd-scos-images

Details

In response to this:

/override ci/prow/okd-scos-images

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.

@pablintino
Copy link
Contributor Author

/override ci/prow/okd-scos-images

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 26, 2025

@pablintino: Overrode contexts on behalf of pablintino: ci/prow/okd-scos-images

Details

In response to this:

/override ci/prow/okd-scos-images

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

openshift-ci bot commented Dec 26, 2025

@pablintino: all tests passed!

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 9333c5a into openshift:main Dec 26, 2025
14 checks passed
@openshift-ci-robot
Copy link
Contributor

@pablintino: Jira Issue Verification Checks: Jira Issue OCPBUGS-69910
✔️ 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-69910 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:

- What I did

Update Dockerfile and generated Dockerfile.rhel7 to use OpenShift 4.22 builder images and base image instead of 4.21.

- How to verify it

Automated pre-submit e2e is enough.

- Description for the changelog

Update Dockerfile and generated Dockerfile.rhel7 to use OpenShift 4.22 builder images and base image instead of 4.21.

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.22.0-0.nightly-2025-12-26-160536

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

4 participants