OCPBUGS-85579: Updates channels to skip v1.19.0 during upgrades

[bharath-b-rh]

The PR is for updating the channels to skip 1.19.0 which has issue reported in OCPBUGS-85579, where the operator installation fails on console-less cluster. By skipping the operator v1.19.0, users could upgrade from lower versions without any failure directly to v1.19.1.

[openshift-ci-robot]

@bharath-b-rh: This pull request references Jira Issue OCPBUGS-85579, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Release Pending (Done) 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:

The PR is for updating the channels to skip 1.19.0 which has issue reported in OCPBUGS-85579, where the operator installation fails on console-less cluster. By skipping the operator v1.19.0, users could upgrade from lower versions without any failure directly to v1.19.1.

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bharath-b-rh

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 [bharath-b-rh]

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

[bharath-b-rh]

/jira refresh

[openshift-ci-robot]

@bharath-b-rh: This pull request references Jira Issue OCPBUGS-85579, which is valid.

3 validation(s) were run on this bug

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

No GitHub users were found matching the public email listed for the QA contact in Jira (amendiol@redhat.com), skipping review request.

Details

In response to this:

/jira refresh

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.

[mytreya-rh]

/lgtm

[openshift-ci-robot]

@bharath-b-rh: Jira Issue OCPBUGS-85579: All pull requests linked via external trackers have merged:

• openshift/cert-manager-operator#424
• openshift/cert-manager-operator#426
• openshift/cert-manager-operator#455
• openshift/release#81900
• openshift/cert-manager-operator#467
• openshift/cert-manager-operator#468
• openshift/cert-manager-operator-release#900

Jira Issue OCPBUGS-85579 has been moved to the MODIFIED state.

Details

In response to this:

The PR is for updating the channels to skip 1.19.0 which has issue reported in OCPBUGS-85579, where the operator installation fails on console-less cluster. By skipping the operator v1.19.0, users could upgrade from lower versions without any failure directly to v1.19.1.

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.