Skip to content

Conversation

@ibihim
Copy link

@ibihim ibihim commented Jan 14, 2026

Summary

This PR is a rebased version of #271, which was stuck due to e2e-component test failures.

Original PR: #271
Original Author: AOS Automation Release Team (openshift-bot)

Change

Updates the Dockerfile builder image from Go 1.20 to Go 1.21 for OpenShift 4.16 ART consistency.

-FROM registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.20-openshift-4.16 AS builder
+FROM registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.21-openshift-4.16 AS builder

Context

Reconciling with https://github.com/openshift/ocp-build-data/tree/b7ba6c3881993b1c2e0a96905cce738d604e1f1d/images/golang-github-openshift-oauth-proxy.yml

/cc @openshift-bot

@openshift-ci openshift-ci bot requested a review from openshift-bot January 14, 2026 13:48
@openshift-ci-robot openshift-ci-robot added 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 14, 2026
@openshift-ci-robot
Copy link

@ibihim: This pull request references Jira Issue OCPBUGS-25776, which is invalid:

  • expected the bug to be open, but it isn't
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Obsolete) instead
  • expected Jira Issue OCPBUGS-25776 to depend on a bug targeting a version in 4.17.0, 4.17.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

Summary

This PR is a rebased version of #271, which was stuck due to e2e-component test failures.

Original PR: #271
Original Author: AOS Automation Release Team (openshift-bot)

Change

Updates the Dockerfile builder image from Go 1.20 to Go 1.21 for OpenShift 4.16 ART consistency.

-FROM registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.20-openshift-4.16 AS builder
+FROM registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.21-openshift-4.16 AS builder

Context

Reconciling with https://github.com/openshift/ocp-build-data/tree/b7ba6c3881993b1c2e0a96905cce738d604e1f1d/images/golang-github-openshift-oauth-proxy.yml

/cc @openshift-bot

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

openshift-ci bot commented Jan 14, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ibihim
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@ibihim ibihim changed the title OCPBUGS-25776: Updating golang-github-openshift-oauth-proxy-container image for ART 4.16 (rebased) OCPBUGS-25776: NO-ISSUE: Updating golang-github-openshift-oauth-proxy-container image to be consistent with ART for 4.16 Jan 14, 2026
@ibihim ibihim changed the title OCPBUGS-25776: NO-ISSUE: Updating golang-github-openshift-oauth-proxy-container image to be consistent with ART for 4.16 OCPBUGS-25776: Updating golang-github-openshift-oauth-proxy-container image to be consistent with ART for 4.16 Jan 14, 2026
@ibihim ibihim changed the title OCPBUGS-25776: Updating golang-github-openshift-oauth-proxy-container image to be consistent with ART for 4.16 NO-JIRA: Updating golang-github-openshift-oauth-proxy-container image to be consistent with ART for 4.16 Jan 14, 2026
@openshift-ci-robot
Copy link

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

Details

In response to this:

Summary

This PR is a rebased version of #271, which was stuck due to e2e-component test failures.

Original PR: #271
Original Author: AOS Automation Release Team (openshift-bot)

Change

Updates the Dockerfile builder image from Go 1.20 to Go 1.21 for OpenShift 4.16 ART consistency.

-FROM registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.20-openshift-4.16 AS builder
+FROM registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.21-openshift-4.16 AS builder

Context

Reconciling with https://github.com/openshift/ocp-build-data/tree/b7ba6c3881993b1c2e0a96905cce738d604e1f1d/images/golang-github-openshift-oauth-proxy.yml

/cc @openshift-bot

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

openshift-ci bot commented Jan 14, 2026

@ibihim: 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-component e62c006 link true /test e2e-component

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

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