OPRUN-3267: Adding OLMOperatorsInFailedState risk

[LalatenduMohanty]

Both OCPBUGS-31080 and OCPBUGS-24009 has same symptoms and mostlikely related. We are adding a single risk for both of these bugs. However if we come to know if these bugs are separate then we will add separate risks.

Used below script to generate the files

$ curl -s 'https://api.openshift.com/api/upgrades_info/graph?channel=candidate-4.15&arch=amd64' | jq -r '.nodes[] | .version' | grep '^4[.]15[.]' | grep -v '^4[.]15[.]0' | grep -v '0-[er]c[.]'| while read VERSION; do sed "s/4.15.0/${VERSION}/" blocked-edges/4.15.0-OLMOperatorsInFailedState.yaml > "blocked-edges/${VERSION}-OLMOperatorsInFailedState.yaml"; done

[openshift-ci-robot]

@LalatenduMohanty: This pull request references OPRUN-3267 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the spike to target the "4.16.0" version, but no target version was set.

In response to this:

Both OCPBUGS-31080 and OCPBUGS-24009 has same symptoms and mostlikely related. We are adding a single risk for both of these bugs. However if we come to know if these bugs are separate then we will add separate risks.

Used below script to generate the files
$ curl -s 'https://api.openshift.com/api/upgrades_info/graph?channel=candidate-4.15&arch=amd64' | jq -r '.nodes[] | .version' | grep '^4[.]15[.]' | grep -v '0-[er]c[.]'| while read VERSION; do sed "s/4.15.0/${VERSION}/" blocked-edges/4.15.0-OLMOperatorsInFailedState.yaml > "blocked-edges/${VERSION}-OLMOperatorsInFailedState.yaml"; done

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-robot]

@LalatenduMohanty: This pull request references OPRUN-3267 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the spike to target the "4.16.0" version, but no target version was set.

In response to this:

Both OCPBUGS-31080 and OCPBUGS-24009 has same symptoms and mostlikely related. We are adding a single risk for both of these bugs. However if we come to know if these bugs are separate then we will add separate risks.

Used below script to generate the files

$ curl -s 'https://api.openshift.com/api/upgrades_info/graph?channel=candidate-4.15&arch=amd64' | jq -r '.nodes[] | .version' | grep '^4[.]15[.]' | grep -v '^4[.]15[.]0' | grep -v '0-[er]c[.]'| while read VERSION; do sed "s/4.15.0/${VERSION}/" blocked-edges/4.15.0-OLMOperatorsInFailedState.yaml > "blocked-edges/${VERSION}-OLMOperatorsInFailedState.yaml"; done

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.

[wking]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: LalatenduMohanty, wking

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [LalatenduMohanty,wking]

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