[release-4.19] OCPBUGS-56811: Update Control Plane replica validation for Single Node OpenShift

[sadasu]

Installer can be used to provision Single Node OpenShift(SNO) only on AWS, GCP, Azure, PowerVS and Baremetal platforms. SNO is not supported on all on-prem platforms yet. Even on the platforms that support SNO installs, the install method currently supported are assisted/agent/ZTP.

Update test method TestBaremetalGeneratedAssetFiles() to create a valid Baremetal IPI install config.

Manual backport of #9048

[openshift-ci-robot]

@sadasu: This pull request references Jira Issue OCPBUGS-56811, which is invalid:

• expected the bug to target either version "4.19." or "openshift-4.19.", but it targets "4.20.0" instead
• expected dependent Jira Issue OCPBUGS-6508 to target a version in 4.20.0, but it targets "4.19.0" 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.

In response to this:

Installer can be used to provision Single Node OpenShift(SNO) only on AWS, GCP, Azure, PowerVS and Baremetal platforms. SNO is not supported on all on-prem platforms yet. Even on the platforms that support SNO installs, the install method currently supported are assisted/agent/ZTP.

Update test method TestBaremetalGeneratedAssetFiles() to create a valid Baremetal IPI install config.

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.

[sadasu]

/jira refresh

[openshift-ci-robot]

@sadasu: This pull request references Jira Issue OCPBUGS-56811, which is invalid:

• expected dependent Jira Issue OCPBUGS-6508 to target a version in 4.20.0, but it targets "4.19.0" 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.

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.

[sadasu]

/jira refresh

[openshift-ci-robot]

@sadasu: This pull request references Jira Issue OCPBUGS-56811, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.0) matches configured target version for branch (4.19.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-6508 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-6508 targets the "4.20.0" version, which is one of the valid target versions: 4.20.0
• bug has dependents

Requesting review from QA contact:
/cc @gpei

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.

[sadasu]

/label backport-risk-assessed

[gpei]

/label cherry-pick-approved

[tthvo]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tthvo

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

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

[openshift-ci-robot]

@sadasu: Jira Issue OCPBUGS-56811: All pull requests linked via external trackers have merged:

• openshift/installer#9756

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

In response to this:

Installer can be used to provision Single Node OpenShift(SNO) only on AWS, GCP, Azure, PowerVS and Baremetal platforms. SNO is not supported on all on-prem platforms yet. Even on the platforms that support SNO installs, the install method currently supported are assisted/agent/ZTP.

Update test method TestBaremetalGeneratedAssetFiles() to create a valid Baremetal IPI install config.

Manual backport of #9048

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]

@sadasu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-vsphere-ovn-multi-network	4cd9eaf	link	false	/test e2e-vsphere-ovn-multi-network

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-installer
This PR has been included in build ose-installer-container-v4.19.0-202505290343.p0.g19e8b22.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-baremetal-installer
This PR has been included in build ose-baremetal-installer-container-v4.19.0-202505290343.p0.g19e8b22.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-artifacts
This PR has been included in build ose-installer-artifacts-container-v4.19.0-202505290343.p0.g19e8b22.assembly.stream.el9.
All builds following this will include this PR.

[sadasu]

/cherry-pick release-4.18

[openshift-cherrypick-robot]

@sadasu: new pull request created: #9758

In response to this:

/cherry-pick release-4.18

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.