OCPBUGS-60154: Update olmv1.go cluster-logging to 6.3.0

[bentito]

cluster-logging 6.2.2 set maxOCPVersion <= 4.20 so hopefully this bump to 6.3.0 will help

[camilamacedo86]

Cluster Logging and its version do not exist in 4.20
We need a scenario that works for 4.20 and also for 4.19 :-(
So that we can move forward and bump 4.20 catalogs

[bentito]

This is not the droid you're looking for.

More precisely, the actual problem is not some version of cluster-logging operator that has a better value for maxOCPVersion, it's to find an operator that has maxOCPVersion and with a good value setting maxOCPVersion <= 4.20.

Closing this since the approach in this PR, I now understand, can't work.

[camilamacedo86]

Hi @bentito

lets keep open if they add we can merge this one instead
What do you think about adding the OCBUG as well in the title, since we know it is related to that one?

[bentito]

opened back up

[openshift-ci-robot]

@bentito: This pull request references Jira Issue OCPBUGS-60154, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.0) matches configured target version for branch (4.20.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @Xia-Zhao-rh

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

cluster-logging 6.2.2 set maxOCPVersion <= 4.20 so hopefully this bump to 6.3.0 will help

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]

@bentito: 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-ovn-single-node-upgrade	ece8cd1	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-openstack-ovn	ece8cd1	link	false	/test e2e-openstack-ovn
ci/prow/e2e-hypershift-conformance	ece8cd1	link	false	/test e2e-hypershift-conformance
ci/prow/e2e-azure	ece8cd1	link	false	/test e2e-azure
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout	ece8cd1	link	false	/test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway	ece8cd1	link	false	/test e2e-metal-ipi-ovn-dualstack-local-gateway
ci/prow/e2e-aws-disruptive	ece8cd1	link	false	/test e2e-aws-disruptive
ci/prow/e2e-metal-ipi-serial-ovn-ipv6-1of2	ece8cd1	link	false	/test e2e-metal-ipi-serial-ovn-ipv6-1of2
ci/prow/e2e-metal-ipi-ovn-dualstack	ece8cd1	link	false	/test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-aws-ovn-kube-apiserver-rollout	ece8cd1	link	false	/test e2e-aws-ovn-kube-apiserver-rollout

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.

[camilamacedo86]

/lgtm

[camilamacedo86]

/approve

[tmshort]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bentito, camilamacedo86, tmshort

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:

• test/extended/olm/OWNERS [tmshort]

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]

@bentito: This pull request references Jira Issue OCPBUGS-60154. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

Details

In response to this:

cluster-logging 6.2.2 set maxOCPVersion <= 4.20 so hopefully this bump to 6.3.0 will help

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.