[release-4.18] OCPBUGS-51245,OCPBUGS-51227,OCPBUGS-51225: pin go-jose/[email protected] (#3550) #992

anik120 · 2025-04-24T13:44:17Z

CVE-2025-27144

Upstream-repository: operator-lifecycle-manager
Upstream-commit: dfd0b2bea85038d3c0d65348bc812d297f16b8d2

openshift-ci-robot · 2025-04-24T13:44:24Z

@anik120: This pull request references Jira Issue OCPBUGS-51225, 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 Jira Issue OCPBUGS-51225 to depend on a bug targeting a version in 4.19.0 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.

In response to this:

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.

anik120 · 2025-04-24T13:47:30Z

/jira refresh

openshift-ci-robot · 2025-04-24T13:47:34Z

@anik120: This pull request references Jira Issue OCPBUGS-51225, which is invalid:

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

In response to this:

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.

anik120 · 2025-04-24T13:59:37Z

/hold

looks like d3160ca only changed the staging directory, and not the main go.mod file (as a result the the wrong thing is being vendored in). Holding this till I and done fixing it in master -> 4.19

go.mod

anik120 · 2025-04-28T18:42:58Z

/hold cancel

Fixed the upgrade.

staging/operator-lifecycle-manager/go.mod

Upstream-repository: operator-lifecycle-manager Upstream-commit: dfd0b2bea85038d3c0d65348bc812d297f16b8d2

openshift-ci-robot · 2025-04-28T18:50:46Z

@anik120: This pull request references Jira Issue OCPBUGS-51227, 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 Jira Issue OCPBUGS-51227 to depend on a bug targeting a version in 4.19.0 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.

This pull request references Jira Issue OCPBUGS-51225, which is invalid:

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

In response to this:

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.

anik120 · 2025-04-28T19:02:28Z

/jira refresh

openshift-ci-robot · 2025-04-28T19:02:36Z

@anik120: This pull request references Jira Issue OCPBUGS-51227, which is invalid:

expected dependent Jira Issue OCPBUGS-52924 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

This pull request references Jira Issue OCPBUGS-51225, which is invalid:

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

In response to this:

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.

camilamacedo86 · 2025-04-28T19:18:01Z

go.mod

@@ -87,7 +87,7 @@ require (
 	github.com/go-git/gcfg v1.5.1-0.20230307220236-3a3c6141e376 // indirect
 	github.com/go-git/go-billy/v5 v5.6.1 // indirect
 	github.com/go-git/go-git/v5 v5.13.1 // indirect
-	github.com/go-jose/go-jose/v4 v4.0.4 // indirect
+	github.com/go-jose/go-jose/v4 v4.0.5 // indirect


It will not solve the CVE for operator-registry downstream
That is here: https://github.com/openshift/operator-framework-olm/blob/main/staging/operator-registry/go.mod#L104

We don't have to change the staging folder, all of this is incorporated by the top level go.mod file change.

openshift-ci-robot · 2025-04-28T19:27:14Z

@anik120: This pull request references Jira Issue OCPBUGS-51245, 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 Jira Issue OCPBUGS-51245 to depend on a bug targeting a version in 4.19.0 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.

This pull request references Jira Issue OCPBUGS-51227, which is invalid:

expected dependent Jira Issue OCPBUGS-52924 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

This pull request references Jira Issue OCPBUGS-51225, which is invalid:

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

In response to this:

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.

anik120 · 2025-04-28T19:28:39Z

/jira refresh

openshift-ci-robot · 2025-04-28T19:28:45Z

@anik120: This pull request references Jira Issue OCPBUGS-51245, which is invalid:

expected dependent Jira Issue OCPBUGS-52930 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

This pull request references Jira Issue OCPBUGS-51227, which is invalid:

expected dependent Jira Issue OCPBUGS-52924 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

This pull request references Jira Issue OCPBUGS-51225, which is invalid:

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

In response to this:

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.

camilamacedo86

/lgtm

openshift-ci · 2025-04-28T20:06:40Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anik120, camilamacedo86

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

~~DOWNSTREAM_OWNERS~~ [anik120]

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

openshift-ci · 2025-04-28T22:07:06Z

@anik120: 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-olm-flaky	`6fb8afa`	link	false	`/test e2e-gcp-olm-flaky`
ci/prow/okd-scos-e2e-aws-ovn	`6fb8afa`	link	false	`/test okd-scos-e2e-aws-ovn`

Full PR test history. Your PR dashboard.

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.

anik120 · 2025-04-29T13:42:00Z

/jira refresh

openshift-ci-robot · 2025-04-29T13:42:13Z

@anik120: This pull request references Jira Issue OCPBUGS-51245, 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.18.z) matches configured target version for branch (4.18.z)
bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-52930 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-52930 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

This pull request references Jira Issue OCPBUGS-51227, 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.18.z) matches configured target version for branch (4.18.z)
bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-52924 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-52924 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

This pull request references Jira Issue OCPBUGS-51225, which is invalid:

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

In response to this:

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.

anik120 · 2025-04-29T17:54:48Z

/jira refresh

openshift-ci-robot · 2025-04-29T17:54:55Z

@anik120: This pull request references Jira Issue OCPBUGS-51245, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.18.z) matches configured target version for branch (4.18.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-52930 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-52930 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

This pull request references Jira Issue OCPBUGS-51227, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.18.z) matches configured target version for branch (4.18.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-52924 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-52924 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

This pull request references Jira Issue OCPBUGS-51225, which is invalid:

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

In response to this:

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.

anik120 · 2025-05-01T15:53:21Z

/jira refresh

openshift-ci-robot · 2025-05-01T15:53:38Z

@anik120: This pull request references Jira Issue OCPBUGS-51245, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.18.z) matches configured target version for branch (4.18.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-52930 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-52930 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

This pull request references Jira Issue OCPBUGS-51227, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.18.z) matches configured target version for branch (4.18.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-52924 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-52924 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

This pull request references Jira Issue OCPBUGS-51225, 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.18.z) matches configured target version for branch (4.18.z)
bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-52923 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-52923 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira ([email protected]), skipping review request.

In response to this:

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.

bandrade · 2025-05-01T16:22:03Z

/label cherry-pick-approved

oceanc80 · 2025-05-01T18:20:47Z

/label backport-risk-assessed

openshift-ci-robot · 2025-05-01T18:25:35Z

@anik120: Jira Issue OCPBUGS-51245: All pull requests linked via external trackers have merged:

openshift/operator-framework-olm#992

Jira Issue OCPBUGS-51245 has been moved to the MODIFIED state.

Jira Issue OCPBUGS-51227: All pull requests linked via external trackers have merged:

openshift/operator-framework-olm#992

Jira Issue OCPBUGS-51227 has been moved to the MODIFIED state.

Jira Issue OCPBUGS-51225: All pull requests linked via external trackers have merged:

openshift/operator-framework-olm#992

Jira Issue OCPBUGS-51225 has been moved to the MODIFIED state.

In response to this:

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 · 2025-05-01T21:25:51Z

[ART PR BUILD NOTIFIER]

Distgit: operator-registry
This PR has been included in build operator-registry-container-v4.18.0-202505012034.p0.g3ea075d.assembly.stream.el9.
All builds following this will include this PR.

openshift-bot · 2025-05-01T21:28:49Z

[ART PR BUILD NOTIFIER]

Distgit: ose-operator-framework-tools
This PR has been included in build ose-operator-framework-tools-container-v4.18.0-202505012034.p0.g3ea075d.assembly.stream.el9.
All builds following this will include this PR.

openshift-bot · 2025-05-01T21:28:52Z

[ART PR BUILD NOTIFIER]

Distgit: operator-lifecycle-manager
This PR has been included in build operator-lifecycle-manager-container-v4.18.0-202505012034.p0.g3ea075d.assembly.stream.el9.
All builds following this will include this PR.

openshift-merge-robot · 2025-05-02T12:42:52Z

Fix included in accepted release 4.18.0-0.nightly-2025-05-02-014239

openshift-ci bot requested review from ankitathomas and perdasilva April 24, 2025 13:45

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 24, 2025

anik120 force-pushed the release-4.18-CVE-2025-27144 branch from b4503f0 to 24a5b5b Compare April 24, 2025 13:50

openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 24, 2025

camilamacedo86 reviewed Apr 28, 2025

View reviewed changes

go.mod Outdated Show resolved Hide resolved

anik120 force-pushed the release-4.18-CVE-2025-27144 branch from 24a5b5b to 9c1b1d1 Compare April 28, 2025 18:40

openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 28, 2025

camilamacedo86 reviewed Apr 28, 2025

View reviewed changes

staging/operator-lifecycle-manager/go.mod Outdated Show resolved Hide resolved

CVE-2025-27144: pin go-jose/[email protected] (#3550)

6fb8afa

Upstream-repository: operator-lifecycle-manager Upstream-commit: dfd0b2bea85038d3c0d65348bc812d297f16b8d2

anik120 force-pushed the release-4.18-CVE-2025-27144 branch from 9c1b1d1 to 6fb8afa Compare April 28, 2025 18:49

anik120 changed the title ~~[release-4.18] OCPBUGS-51225: pin go-jose/[email protected] (#3550)~~ [release-4.18] OCPBUGS-51227,OCPBUGS-51225: pin go-jose/[email protected] (#3550) Apr 28, 2025

camilamacedo86 reviewed Apr 28, 2025

View reviewed changes

anik120 changed the title ~~[release-4.18] OCPBUGS-51227,OCPBUGS-51225: pin go-jose/[email protected] (#3550)~~ [release-4.18] OCPBUGS-51245,OCPBUGS-51227,OCPBUGS-51225: pin go-jose/[email protected] (#3550) Apr 28, 2025

camilamacedo86 approved these changes Apr 28, 2025

View reviewed changes

openshift-ci bot assigned camilamacedo86 Apr 28, 2025

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 28, 2025

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 May 1, 2025

openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label May 1, 2025

openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label May 1, 2025

openshift-ci bot assigned bandrade, emmajiafan, jianzhangbjz, KeenonLee, kuiwang02 and Xia-Zhao-rh May 1, 2025

openshift-merge-bot bot merged commit 3ea075d into openshift:release-4.18 May 1, 2025
12 of 14 checks passed

[release-4.18] OCPBUGS-51245,OCPBUGS-51227,OCPBUGS-51225: pin go-jose/[email protected] (#3550) #992

[release-4.18] OCPBUGS-51245,OCPBUGS-51227,OCPBUGS-51225: pin go-jose/[email protected] (#3550) #992

Uh oh!

Conversation

anik120 commented Apr 24, 2025

Uh oh!

openshift-ci-robot commented Apr 24, 2025

Uh oh!

anik120 commented Apr 24, 2025

Uh oh!

openshift-ci-robot commented Apr 24, 2025

Uh oh!

anik120 commented Apr 24, 2025

Uh oh!

Uh oh!

anik120 commented Apr 28, 2025

Uh oh!

Uh oh!

openshift-ci-robot commented Apr 28, 2025

Uh oh!

anik120 commented Apr 28, 2025

Uh oh!

openshift-ci-robot commented Apr 28, 2025

Uh oh!

camilamacedo86 Apr 28, 2025

Choose a reason for hiding this comment

Uh oh!

anik120 Apr 28, 2025

Choose a reason for hiding this comment

Uh oh!

openshift-ci-robot commented Apr 28, 2025

Uh oh!

anik120 commented Apr 28, 2025

Uh oh!

openshift-ci-robot commented Apr 28, 2025

Uh oh!

camilamacedo86 left a comment

Choose a reason for hiding this comment

Uh oh!

openshift-ci bot commented Apr 28, 2025

Uh oh!

openshift-ci bot commented Apr 28, 2025

Uh oh!

anik120 commented Apr 29, 2025

Uh oh!

openshift-ci-robot commented Apr 29, 2025

Uh oh!

anik120 commented Apr 29, 2025

Uh oh!

openshift-ci-robot commented Apr 29, 2025

Uh oh!

anik120 commented May 1, 2025

Uh oh!

openshift-ci-robot commented May 1, 2025

Uh oh!

bandrade commented May 1, 2025

Uh oh!

oceanc80 commented May 1, 2025

Uh oh!

Uh oh!

openshift-ci-robot commented May 1, 2025

Uh oh!

openshift-bot commented May 1, 2025

Uh oh!

openshift-bot commented May 1, 2025

Uh oh!

openshift-bot commented May 1, 2025

Uh oh!

openshift-merge-robot commented May 2, 2025

Uh oh!

Uh oh!