MGMT-20082: Deploying 4/5 nodes control plane is blocked

[jgyselov]

https://issues.redhat.com/browse/MGMT-20082
https://issues.redhat.com/browse/MGMT-20083

4 and 5 control planes nodes should not be allowed for OpenShift versions older than 4.18 and those that are -multi.

[openshift-ci-robot]

@jgyselov: This pull request references MGMT-20082 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 bug to target the "4.19.0" version, but no target version was set.

In response to this:

https://issues.redhat.com/browse/MGMT-20082

4 and 5 control planes nodes should not be allowed for OpenShift versions older than 4.18 and those that are -multi.

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]

@jgyselov: This pull request references MGMT-20082 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 bug to target the "4.19.0" version, but no target version was set.

In response to this:

https://issues.redhat.com/browse/MGMT-20082
https://issues.redhat.com/browse/MGMT-20083

4 and 5 control planes nodes should not be allowed for OpenShift versions older than 4.18 and those that are -multi.

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: ElayAharoni, jgyselov

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 [jgyselov]

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

[openshift-ci]

New changes are detected. LGTM label has been removed.

[jgyselov]

/cherry-pick releases/v2.14-cim

[openshift-cherrypick-robot]

@jgyselov: #2861 failed to apply on top of branch "releases/v2.14-cim":

Applying: Force version fix
Applying: Allow HA CPN based on the selected OpenShift image
Using index info to reconstruct a base tree...
M	libs/locales/lib/en/translation.json
M	libs/ui-lib/lib/cim/components/ClusterDeployment/ClusterDeploymentDetailsForm.tsx
M	libs/ui-lib/lib/cim/components/ClusterDeployment/ClusterDetailsFormFields.tsx
Falling back to patching base and 3-way merge...
Auto-merging libs/ui-lib/lib/cim/components/ClusterDeployment/ClusterDetailsFormFields.tsx
Auto-merging libs/ui-lib/lib/cim/components/ClusterDeployment/ClusterDeploymentDetailsForm.tsx
CONFLICT (content): Merge conflict in libs/ui-lib/lib/cim/components/ClusterDeployment/ClusterDeploymentDetailsForm.tsx
Auto-merging libs/locales/lib/en/translation.json
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0002 Allow HA CPN based on the selected OpenShift image

In response to this:

/cherry-pick releases/v2.14-cim

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.