Skip to content

Update roks-toolkit-base to 8.10-1759911539 - #6

Closed
Joseph-Goergen wants to merge 1 commit into
Prucek:masterfrom
Joseph-Goergen:patch-5
Closed

Update roks-toolkit-base to 8.10-1759911539#6
Joseph-Goergen wants to merge 1 commit into
Prucek:masterfrom
Joseph-Goergen:patch-5

Conversation

@Joseph-Goergen

Copy link
Copy Markdown

No description provided.

@openshift-ci

openshift-ci Bot commented Oct 14, 2025

Copy link
Copy Markdown

Hi @Joseph-Goergen. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@openshift-ci

openshift-ci Bot commented Oct 14, 2025

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Joseph-Goergen
Once this PR has been reviewed and has the lgtm label, please assign prucek 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

@openshift-ci-robot

Copy link
Copy Markdown
Collaborator

@Joseph-Goergen, 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[0]: invalid cluster profile "azure-oadp-qe", invalid ci-operator config: configuration has 5 errors:

 * tests[0]: invalid cluster profile "aws-oadp-qe"
 * tests[1]: invalid cluster profile "aws-oadp-qe"
 * tests[2]: invalid cluster profile "aws-oadp-qe"
 * tests[3]: invalid cluster profile "aws-oadp-qe"
 * tests[4]: invalid cluster profile "aws-oadp-qe"
, invalid ci-operator config: invalid configuration: tests[5]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: invalid configuration: tests[18]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: invalid configuration: tests[19]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: configuration has 2 errors:

 * tests[17]: invalid cluster profile "equinix-edge-enablement"
 * tests[18]: invalid cluster profile "equinix-edge-enablement"
, invalid ci-operator config: invalid configuration: tests[17]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: invalid configuration: tests[16]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: invalid configuration: tests[12]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: invalid configuration: tests[15]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: invalid configuration: tests[0]: invalid cluster profile "gcp-observability", invalid ci-operator config: invalid configuration: tests[0]: invalid cluster profile "aws-quay-qe", invalid ci-operator config: invalid configuration: tests[0]: invalid cluster profile "azure-observability", invalid ci-operator config: invalid configuration: tests[1]: invalid cluster profile "azure-observability", invalid ci-operator config: invalid configuration: tests[43]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: invalid configuration: tests[45]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: invalid configuration: tests[50]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: invalid configuration: tests[53]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: invalid configuration: tests[41]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: invalid configuration: tests[36]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: invalid configuration: tests[51]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: invalid configuration: tests[57]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: configuration has 3 errors:

 * tests[42]: invalid cluster profile "equinix-edge-enablement"
 * tests[43]: invalid cluster profile "equinix-edge-enablement"
 * tests[75]: invalid cluster profile "equinix-edge-enablement"
, invalid ci-operator config: invalid configuration: tests[39]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: configuration has 2 errors:

 * tests[38]: invalid cluster profile "equinix-edge-enablement"
 * tests[68]: invalid cluster profile "equinix-edge-enablement"
, invalid ci-operator config: configuration has 3 errors:

 * tests[40]: invalid cluster profile "equinix-edge-enablement"
 * tests[41]: invalid cluster profile "equinix-edge-enablement"
 * tests[73]: invalid cluster profile "equinix-edge-enablement"
, invalid ci-operator config: invalid configuration: tests[63]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: invalid configuration: tests[1]: invalid cluster profile "gcp-observability", invalid ci-operator config: configuration has 2 errors:

 * tests[2]: invalid cluster profile "equinix-edge-enablement"
 * tests[3]: invalid cluster profile "equinix-edge-enablement"
, invalid ci-operator config: invalid configuration: tests[1]: invalid cluster profile "libvirt-ppc64le-s2s", invalid ci-operator config: invalid configuration: tests[2]: invalid cluster profile "libvirt-ppc64le-s2s", invalid ci-operator config: invalid configuration: tests[3]: invalid cluster profile "libvirt-ppc64le-s2s", invalid ci-operator config: invalid configuration: tests[7]: invalid cluster profile "libvirt-ppc64le-s2s", invalid ci-operator config: invalid configuration: tests[6]: invalid cluster profile "libvirt-ppc64le-s2s", invalid ci-operator config: configuration has 5 errors:

 * tests[14]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[15]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[16]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[17]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[18]: invalid cluster profile "libvirt-ppc64le-s2s"
, invalid ci-operator config: configuration has 7 errors:

 * tests[23]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[24]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[25]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[26]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[27]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[28]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[29]: invalid cluster profile "libvirt-ppc64le-s2s"
, invalid ci-operator config: configuration has 7 errors:

 * tests[24]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[25]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[26]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[27]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[28]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[29]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[30]: invalid cluster profile "libvirt-ppc64le-s2s"
, invalid ci-operator config: configuration has 5 errors:

 * tests[5]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[6]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[7]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[8]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[9]: invalid cluster profile "libvirt-ppc64le-s2s"
, invalid ci-operator config: configuration has 5 errors:

 * tests[7]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[8]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[9]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[10]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[11]: invalid cluster profile "libvirt-ppc64le-s2s"
, invalid ci-operator config: configuration has 7 errors:

 * tests[26]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[27]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[28]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[29]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[30]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[31]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[32]: invalid cluster profile "libvirt-ppc64le-s2s"
, invalid ci-operator config: configuration has 10 errors:

 * tests[31]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[32]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[33]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[34]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[35]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[36]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[37]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[38]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[39]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[40]: invalid cluster profile "libvirt-ppc64le-s2s"
, invalid ci-operator config: configuration has 8 errors:

 * tests[26]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[27]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[28]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[29]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[30]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[31]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[32]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[33]: invalid cluster profile "libvirt-ppc64le-s2s"
, invalid ci-operator config: configuration has 10 errors:

 * tests[33]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[34]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[35]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[36]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[37]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[38]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[39]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[40]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[41]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[42]: invalid cluster profile "libvirt-ppc64le-s2s"
, invalid ci-operator config: configuration has 11 errors:

 * tests[33]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[34]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[35]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[36]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[37]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[38]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[39]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[40]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[41]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[42]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[43]: invalid cluster profile "powervs-8"
, invalid ci-operator config: configuration has 10 errors:

 * tests[34]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[35]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[36]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[37]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[38]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[39]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[40]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[41]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[42]: invalid cluster profile "libvirt-ppc64le-s2s"
 * tests[43]: invalid cluster profile "libvirt-ppc64le-s2s"
, invalid ci-operator config: configuration has 2 errors:

 * tests[3]: invalid cluster profile "gcp-sustaining-autorelease-412"
 * tests[4]: invalid cluster profile "gcp-sustaining-autorelease-412"
, invalid ci-operator config: invalid configuration: tests[3]: invalid cluster profile "gcp-sustaining-autorelease-412", invalid ci-operator config: configuration has 2 errors:

 * tests[0]: invalid cluster profile "gcp-observability"
 * tests[2]: invalid cluster profile "azure-observability"
, invalid ci-operator config: configuration has 2 errors:

 * tests[0]: invalid cluster profile "azure-observability"
 * tests[1]: invalid cluster profile "azure-observability"
, invalid ci-operator config: invalid configuration: tests[2]: invalid cluster profile "gcp-observability", invalid ci-operator config: configuration has 2 errors:

 * tests[1]: invalid cluster profile "gcp-observability"
 * tests[2]: invalid cluster profile "azure-observability"
, invalid ci-operator config: configuration has 2 errors:

 * tests[176]: invalid cluster profile "equinix-edge-enablement"
 * tests[177]: invalid cluster profile "equinix-edge-enablement"
, invalid ci-operator config: invalid configuration: tests[145]: invalid cluster profile "aws-quay-qe", invalid ci-operator config: configuration has 4 errors:

 * tests[33]: invalid cluster profile "equinix-edge-enablement"
 * tests[34]: invalid cluster profile "equinix-edge-enablement"
 * tests[45]: invalid cluster profile "equinix-edge-enablement"
 * tests[46]: invalid cluster profile "equinix-edge-enablement"
, invalid ci-operator config: configuration has 3 errors:

 * tests[30]: invalid cluster profile "equinix-edge-enablement"
 * tests[41]: invalid cluster profile "equinix-edge-enablement"
 * tests[42]: invalid cluster profile "equinix-edge-enablement"
, invalid ci-operator config: configuration has 4 errors:

 * tests[31]: invalid cluster profile "equinix-edge-enablement"
 * tests[32]: invalid cluster profile "equinix-edge-enablement"
 * tests[43]: invalid cluster profile "equinix-edge-enablement"
 * tests[44]: invalid cluster profile "equinix-edge-enablement"
, invalid ci-operator config: configuration has 2 errors:

 * tests[39]: invalid cluster profile "equinix-edge-enablement"
 * tests[40]: invalid cluster profile "equinix-edge-enablement"
, invalid ci-operator config: configuration has 2 errors:

 * releases.initial.stream: must be one of ci, nightly
 * releases.latest.stream: must be one of ci, nightly
, invalid ci-operator config: invalid configuration: tests[2]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: invalid configuration: tests[1]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: configuration has 2 errors:

 * tests[4]: invalid cluster profile "equinix-edge-enablement"
 * tests[5]: invalid cluster profile "equinix-edge-enablement"
, invalid ci-operator config: configuration has 2 errors:

 * tests[5]: invalid cluster profile "equinix-edge-enablement"
 * tests[6]: invalid cluster profile "equinix-edge-enablement"
, invalid ci-operator config: configuration has 3 errors:

 * tests[6]: invalid cluster profile "equinix-edge-enablement"
 * tests[7]: invalid cluster profile "equinix-edge-enablement"
 * tests[116]: invalid cluster profile "equinix-edge-enablement"
, invalid ci-operator config: configuration has 7 errors:

 * tests[0]: invalid cluster profile "oex-aws-qe"
 * tests[1]: invalid cluster profile "oex-aws-qe"
 * tests[2]: invalid cluster profile "oex-aws-qe"
 * tests[3]: invalid cluster profile "oex-aws-qe"
 * tests[4]: invalid cluster profile "oex-aws-qe"
 * tests[5]: invalid cluster profile "oex-aws-qe"
 * tests[6]: invalid cluster profile "oex-aws-qe"
, invalid ci-operator config: configuration has 3 errors:

 * tests[8]: invalid cluster profile "equinix-edge-enablement"
 * tests[9]: invalid cluster profile "equinix-edge-enablement"
 * tests[116]: invalid cluster profile "equinix-edge-enablement"
, invalid ci-operator config: configuration has 29 errors:

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

 * tests[8]: invalid cluster profile "equinix-edge-enablement"
 * tests[9]: invalid cluster profile "equinix-edge-enablement"
 * tests[140]: invalid cluster profile "equinix-edge-enablement"
, invalid ci-operator config: configuration has 8 errors:

 * tests[8]: invalid cluster profile "equinix-edge-enablement"
 * tests[9]: invalid cluster profile "equinix-edge-enablement"
 * tests[29]: invalid cluster profile "equinix-edge-enablement"
 * tests[30]: invalid cluster profile "equinix-edge-enablement"
 * tests[31]: invalid cluster profile "equinix-edge-enablement"
 * tests[32]: invalid cluster profile "equinix-edge-enablement"
 * tests[33]: invalid cluster profile "equinix-edge-enablement"
 * tests[152]: invalid cluster profile "equinix-edge-enablement"
, invalid ci-operator config: configuration has 17 errors:

 * tests[8]: invalid cluster profile "equinix-edge-enablement"
 * tests[9]: invalid cluster profile "equinix-edge-enablement"
 * tests[29]: invalid cluster profile "equinix-edge-enablement"
 * tests[30]: invalid cluster profile "equinix-edge-enablement"
 * tests[31]: invalid cluster profile "equinix-edge-enablement"
 * tests[32]: invalid cluster profile "equinix-edge-enablement"
 * tests[33]: invalid cluster profile "equinix-edge-enablement"
 * tests[34]: invalid cluster profile "equinix-edge-enablement"
 * tests[35]: invalid cluster profile "equinix-edge-enablement"
 * tests[36]: invalid cluster profile "equinix-edge-enablement"
 * tests[37]: invalid cluster profile "equinix-edge-enablement"
 * tests[38]: invalid cluster profile "equinix-edge-enablement"
 * tests[39]: invalid cluster profile "equinix-edge-enablement"
 * tests[40]: invalid cluster profile "equinix-edge-enablement"
 * tests[41]: invalid cluster profile "equinix-edge-enablement"
 * tests[42]: invalid cluster profile "equinix-edge-enablement"
 * tests[163]: invalid cluster profile "equinix-edge-enablement"
, invalid ci-operator config: configuration has 17 errors:

 * tests[9]: invalid cluster profile "equinix-edge-enablement"
 * tests[10]: invalid cluster profile "equinix-edge-enablement"
 * tests[30]: invalid cluster profile "equinix-edge-enablement"
 * tests[31]: invalid cluster profile "equinix-edge-enablement"
 * tests[32]: invalid cluster profile "equinix-edge-enablement"
 * tests[33]: invalid cluster profile "equinix-edge-enablement"
 * tests[34]: invalid cluster profile "equinix-edge-enablement"
 * tests[35]: invalid cluster profile "equinix-edge-enablement"
 * tests[36]: invalid cluster profile "equinix-edge-enablement"
 * tests[37]: invalid cluster profile "equinix-edge-enablement"
 * tests[38]: invalid cluster profile "equinix-edge-enablement"
 * tests[39]: invalid cluster profile "equinix-edge-enablement"
 * tests[40]: invalid cluster profile "equinix-edge-enablement"
 * tests[41]: invalid cluster profile "equinix-edge-enablement"
 * tests[42]: invalid cluster profile "equinix-edge-enablement"
 * tests[43]: invalid cluster profile "equinix-edge-enablement"
 * tests[165]: invalid cluster profile "equinix-edge-enablement"
, invalid ci-operator config: configuration has 9 errors:

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

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

 * tests[1]: invalid cluster profile "metal-perfscale-osp"
 * tests[2]: invalid cluster profile "metal-perfscale-osp"
, invalid ci-operator config: invalid configuration: tests[21]: invalid cluster profile "metal-perfscale-osp", invalid ci-operator config: invalid configuration: tests[6]: job timeout is limited to 8h0m0s, invalid ci-operator config: configuration has 6 errors:

 * tests[0]: invalid cluster profile "gcp-observability"
 * tests[1]: invalid cluster profile "gcp-observability"
 * tests[2]: invalid cluster profile "gcp-observability"
 * tests[12]: invalid cluster profile "gcp-observability"
 * tests[13]: invalid cluster profile "gcp-observability"
 * tests[14]: invalid cluster profile "gcp-observability"
, invalid ci-operator config: invalid configuration: tests[6]: invalid cluster profile "aws-quay-qe", invalid ci-operator config: configuration has 2 errors:

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

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

 * tests[9]: invalid cluster profile "aws-quay-qe"
 * tests[10]: invalid cluster profile "aws-quay-qe"
, invalid ci-operator config: configuration has 3 errors:

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

 * tests[14]: invalid cluster profile "aws-quay-qe"
 * tests[15]: invalid cluster profile "aws-quay-qe"
 * tests[16]: invalid cluster profile "aws-quay-qe"
 * tests[17]: invalid cluster profile "aws-quay-qe"
 * tests[18]: invalid cluster profile "aws-quay-qe"
 * tests[19]: invalid cluster profile "aws-quay-qe"
, invalid ci-operator config: invalid configuration: tests[0]: invalid cluster profile "metal-redhat-gs", invalid ci-operator config: invalid configuration: tests[4]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: invalid configuration: tests[7]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: invalid configuration: tests[6]: invalid cluster profile "equinix-edge-enablement", invalid ci-operator config: configuration has 7 errors:

 * tests[1]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[2]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[6]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[7]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[8]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[15]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[17]: invalid cluster profile "openstack-vh-bm-rhos"
, invalid ci-operator config: configuration has 4 errors:

 * tests[1]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[5]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[6]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[7]: invalid cluster profile "openstack-vh-bm-rhos"
, invalid ci-operator config: configuration has 9 errors:

 * tests[1]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[2]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[5]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[6]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[7]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[10]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[13]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[14]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[16]: invalid cluster profile "openstack-vh-bm-rhos"
, invalid ci-operator config: configuration has 11 errors:

 * tests[1]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[2]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[5]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[6]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[7]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[10]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[13]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[14]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[16]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[17]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[18]: invalid cluster profile "openstack-vh-bm-rhos"
, invalid ci-operator config: configuration has 10 errors:

 * tests[1]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[2]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[5]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[6]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[7]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[10]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[13]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[14]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[15]: invalid cluster profile "openstack-vh-bm-rhos"
 * tests[17]: invalid cluster profile "openstack-vh-bm-rhos"
, invalid ci-operator config: configuration has 3 errors:

 * tests[2]: invalid cluster profile "oex-aws-qe"
 * tests[3]: invalid cluster profile "oex-aws-qe"
 * tests[4]: invalid cluster profile "oex-aws-qe"
, invalid ci-operator config: configuration has 2 errors:

 * tests[1]: invalid cluster profile "oex-aws-qe"
 * tests[2]: invalid cluster profile "oex-aws-qe"
, invalid ci-operator config: configuration has 4 errors:

 * tests[2]: invalid cluster profile "oex-aws-qe"
 * tests[3]: invalid cluster profile "oex-aws-qe"
 * tests[4]: invalid cluster profile "oex-aws-qe"
 * tests[5]: invalid cluster profile "oex-aws-qe"
, invalid ci-operator config: configuration has 8 errors:

 * tests[2]: invalid cluster profile "oex-aws-qe"
 * tests[3]: invalid cluster profile "oex-aws-qe"
 * tests[4]: invalid cluster profile "oex-aws-qe"
 * tests[5]: invalid cluster profile "oex-aws-qe"
 * tests[6]: invalid cluster profile "oex-aws-qe"
 * tests[7]: invalid cluster profile "oex-aws-qe"
 * tests[8]: invalid cluster profile "oex-aws-qe"
 * tests[9]: invalid cluster profile "oex-aws-qe"
, invalid ci-operator config: configuration has 21 errors:

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

 * tests[0]: invalid cluster profile "oex-aws-qe"
 * tests[1]: invalid cluster profile "oex-aws-qe"
 * tests[2]: invalid cluster profile "oex-aws-qe"
 * tests[3]: invalid cluster profile "oex-aws-qe"
 * tests[4]: invalid cluster profile "oex-aws-qe"
 * tests[5]: invalid cluster profile "oex-aws-qe"
 * tests[6]: invalid cluster profile "oex-aws-qe"
 * tests[7]: invalid cluster profile "oex-aws-qe"
 * tests[8]: invalid cluster profile "oex-aws-qe"
 * tests[9]: invalid cluster profile "oex-aws-qe"
 * tests[10]: invalid cluster profile "oex-aws-qe"
 * tests[11]: invalid cluster profile "oex-aws-qe"
 * tests[12]: invalid cluster profile "oex-aws-qe"
 * tests[13]: invalid cluster profile "oex-aws-qe"
 * tests[14]: invalid cluster profile "oex-aws-qe"
 * tests[15]: invalid cluster profile "oex-aws-qe"
 * tests[16]: invalid cluster profile "oex-aws-qe"
 * tests[17]: invalid cluster profile "oex-aws-qe"
 * tests[18]: invalid cluster profile "oex-aws-qe"
 * tests[19]: invalid cluster profile "oex-aws-qe"
 * tests[20]: invalid cluster profile "oex-aws-qe"
 * tests[21]: invalid cluster profile "oex-aws-qe"
]
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 list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

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 pushed a commit that referenced this pull request Dec 11, 2025
* 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants