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.

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

openshift-ci bot commented Dec 19, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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:

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 Dec 19, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 19, 2025

@pablintino: 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-gcp-op-single-node 111f9ee link true /test e2e-gcp-op-single-node
ci/prow/e2e-gcp-op-1of2 111f9ee link true /test e2e-gcp-op-1of2
ci/prow/bootstrap-unit 111f9ee link false /test bootstrap-unit
ci/prow/e2e-aws-ovn 111f9ee link true /test e2e-aws-ovn
ci/prow/e2e-gcp-op-2of2 111f9ee link true /test e2e-gcp-op-2of2
ci/prow/e2e-hypershift 111f9ee link true /test e2e-hypershift

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.

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-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants