MCO-1840: Remove MCN CRD cleanup cronjob by djoshy · Pull Request #5234 · openshift/machine-config-operator

djoshy · 2025-08-08T18:17:31Z

This removes the cronjob introduced in #5215. This PR should only be merged after the 4.21 branch has taken place.

How to verify:
(This can be done without waiting for 4.21 branch)

Launch a cluster on the latest 4.20 CI image
Verify that the MCN cron job exists post installation:

$ oc get cronjob -n openshift-machine-config-operator
NAME                               SCHEDULE    TIMEZONE   SUSPEND   ACTIVE   LAST SCHEDULE   AGE
machine-config-nodes-crd-cleanup   * * * * *   <none>     True      0        66m             66m

Upgrade to a 4.20 image with this PR
Wait for the new MCO to roll out and all nodes to be updated. The upgrade should be complete; CVO (oc get clusterversion) should no longer be progressing.
Check CVO logs to verify the delete:

I0808 17:58:56.774324       1 helper.go:65] Delete requested for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup".
I0808 17:58:56.774360       1 sync_worker.go:1056] Done syncing for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" (954 of 981)
I0808 17:58:56.774388       1 sync_worker.go:1041] Running sync for clusterrolebinding "default-account-openshift-machine-config-operator" (955 of 981)
I0808 17:58:56.813753       1 helper.go:76] Delete of clusterrolebinding "default-account-openshift-machine-config-operator" completed.
I0808 17:58:56.813786       1 sync_worker.go:1056] Done syncing for clusterrolebinding "default-account-openshift-machine-config-operator" (955 of 981)
I0808 17:58:56.813806       1 sync_worker.go:1041] Running sync for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" (956 of 981)
I0808 17:58:56.864216       1 helper.go:76] Delete of cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" completed.

Check for the cronjob:

$ oc get cronjob -n openshift-machine-config-operator
No resources found in openshift-machine-config-operator namespace.

openshift-ci-robot · 2025-08-08T18:17:35Z

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

Details

In response to this:

This removes the cronjob introduced in #5215. This PR should only be merged after the 4.21 branch has taken place.

How to verify:
(This can be done without waiting for 4.21 branch)

Launch a cluster on the latest 4.20 CI image
Verify that the MCN cron job exists post installation:

$ oc get cronjob -n openshift-machine-config-operator
NAME                               SCHEDULE    TIMEZONE   SUSPEND   ACTIVE   LAST SCHEDULE   AGE
machine-config-nodes-crd-cleanup   * * * * *   <none>     True      0        66m             66m

Upgrade to a 4.20 image with this PR
Wait for the new MCO to roll out and all nodes to be updated. The CVO (oc get clusterversion) should not longer be progressing.
Check CVO logs to verify the delete:

I0808 17:58:56.774324       1 helper.go:65] Delete requested for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup".
I0808 17:58:56.774360       1 sync_worker.go:1056] Done syncing for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" (954 of 981)
I0808 17:58:56.774388       1 sync_worker.go:1041] Running sync for clusterrolebinding "default-account-openshift-machine-config-operator" (955 of 981)
I0808 17:58:56.813753       1 helper.go:76] Delete of clusterrolebinding "default-account-openshift-machine-config-operator" completed.
I0808 17:58:56.813786       1 sync_worker.go:1056] Done syncing for clusterrolebinding "default-account-openshift-machine-config-operator" (955 of 981)
I0808 17:58:56.813806       1 sync_worker.go:1041] Running sync for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" (956 of 981)
I0808 17:58:56.864216       1 helper.go:76] Delete of cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" completed.

Check for the cronjob:

$ oc get cronjob
No resources found in openshift-machine-config-operator namespace.

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.

djoshy · 2025-08-08T18:18:26Z

/hold

Throwing in a hold while we wait for the branch.

isabella-janssen · 2025-08-11T14:27:35Z

/retitle OCPBUGS-60306: Remove MCN CRD cleanup cronjob

openshift-ci-robot · 2025-08-11T14:27:43Z

@djoshy: This pull request references Jira Issue OCPBUGS-60306, which is invalid:

expected the bug to target either version "4.20." or "openshift-4.20.", but it targets "4.21" 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.

Details

In response to this:

This removes the cronjob introduced in #5215. This PR should only be merged after the 4.21 branch has taken place.

How to verify:
(This can be done without waiting for 4.21 branch)

Launch a cluster on the latest 4.20 CI image
Verify that the MCN cron job exists post installation:

$ oc get cronjob -n openshift-machine-config-operator
NAME                               SCHEDULE    TIMEZONE   SUSPEND   ACTIVE   LAST SCHEDULE   AGE
machine-config-nodes-crd-cleanup   * * * * *   <none>     True      0        66m             66m

Upgrade to a 4.20 image with this PR
Wait for the new MCO to roll out and all nodes to be updated. The upgrade should be complete; CVO (oc get clusterversion) should no longer be progressing.
Check CVO logs to verify the delete:

I0808 17:58:56.774324       1 helper.go:65] Delete requested for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup".
I0808 17:58:56.774360       1 sync_worker.go:1056] Done syncing for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" (954 of 981)
I0808 17:58:56.774388       1 sync_worker.go:1041] Running sync for clusterrolebinding "default-account-openshift-machine-config-operator" (955 of 981)
I0808 17:58:56.813753       1 helper.go:76] Delete of clusterrolebinding "default-account-openshift-machine-config-operator" completed.
I0808 17:58:56.813786       1 sync_worker.go:1056] Done syncing for clusterrolebinding "default-account-openshift-machine-config-operator" (955 of 981)
I0808 17:58:56.813806       1 sync_worker.go:1041] Running sync for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" (956 of 981)
I0808 17:58:56.864216       1 helper.go:76] Delete of cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" completed.

Check for the cronjob:

$ oc get cronjob -n openshift-machine-config-operator
No resources found in openshift-machine-config-operator namespace.

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 · 2025-08-11T14:36:19Z

@djoshy: This pull request references MCO-1840 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

Details

In response to this:

This removes the cronjob introduced in #5215. This PR should only be merged after the 4.21 branch has taken place.

How to verify:
(This can be done without waiting for 4.21 branch)

Launch a cluster on the latest 4.20 CI image
Verify that the MCN cron job exists post installation:

$ oc get cronjob -n openshift-machine-config-operator
NAME                               SCHEDULE    TIMEZONE   SUSPEND   ACTIVE   LAST SCHEDULE   AGE
machine-config-nodes-crd-cleanup   * * * * *   <none>     True      0        66m             66m

Upgrade to a 4.20 image with this PR
Wait for the new MCO to roll out and all nodes to be updated. The upgrade should be complete; CVO (oc get clusterversion) should no longer be progressing.
Check CVO logs to verify the delete:

I0808 17:58:56.774324       1 helper.go:65] Delete requested for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup".
I0808 17:58:56.774360       1 sync_worker.go:1056] Done syncing for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" (954 of 981)
I0808 17:58:56.774388       1 sync_worker.go:1041] Running sync for clusterrolebinding "default-account-openshift-machine-config-operator" (955 of 981)
I0808 17:58:56.813753       1 helper.go:76] Delete of clusterrolebinding "default-account-openshift-machine-config-operator" completed.
I0808 17:58:56.813786       1 sync_worker.go:1056] Done syncing for clusterrolebinding "default-account-openshift-machine-config-operator" (955 of 981)
I0808 17:58:56.813806       1 sync_worker.go:1041] Running sync for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" (956 of 981)
I0808 17:58:56.864216       1 helper.go:76] Delete of cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" completed.

Check for the cronjob:

$ oc get cronjob -n openshift-machine-config-operator
No resources found in openshift-machine-config-operator namespace.

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 · 2025-09-02T15:16:44Z

/lgtm

Now that 4.20 branching is complete, this PR should be ready to go & it looks fair to me!

openshift-ci · 2025-09-02T15:25:28Z

[APPROVALNOTIFIER] This PR is APPROVED

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

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

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

djoshy · 2025-09-02T15:46:38Z

/test all

djoshy · 2025-09-10T19:06:21Z

/test all

openshift-ci · 2025-09-10T23:54:14Z

@djoshy: 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-azure-ovn-upgrade	`d88959a`	link	false	`/test e2e-azure-ovn-upgrade`
ci/prow/e2e-aws-serial	`d88959a`	link	false	`/test e2e-aws-serial`
ci/prow/e2e-azure-ovn-upgrade-out-of-change	`715f38d`	link	false	`/test e2e-azure-ovn-upgrade-out-of-change`
ci/prow/e2e-gcp-mco-disruptive	`715f38d`	link	false	`/test e2e-gcp-mco-disruptive`
ci/prow/e2e-gcp-op-ocl	`715f38d`	link	false	`/test e2e-gcp-op-ocl`
ci/prow/bootstrap-unit	`715f38d`	link	false	`/test bootstrap-unit`
ci/prow/e2e-aws-mco-disruptive	`715f38d`	link	false	`/test e2e-aws-mco-disruptive`

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.

djoshy · 2025-09-17T18:19:44Z

/unhold

ptalgulk01 · 2025-09-18T07:25:30Z

Pre-merge verified:

Deployed 4.20 cluster with IPI based AWS.

Able to see cronjob exist for mcn-cleanup

$ oc get cronjob -n openshift-machine-config-operator 
NAME                               SCHEDULE    TIMEZONE   SUSPEND   ACTIVE   LAST SCHEDULE   AGE
machine-config-nodes-crd-cleanup   * * * * *   <none>     True      0        87m             88m

$ oc logs cluster-version-operator-69964fb5b9-4t2r7  -n openshift-cluster-version
I0918 05:00:08.537224       1 sync_worker.go:1056] Done syncing for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" (810 of 956)
I0918 05:00:08.189767       1 sync_worker.go:1041] Running sync for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" (810 of 956)

Upgrade the cluster to this 4.21 PR image

$ oc adm upgrade --to-image=registry.build11.ci.openshift.org/ci-ln-lybh0dt/release:latest --allow-explicit-upgrade  --force

When upgrade is on MCO operator check the CVO pod log

$ oc get clusterversion
NAME      VERSION                         AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.20.0-0.ci-2025-09-17-211301   True        True          63m     Working towards 4.21.0-0-2025-09-17-141021-test-ci-ln-lybh0dt-latest: 823 of 956 done (86% complete), waiting on machine-config

$ oc logs cluster-version-operator-765f7b5865-pt2xq -n openshift-cluster-version | grep -i cronjob
I0918 07:07:27.395848       1 sync_worker.go:1041] Running sync for cronjob "openshift-operator-lifecycle-manager/collect-profiles" (714 of 956)
I0918 07:07:27.546124       1 sync_worker.go:1056] Done syncing for cronjob "openshift-operator-lifecycle-manager/collect-profiles" (714 of 956) 
I0918 07:08:09.643962       1 sync_worker.go:1041] Running sync for cronjob "openshift-operator-lifecycle-manager/collect-profiles" (714 of 956)
I0918 07:08:09.794371       1 sync_worker.go:1056] Done syncing for cronjob "openshift-operator-lifecycle-manager/collect-profiles" (714 of 956)
I0918 07:10:44.042710       1 sync_worker.go:1041] Running sync for cronjob "openshift-operator-lifecycle-manager/collect-profiles" (714 of 956)
I0918 07:10:44.192199       1 sync_worker.go:1056] Done syncing for cronjob "openshift-operator-lifecycle-manager/collect-profiles" (714 of 956)
I0918 07:14:11.612403       1 sync_worker.go:1041] Running sync for cronjob "openshift-operator-lifecycle-manager/collect-profiles" (714 of 956)
I0918 07:14:11.762993       1 sync_worker.go:1056] Done syncing for cronjob "openshift-operator-lifecycle-manager/collect-profiles" (714 of 956)
I0918 07:14:23.962373       1 sync_worker.go:1041] Running sync for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" (931 of 956)
I0918 07:14:24.265123       1 helper.go:65] Delete requested for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup".
I0918 07:14:24.265152       1 sync_worker.go:1056] Done syncing for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" (931 of 956)

After upfrade of cluster no resources related mcn-cleanup-crd seen.

$ oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.21.0-0-2025-09-17-141021-test-ci-ln-lybh0dt-latest   True        False         2m21s   Cluster version is 4.21.0-0-2025-09-17-141021-test-ci-ln-lybh0dt-latest

$ oc get cronjob -n openshift-machine-config-operator
No resources found in openshift-machine-config-operator namespace.

$  oc get pods -n openshift-machine-config-operator | grep cleanup
empty

/label qe-approved
/verified by @ptalgulk01

openshift-ci-robot · 2025-09-18T07:25:43Z

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

Details

In response to this:

Pre-merge verified:

Deployed 4.20 cluster with IPI based AWS.

Able to see cronjob exist for mcn-cleanup

$ oc get cronjob -n openshift-machine-config-operator 
NAME                               SCHEDULE    TIMEZONE   SUSPEND   ACTIVE   LAST SCHEDULE   AGE
machine-config-nodes-crd-cleanup   * * * * *   <none>     True      0        87m             88m

$ oc logs cluster-version-operator-69964fb5b9-4t2r7  -n openshift-cluster-version
I0918 05:00:08.537224       1 sync_worker.go:1056] Done syncing for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" (810 of 956)
I0918 05:00:08.189767       1 sync_worker.go:1041] Running sync for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" (810 of 956)

Upgrade the cluster to this 4.21 PR image

$ oc adm upgrade --to-image=registry.build11.ci.openshift.org/ci-ln-lybh0dt/release:latest --allow-explicit-upgrade  --force

When upgrade is on MCO operator check the CVO pod log

$ oc get clusterversion
NAME      VERSION                         AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.20.0-0.ci-2025-09-17-211301   True        True          63m     Working towards 4.21.0-0-2025-09-17-141021-test-ci-ln-lybh0dt-latest: 823 of 956 done (86% complete), waiting on machine-config

$ oc logs cluster-version-operator-765f7b5865-pt2xq -n openshift-cluster-version | grep -i cronjob
I0918 07:07:27.395848       1 sync_worker.go:1041] Running sync for cronjob "openshift-operator-lifecycle-manager/collect-profiles" (714 of 956)
I0918 07:07:27.546124       1 sync_worker.go:1056] Done syncing for cronjob "openshift-operator-lifecycle-manager/collect-profiles" (714 of 956)
I0918 07:08:09.643962       1 sync_worker.go:1041] Running sync for cronjob "openshift-operator-lifecycle-manager/collect-profiles" (714 of 956)
I0918 07:08:09.794371       1 sync_worker.go:1056] Done syncing for cronjob "openshift-operator-lifecycle-manager/collect-profiles" (714 of 956)
I0918 07:10:44.042710       1 sync_worker.go:1041] Running sync for cronjob "openshift-operator-lifecycle-manager/collect-profiles" (714 of 956)
I0918 07:10:44.192199       1 sync_worker.go:1056] Done syncing for cronjob "openshift-operator-lifecycle-manager/collect-profiles" (714 of 956)
I0918 07:14:11.612403       1 sync_worker.go:1041] Running sync for cronjob "openshift-operator-lifecycle-manager/collect-profiles" (714 of 956)
I0918 07:14:11.762993       1 sync_worker.go:1056] Done syncing for cronjob "openshift-operator-lifecycle-manager/collect-profiles" (714 of 956)
I0918 07:14:23.962373       1 sync_worker.go:1041] Running sync for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" (931 of 956)
I0918 07:14:24.265123       1 helper.go:65] Delete requested for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup".
I0918 07:14:24.265152       1 sync_worker.go:1056] Done syncing for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" (931 of 956)

$ oc get cronjob -n openshift-machine-config-operator
No resources found in openshift-machine-config-operator namespace.

$  oc get pods -n openshift-machine-config-operator | grep cleanup
empty

/label qe-approved
/verified by @ptalgulk01

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.

ptalgulk01 · 2025-09-18T07:26:19Z

/label qe-approved

openshift-ci-robot · 2025-09-18T07:26:25Z

@djoshy: This pull request references MCO-1840 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.21.0" version, but no target version was set.

Details

In response to this:

This removes the cronjob introduced in #5215. This PR should only be merged after the 4.21 branch has taken place.

How to verify:
(This can be done without waiting for 4.21 branch)

Launch a cluster on the latest 4.20 CI image
Verify that the MCN cron job exists post installation:

$ oc get cronjob -n openshift-machine-config-operator
NAME                               SCHEDULE    TIMEZONE   SUSPEND   ACTIVE   LAST SCHEDULE   AGE
machine-config-nodes-crd-cleanup   * * * * *   <none>     True      0        66m             66m

Upgrade to a 4.20 image with this PR
Wait for the new MCO to roll out and all nodes to be updated. The upgrade should be complete; CVO (oc get clusterversion) should no longer be progressing.
Check CVO logs to verify the delete:

I0808 17:58:56.774324       1 helper.go:65] Delete requested for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup".
I0808 17:58:56.774360       1 sync_worker.go:1056] Done syncing for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" (954 of 981)
I0808 17:58:56.774388       1 sync_worker.go:1041] Running sync for clusterrolebinding "default-account-openshift-machine-config-operator" (955 of 981)
I0808 17:58:56.813753       1 helper.go:76] Delete of clusterrolebinding "default-account-openshift-machine-config-operator" completed.
I0808 17:58:56.813786       1 sync_worker.go:1056] Done syncing for clusterrolebinding "default-account-openshift-machine-config-operator" (955 of 981)
I0808 17:58:56.813806       1 sync_worker.go:1041] Running sync for cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" (956 of 981)
I0808 17:58:56.864216       1 helper.go:76] Delete of cronjob "openshift-machine-config-operator/machine-config-nodes-crd-cleanup" completed.

Check for the cronjob:

$ oc get cronjob -n openshift-machine-config-operator
No resources found in openshift-machine-config-operator namespace.

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 added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 8, 2025

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

openshift-ci Bot requested review from RishabhSaini and umohnani8 August 8, 2025 18:19

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 8, 2025

openshift-ci Bot changed the title ~~NO-ISSUE: Remove MCN CRD cleanup cronjob~~ OCPBUGS-60306: Remove MCN CRD cleanup cronjob Aug 11, 2025

openshift-ci-robot added the jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. label Aug 11, 2025

openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Aug 11, 2025

djoshy changed the title ~~OCPBUGS-60306: Remove MCN CRD cleanup cronjob~~ MCO-1840: Remove MCN CRD cleanup cronjob Aug 11, 2025

openshift-ci-robot removed the jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. label Aug 11, 2025

openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Aug 11, 2025

djoshy force-pushed the delete-mcn-cron-job branch from d88959a to 31e8108 Compare August 12, 2025 12:58

install: remove mcn crd cleanup cronjob

715f38d

djoshy force-pushed the delete-mcn-cron-job branch from 31e8108 to 715f38d Compare August 12, 2025 13:03

openshift-ci Bot assigned isabella-janssen Sep 2, 2025

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Sep 2, 2025

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

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 18, 2025

openshift-ci Bot added the qe-approved Signifies that QE has signed off on this PR label Sep 18, 2025

openshift-merge-bot Bot merged commit 223bed0 into openshift:main Sep 18, 2025
17 of 22 checks passed

djoshy deleted the delete-mcn-cron-job branch September 22, 2025 14:40

Conversation

djoshy commented Aug 8, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Aug 8, 2025

Uh oh!

djoshy commented Aug 8, 2025

Uh oh!

isabella-janssen commented Aug 11, 2025

Uh oh!

openshift-ci-robot commented Aug 11, 2025

Uh oh!

openshift-ci-robot commented Aug 11, 2025 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

isabella-janssen commented Sep 2, 2025

Uh oh!

openshift-ci Bot commented Sep 2, 2025

Uh oh!

djoshy commented Sep 2, 2025

Uh oh!

djoshy commented Sep 10, 2025

Uh oh!

openshift-ci Bot commented Sep 10, 2025

Uh oh!

djoshy commented Sep 17, 2025

Uh oh!

ptalgulk01 commented Sep 18, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Sep 18, 2025

Uh oh!

ptalgulk01 commented Sep 18, 2025

Uh oh!

openshift-ci-robot commented Sep 18, 2025 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

djoshy commented Aug 8, 2025 •

edited

Loading

openshift-ci-robot commented Aug 11, 2025 •

edited by openshift-ci Bot

Loading

ptalgulk01 commented Sep 18, 2025 •

edited

Loading

openshift-ci-robot commented Sep 18, 2025 •

edited by openshift-ci Bot

Loading