Epic Goal

The IBM Power Team switches the jobs to Release Blocker and maintains stability.

The current jobs are informing jobs that are part of an install analysis:

• 4.21 - https://prow.ci.openshift.org/job-history/gs/test-platform-results/logs/periodic-ci-openshift-multiarch-master-nightly-4.21-install-analysis-all-ppc64le
• 4.20 - https://prow.ci.openshift.org/job-history/gs/test-platform-results/logs/periodic-ci-openshift-multiarch-master-nightly-4.20-install-analysis-all-ppc64le

This epic switches from informing to payload blocking. This switch would be for 4.22 only.

We may need to select additional jobs.

Why is this important?

• IBM Power is a stable component of the OpenShift 4.22 release.
• This progression is part of the overall IBM Power stability journey.

Acceptance Criteria

• IBM Power jobs are marked as a payload release blocker and are stable for the 4.22 release.
• There are sufficient daily jobs to be a payload release blocker.
• The release blockers are on `multi` power payload.
• Qualifying Spike has an outcome defined.

Note `multi` will have the same sha256 commit as `intel` and should be used to stay in sync.

Dependencies (internal and external)
1. ART

2. IBM Power CI

Done Checklist

• CI - For new features (non-enablement), existing Multi-Arch CI jobs are not broken by the Epic