Bug 2084158

Summary: Support provisioning bm cluster where no provisioning network provided
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: Thuy Nguyen <thnguyen>
Component: ConsoleAssignee: Kevin Cormier <kcormier>
Status: CLOSED ERRATA QA Contact: Xiang Yin <xiyin>
Severity: medium Docs Contact: Christopher Dawson <cdawson>
Priority: unspecified    
Version: rhacm-2.5CC: dho, dhuynh, ecai, huichen, kcormier
Target Milestone: ---Flags: bot-tracker-sync: rhacm-2.5+
Target Release: rhacm-2.5   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-09 02:12:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Thuy Nguyen 2022-05-11 14:34:01 UTC
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:

Comment 3 Kevin Cormier 2022-05-11 19:07:54 UTC
@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?

Comment 5 bot-tracker-sync 2022-05-16 20:58:23 UTC
G2Bsync 1128068687 comment 
 thuyn-581 Mon, 16 May 2022 19:46:38 UTC 
 G2BSync -
Validated on 2.5.0-RC2.

Comment 9 errata-xmlrpc 2022-06-09 02:12:04 UTC
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