Description of problem: Deploy an ocp cluster without provisioning network is not possible in ACM UI Version-Release number of selected component (if applicable): How reproducible: To deploy a cluster without provisioning network, the following change should be set in install-config platform: baremetal: apiVIP: <api_VIP> ingressVIP: <ingress_VIP> provisioningNetwork: "Disabled" Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The above is documented here: https://docs.openshift.com/container-platform/4.10/installing/installing_bare_metal_ipi/ipi-install-installation-workflow.html#modifying-install-config-for-no-provisioning-network_ipi-install-installation-workflow
@thnguyen Can you please provide the full install-config.yaml that worked for you? I'm wondering if we need to exclude the provisioningNetworkInterface and provisioningBridge values, or any other values. Can we we set provisioningNetwork: "Disabled" as long as the provisioningNetworkCIDR is not provided, or would we need to add a checkbox in the UI?
G2Bsync 1128068687 comment thuyn-581 Mon, 16 May 2022 19:46:38 UTC G2BSync - Validated on 2.5.0-RC2.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Red Hat Advanced Cluster Management 2.5 security updates, images, and bug fixes), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:4956