Make CLO install channel change resilient

Open yuumasato opened this issue 3 months ago • 1 comments

Description:

This patch probes the operator manifest to grab the latest available channel and use that to install CLO.

Rationale:

Cluster Logging Operator keeps changing the list of available channels. On OCP version 4.19 stable-6.1 is not available anymore, while on 4.16 stable-6.3 is not available.

Review Hints:

Check that manual remediation work across supported OCP versions.

Sep 23 '25 13:09 yuumasato

@yuumasato: 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-aws-openshift-node-compliance	3b38ab2d7d892f498ce24ef7b68b3502bf36e930	link	true	`/test e2e-aws-openshift-node-compliance`
ci/prow/e2e-aws-openshift-platform-compliance	3b38ab2d7d892f498ce24ef7b68b3502bf36e930	link	true	`/test e2e-aws-openshift-platform-compliance`

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.

Oct 09 '25 01:10 openshift-ci[bot]