Bug 2096406

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 WONTFIX QA Contact: Xiang Yin <xiyin>
Severity: medium Docs Contact: Christopher Dawson <cdawson>
Priority: unspecified    
Version: rhacm-2.4.zCC: dho, dhuynh, huichen
Target Milestone: ---Flags: bot-tracker-sync: rhacm-2.4.z+
Target Release: ---   
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-08-23 15:21:19 UTC Type: ---
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-06-13 18:31:35 UTC
This bug was initially created as a copy of Bug #2084158

I am copying this bug because: 



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 1 Kevin Cormier 2022-08-23 15:21:19 UTC
Will not bother backporting this fix unless reported by a customer.