Testing2 by Prucek · Pull Request #2 · Prucek/release

Prucek · 2024-02-08T13:54:34Z

/hold

openshift-ci · 2024-02-08T13:55:47Z

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Prucek

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

Prucek · 2024-02-08T14:26:48Z

/pj-rehearse periodic-ci-openshift-ci-tools-master-canary-build03

Prucek · 2024-02-08T14:50:33Z

/pj-rehearse periodic-ci-openshift-ci-tools-master-canary-build03

openshift-ci-robot · 2024-02-09T09:22:28Z

@Prucek, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

could not load configuration from candidate revision of release repo: failed to load ci-operator configuration from release repo: failed to load ci-operator config (error unmarshaling JSON: json: cannot unmarshal number into Go struct field ImageStreamTagReference.base_images.tag of type string)

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 10 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 20 rehearsals
Comment: /pj-rehearse max to run up to 35 rehearsals
Comment: /pj-rehearse auto-ack to run up to 10 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

Prucek · 2024-02-09T09:26:22Z

/pj-rehearse periodic-ci-openshift-ci-tools-master-canary-build03

Prucek · 2024-02-13T14:04:45Z

/pj-rehearse periodic-ci-openshift-ci-tools-master-canary-build03

Prucek · 2024-02-13T14:46:10Z

/pj-rehearse periodic-ci-openshift-ci-tools-master-canary-build03

Prucek · 2024-02-13T15:00:06Z

/pj-rehearse periodic-ci-openshift-ci-tools-master-canary-build03

openshift-ci-robot · 2024-02-13T15:21:37Z

@Prucek, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

could not load configuration from candidate revision of release repo: failed to load ci-operator configuration from release repo: invalid ci-operator config: configuration has 4 errors:

 * promotion: no namespace defined
 * promotion: no name or tag defined
 * promotion.to[0]: no namespace defined
 * promotion.to[0]: no name or tag defined

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 10 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 20 rehearsals
Comment: /pj-rehearse max to run up to 35 rehearsals
Comment: /pj-rehearse auto-ack to run up to 10 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

openshift-ci-robot · 2024-02-13T15:35:52Z

@Prucek, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

could not load configuration from candidate revision of release repo: failed to load ci-operator configuration from release repo: [invalid ci-operator config: configuration has 4 errors:

 * promotion: no namespace defined
 * promotion: no name or tag defined
 * promotion.to[0]: no namespace defined
 * promotion.to[0]: no name or tag defined
, invalid ci-operator config: configuration has 3 errors:

 * tests[0]: invalid cluster profile "quay-aws"
 * tests[1]: invalid cluster profile "quay-aws"
 * tests[2]: invalid cluster profile "quay-aws"
, invalid ci-operator config: configuration has 6 errors:

 * promotion: no namespace defined
 * promotion: no name or tag defined
 * promotion.to[0]: no namespace defined
 * promotion.to[0]: no name or tag defined
 * tests[3]: invalid cluster profile "quay-aws"
 * tests[4]: invalid cluster profile "quay-aws"
, invalid ci-operator config: configuration has 15 errors:

 * tests[0]: invalid cluster profile "quay-aws"
 * tests[1]: invalid cluster profile "quay-aws"
 * tests[2]: invalid cluster profile "quay-aws"
 * tests[3]: invalid cluster profile "quay-aws"
 * tests[4]: invalid cluster profile "quay-aws"
 * tests[5]: invalid cluster profile "quay-aws"
 * tests[6]: invalid cluster profile "quay-aws"
 * tests[7]: invalid cluster profile "quay-aws"
 * tests[8]: invalid cluster profile "quay-aws"
 * tests[9]: invalid cluster profile "quay-aws"
 * tests[10]: invalid cluster profile "quay-aws"
 * tests[11]: invalid cluster profile "quay-aws"
 * tests[12]: invalid cluster profile "quay-aws"
 * tests[13]: invalid cluster profile "quay-aws"
 * tests[14]: invalid cluster profile "quay-aws"
, invalid ci-operator config: configuration has 30 errors:

 * tests[0]: invalid cluster profile "quay-aws"
 * tests[1]: invalid cluster profile "quay-aws"
 * tests[2]: invalid cluster profile "quay-aws"
 * tests[3]: invalid cluster profile "quay-aws"
 * tests[4]: invalid cluster profile "quay-aws"
 * tests[5]: invalid cluster profile "quay-aws"
 * tests[6]: invalid cluster profile "quay-aws"
 * tests[7]: invalid cluster profile "quay-aws"
 * tests[8]: invalid cluster profile "quay-aws"
 * tests[9]: invalid cluster profile "quay-aws"
 * tests[10]: invalid cluster profile "quay-aws"
 * tests[11]: invalid cluster profile "quay-aws"
 * tests[12]: invalid cluster profile "quay-aws"
 * tests[13]: invalid cluster profile "quay-aws"
 * tests[14]: invalid cluster profile "quay-aws"
 * tests[15]: invalid cluster profile "quay-aws"
 * tests[16]: invalid cluster profile "quay-aws"
 * tests[17]: invalid cluster profile "quay-aws"
 * tests[18]: invalid cluster profile "quay-aws"
 * tests[19]: invalid cluster profile "quay-aws"
 * tests[20]: invalid cluster profile "quay-aws"
 * tests[21]: invalid cluster profile "quay-aws"
 * tests[22]: invalid cluster profile "quay-aws"
 * tests[23]: invalid cluster profile "quay-aws"
 * tests[24]: invalid cluster profile "quay-aws"
 * tests[25]: invalid cluster profile "quay-aws"
 * tests[26]: invalid cluster profile "quay-aws"
 * tests[27]: invalid cluster profile "quay-aws"
 * tests[28]: invalid cluster profile "quay-aws"
 * tests[29]: invalid cluster profile "quay-aws"
, invalid ci-operator config: configuration has 2 errors:

 * tests[0]: invalid cluster profile "che-aws"
 * tests[1]: invalid cluster profile "che-aws"
, invalid ci-operator config: configuration has 3 errors:

 * tests[0]: invalid cluster profile "osl-gcp"
 * tests[1]: invalid cluster profile "osl-gcp"
 * tests[2]: invalid cluster profile "osl-gcp"
, invalid ci-operator config: invalid configuration: tests[0]: invalid cluster profile "che-aws", invalid ci-operator config: configuration has 4 errors:

 * tests[0]: invalid cluster profile "che-aws"
 * tests[1]: invalid cluster profile "che-aws"
 * tests[2]: invalid cluster profile "che-aws"
 * tests[3]: invalid cluster profile "che-aws"
, invalid ci-operator config: configuration has 19 errors:

 * tests[0]: invalid cluster profile "che-aws"
 * tests[1]: invalid cluster profile "che-aws"
 * tests[2]: invalid cluster profile "che-aws"
 * tests[3]: invalid cluster profile "che-aws"
 * tests[4]: invalid cluster profile "che-aws"
 * tests[5]: invalid cluster profile "che-aws"
 * tests[6]: invalid cluster profile "che-aws"
 * tests[7]: invalid cluster profile "che-aws"
 * tests[8]: invalid cluster profile "che-aws"
 * tests[9]: invalid cluster profile "che-aws"
 * tests[10]: invalid cluster profile "che-aws"
 * tests[11]: invalid cluster profile "che-aws"
 * tests[12]: invalid cluster profile "che-aws"
 * tests[13]: invalid cluster profile "che-aws"
 * tests[14]: invalid cluster profile "che-aws"
 * tests[15]: invalid cluster profile "che-aws"
 * tests[16]: invalid cluster profile "che-aws"
 * tests[17]: invalid cluster profile "che-aws"
 * tests[18]: invalid cluster profile "che-aws"
, invalid ci-operator config: invalid configuration: tests[1]: invalid cluster profile "medik8s-aws", invalid ci-operator config: invalid configuration: tests[0]: invalid cluster profile "medik8s-aws", invalid ci-operator config: configuration has 6 errors:

 * promotion: no namespace defined
 * promotion: no name or tag defined
 * promotion.to[0]: no namespace defined
 * promotion.to[0]: no name or tag defined
 * promotion.to[1]: no namespace defined
 * promotion.to[1]: no name or tag defined
, invalid ci-operator config: invalid configuration: tests[1]: invalid cluster profile "aws-outpost-qe", invalid ci-operator config: configuration has 5 errors:

 * tests[25]: invalid cluster profile "aws-outpost-qe"
 * tests[26]: invalid cluster profile "aws-outpost-qe"
 * tests[27]: invalid cluster profile "aws-outpost-qe"
 * tests[201]: invalid cluster profile "nutanix-qe-zone"
 * tests[202]: invalid cluster profile "nutanix-qe-zone"
, invalid ci-operator config: configuration has 5 errors:

 * tests[22]: invalid cluster profile "aws-outpost-qe"
 * tests[23]: invalid cluster profile "aws-outpost-qe"
 * tests[24]: invalid cluster profile "aws-outpost-qe"
 * tests[189]: invalid cluster profile "nutanix-qe-zone"
 * tests[190]: invalid cluster profile "nutanix-qe-zone"
, invalid ci-operator config: configuration has 5 errors:

 * you must define at least one test or image build in 'tests' or 'images'
 * promotion: no namespace defined
 * promotion: no name or tag defined
 * promotion.to[0]: no namespace defined
 * promotion.to[0]: no name or tag defined
, invalid ci-operator config: configuration has 61 errors:

 * tests[0]: invalid cluster profile "aws-pipelines-performance"
 * tests[1]: invalid cluster profile "aws-pipelines-performance"
 * tests[2]: invalid cluster profile "aws-pipelines-performance"
 * tests[3]: invalid cluster profile "aws-pipelines-performance"
 * tests[4]: invalid cluster profile "aws-pipelines-performance"
 * tests[5]: invalid cluster profile "aws-pipelines-performance"
 * tests[6]: invalid cluster profile "aws-pipelines-performance"
 * tests[7]: invalid cluster profile "aws-pipelines-performance"
 * tests[8]: invalid cluster profile "aws-pipelines-performance"
 * tests[9]: invalid cluster profile "aws-pipelines-performance"
 * tests[10]: invalid cluster profile "aws-pipelines-performance"
 * tests[11]: invalid cluster profile "aws-pipelines-performance"
 * tests[12]: invalid cluster profile "aws-pipelines-performance"
 * tests[13]: invalid cluster profile "aws-pipelines-performance"
 * tests[14]: invalid cluster profile "aws-pipelines-performance"
 * tests[15]: invalid cluster profile "aws-pipelines-performance"
 * tests[16]: invalid cluster profile "aws-pipelines-performance"
 * tests[17]: invalid cluster profile "aws-pipelines-performance"
 * tests[18]: invalid cluster profile "aws-pipelines-performance"
 * tests[19]: invalid cluster profile "aws-pipelines-performance"
 * tests[20]: invalid cluster profile "aws-pipelines-performance"
 * tests[21]: invalid cluster profile "aws-pipelines-performance"
 * tests[22]: invalid cluster profile "aws-pipelines-performance"
 * tests[23]: invalid cluster profile "aws-pipelines-performance"
 * tests[24]: invalid cluster profile "aws-pipelines-performance"
 * tests[25]: invalid cluster profile "aws-pipelines-performance"
 * tests[26]: invalid cluster profile "aws-pipelines-performance"
 * tests[27]: invalid cluster profile "aws-pipelines-performance"
 * tests[28]: invalid cluster profile "aws-pipelines-performance"
 * tests[29]: invalid cluster profile "aws-pipelines-performance"
 * tests[30]: invalid cluster profile "aws-pipelines-performance"
 * tests[31]: invalid cluster profile "aws-pipelines-performance"
 * tests[32]: invalid cluster profile "aws-pipelines-performance"
 * tests[33]: invalid cluster profile "aws-pipelines-performance"
 * tests[34]: invalid cluster profile "aws-pipelines-performance"
 * tests[35]: invalid cluster profile "aws-pipelines-performance"
 * tests[36]: invalid cluster profile "aws-pipelines-performance"
 * tests[37]: invalid cluster profile "aws-pipelines-performance"
 * tests[38]: invalid cluster profile "aws-pipelines-performance"
 * tests[39]: invalid cluster profile "aws-pipelines-performance"
 * tests[40]: invalid cluster profile "aws-pipelines-performance"
 * tests[41]: invalid cluster profile "aws-pipelines-performance"
 * tests[42]: invalid cluster profile "aws-pipelines-performance"
 * tests[43]: invalid cluster profile "aws-pipelines-performance"
 * tests[44]: invalid cluster profile "aws-pipelines-performance"
 * tests[45]: invalid cluster profile "aws-pipelines-performance"
 * tests[46]: invalid cluster profile "aws-pipelines-performance"
 * tests[47]: invalid cluster profile "aws-pipelines-performance"
 * tests[48]: invalid cluster profile "aws-pipelines-performance"
 * tests[49]: invalid cluster profile "aws-pipelines-performance"
 * tests[50]: invalid cluster profile "aws-pipelines-performance"
 * tests[51]: invalid cluster profile "aws-pipelines-performance"
 * tests[52]: invalid cluster profile "aws-pipelines-performance"
 * tests[53]: invalid cluster profile "aws-pipelines-performance"
 * tests[54]: invalid cluster profile "aws-pipelines-performance"
 * tests[55]: invalid cluster profile "aws-pipelines-performance"
 * tests[56]: invalid cluster profile "aws-pipelines-performance"
 * tests[57]: invalid cluster profile "aws-pipelines-performance"
 * tests[58]: invalid cluster profile "aws-pipelines-performance"
 * tests[59]: invalid cluster profile "aws-pipelines-performance"
 * tests[60]: invalid cluster profile "aws-pipelines-performance"
, invalid ci-operator config: invalid configuration: tests[0]: invalid cluster profile "gitops-aws", invalid ci-operator config: configuration has 3 errors:

 * tests[0]: invalid cluster profile "gitops-aws"
 * tests[1]: invalid cluster profile "gitops-aws"
 * tests[2]: invalid cluster profile "gitops-aws"
, invalid ci-operator config: invalid configuration: tests[2]: invalid cluster profile "gitops-aws", invalid ci-operator config: configuration has 7 errors:

 * promotion: no namespace defined
 * promotion: no name or tag defined
 * promotion.to[0]: no namespace defined
 * promotion.to[0]: no name or tag defined
 * tests[1]: invalid cluster profile "aws-edge-infra"
 * tests[2]: invalid cluster profile "aws-edge-infra"
 * tests[3]: invalid cluster profile "aws-edge-infra"
, invalid ci-operator config: configuration has 4 errors:

 * tests[0]: invalid cluster profile "aws-edge-infra"
 * tests[1]: invalid cluster profile "aws-edge-infra"
 * tests[2]: invalid cluster profile "aws-edge-infra"
 * tests[3]: invalid cluster profile "aws-edge-infra"
, invalid ci-operator config: configuration has 10 errors:

 * tests[0]: invalid cluster profile "aws-rhdh-performance"
 * tests[1]: invalid cluster profile "aws-rhdh-performance"
 * tests[2]: invalid cluster profile "aws-rhdh-performance"
 * tests[3]: invalid cluster profile "aws-rhdh-performance"
 * tests[4]: invalid cluster profile "aws-rhdh-performance"
 * tests[5]: invalid cluster profile "aws-rhdh-performance"
 * tests[6]: invalid cluster profile "aws-rhdh-performance"
 * tests[7]: invalid cluster profile "aws-rhdh-performance"
 * tests[8]: invalid cluster profile "aws-rhdh-performance"
 * tests[9]: invalid cluster profile "aws-rhdh-performance"
, invalid ci-operator config: configuration has 2 errors:

 * tests[0]: invalid cluster profile "aws-edge-infra"
 * tests[1]: invalid cluster profile "aws-edge-infra"
]

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 10 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 20 rehearsals
Comment: /pj-rehearse max to run up to 35 rehearsals
Comment: /pj-rehearse auto-ack to run up to 10 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

Prucek · 2024-02-15T10:16:33Z

/pj-rehearse periodic-ci-openshift-ci-tools-master-canary-build03

openshift-ci-robot · 2024-02-15T12:05:12Z

@Prucek, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

could not load configuration from candidate revision of release repo: failed to load ci-operator configuration from release repo: invalid ci-operator config: invalid configuration: tests[16]: invalid cluster profile "openstack-nerc-dev"

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 10 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 20 rehearsals
Comment: /pj-rehearse max to run up to 35 rehearsals
Comment: /pj-rehearse auto-ack to run up to 10 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

Prucek · 2024-02-15T12:35:11Z

/pj-rehearse periodic-ci-openshift-ci-tools-master-canary-build03

Prucek · 2024-02-20T14:24:28Z

/pj-rehearse periodic-ci-openshift-ci-tools-master-canary-build03

Prucek · 2024-02-21T12:55:39Z

/pj-rehearse periodic-ci-openshift-ci-tools-master-canary-build03

Prucek · 2024-02-27T09:36:40Z

/pj-rehearse periodic-ci-openshift-ci-tools-master-canary-build03

Prucek · 2024-02-27T09:56:54Z

/pj-rehearse periodic-ci-openshift-ci-tools-master-canary-build03

Prucek · 2024-02-27T10:08:16Z

/pj-rehearse periodic-ci-openshift-ci-tools-master-canary-build03

Prucek · 2024-02-27T12:02:08Z

/pj-rehearse periodic-ci-openshift-ci-tools-master-canary-build03

Prucek · 2024-06-06T11:58:51Z

/retest

openshift-merge-robot · 2024-06-06T11:59:00Z

PR needs rebase.

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.

Prucek · 2024-06-06T12:05:09Z

/close

openshift-ci · 2024-06-06T12:05:12Z

@Prucek: Closed this PR.

Details

In response to this:

/close

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.

* ci: use spike-420-issues images for CI rehearsal validation Updated OPCT workflow to use development images for testing fixes to CI failures in OCP 4.20+ clusters. Changes: - Updated OPCT_CLI_IMAGE to quay.io/mrbraga/opct:spike-420-issues - Added OPCT_DEV_EXTRA_CMD with --plugins-image flag pointing to quay.io/mrbraga/plugin-openshift-tests:spike-420-issues-buildx This allows testing custom images without modifying pkg/types.go, using the --plugins-image CLI argument instead of hardcoded defaults. Built images: - opct CLI: quay.io/mrbraga/opct:spike-420-issues - plugins: quay.io/mrbraga/plugin-openshift-tests:spike-420-issues-buildx Related fixes being tested: - Issue #1: Fixed map printing in status utils - Issue #2 & #3: Fixed HTML encoding and messages in printer - Issue #4: Added failure propagation between plugins - Issue #5: Made log level configurable via LOG_LEVEL env var - Issue #6: Fixed time calculation bug in archive metalog - Issue #7: Added k8s conformance test extraction for OCP 4.20+ 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> testing with latest opct version validate 0.6.1 * Removing changes in AI workflow as is not monitored by SPLAT

…enshift#73943)

openshift-ci Bot added the do-not-merge/hold label Feb 8, 2024

Prucek force-pushed the testing_2 branch from 3dff549 to 8345dc3 Compare February 8, 2024 14:48

Prucek force-pushed the testing_2 branch from 8345dc3 to 525c023 Compare February 9, 2024 09:21

Prucek force-pushed the testing_2 branch from 525c023 to 426b9a3 Compare February 9, 2024 09:24

Prucek force-pushed the testing_2 branch from 426b9a3 to fb830d1 Compare February 13, 2024 13:58

Prucek force-pushed the testing_2 branch from f90fe87 to 0d0cf8d Compare February 13, 2024 15:34

wip2

cd351c0

Prucek force-pushed the testing_2 branch from 0d0cf8d to cd351c0 Compare February 15, 2024 12:02

openshift-merge-robot added the needs-rebase label Jun 6, 2024

openshift-ci Bot closed this Jun 6, 2024

Prucek added a commit that referenced this pull request Jan 26, 2026

openshift/origin: remove autodetectable inputs and base_images #2

ecb6519

Prucek added a commit that referenced this pull request Jan 28, 2026

openshift/origin: remove autodetectable inputs and base_images #2 (op…

853e6ee

…enshift#73943)

Conversation

Prucek commented Feb 8, 2024

Uh oh!

openshift-ci Bot commented Feb 8, 2024

Uh oh!

Prucek commented Feb 8, 2024

Uh oh!

Prucek commented Feb 8, 2024

Uh oh!

openshift-ci-robot commented Feb 9, 2024

Uh oh!

Prucek commented Feb 9, 2024

Uh oh!

Prucek commented Feb 13, 2024

Uh oh!

Prucek commented Feb 13, 2024

Uh oh!

Prucek commented Feb 13, 2024

Uh oh!

openshift-ci-robot commented Feb 13, 2024

Uh oh!

openshift-ci-robot commented Feb 13, 2024

Uh oh!

Prucek commented Feb 15, 2024

Uh oh!

openshift-ci-robot commented Feb 15, 2024

Uh oh!

Prucek commented Feb 15, 2024

Uh oh!

Prucek commented Feb 20, 2024

Uh oh!

Prucek commented Feb 21, 2024

Uh oh!

Prucek commented Feb 27, 2024

Uh oh!

Prucek commented Feb 27, 2024

Uh oh!

Prucek commented Feb 27, 2024

Uh oh!

Prucek commented Feb 27, 2024

Uh oh!

Prucek commented Jun 6, 2024

Uh oh!

openshift-merge-robot commented Jun 6, 2024

Uh oh!

Prucek commented Jun 6, 2024

Uh oh!

openshift-ci Bot commented Jun 6, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants