NO-JIRA: Updating golang-github-openshift-oauth-proxy-container image to be consistent with ART for 4.16

[ibihim]

Summary

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

• Cherry-picked the original commit from OCPBUGS-25776: NO-ISSUE: Updating golang-github-openshift-oauth-proxy-container image to be consistent with ART for 4.16 #271 (authored by AOS Automation Release Team)
• Rebased onto current release-4.16 which includes the e2e-component test fix (bf6476f)

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-robot]

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

• Cherry-picked the original commit from OCPBUGS-25776: NO-ISSUE: Updating golang-github-openshift-oauth-proxy-container image to be consistent with ART for 4.16 #271 (authored by AOS Automation Release Team)
• Rebased onto current release-4.16 which includes the e2e-component test fix (bf6476f)

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]

[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:

• OWNERS

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

[openshift-ci-robot]

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

• Cherry-picked the original commit from OCPBUGS-25776: NO-ISSUE: Updating golang-github-openshift-oauth-proxy-container image to be consistent with ART for 4.16 #271 (authored by AOS Automation Release Team)
• Rebased onto current release-4.16 which includes the e2e-component test fix (bf6476f)

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-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: b8a8ae89-137e-4ea6-93c8-499a469d0830

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

@ibihim: 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-component	e62c006	link	true	/test e2e-component
ci/prow/unit	26744fd	link	true	/test unit

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.