TRT TL;DR - we are only adding informing jobs for 4.19; the last should be ready to make informing on March 20th, check back then.

We would like to ask you to re-instate the CNV e2e jobs to be in informing status to OCP, now that they have been stabilized.

Links for these jobs history:

• 4.16: https://prow.ci.openshift.org/job-history/gs/test-platform-results/logs/periodic-ci-openshift-release-master-cnv-nightly-4.16-e2e-azure-deploy-cnv
• 4.17: https://prow.ci.openshift.org/job-history/gs/test-platform-results/logs/periodic-ci-openshift-release-master-cnv-nightly-4.17-e2e-azure-deploy-cnv
• 4.18: https://prow.ci.openshift.org/job-history/gs/test-platform-results/logs/periodic-ci-openshift-release-master-cnv-nightly-4.18-e2e-azure-deploy-cnv
• 4.19: https://prow.ci.openshift.org/job-history/gs/test-platform-results/logs/periodic-ci-openshift-release-master-cnv-nightly-4.19-e2e-azure-deploy-cnv

(links for Sippy are not formatted well in jira)

They all have a pass rate much higher than 70% since at least last sprint.

A method for escalation of breakages to the team (jira, slack, e-mail, etc)

• slack channel: #forum-cnv-hyperconverged-cluster-operator (on which we also get bot reports for every single failure)
• email: cnv-hco@redhat.com

A manager backstop to contact if the job fails for a prolonged period:
kmajcher@redhat.com 

Note:
A PR has been opened:
https://github.com/openshift/release/pull/61608