Bug 2096406 - Support provisioning bm cluster where no provisioning network provided
Summary: Support provisioning bm cluster where no provisioning network provided
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Console
Version: rhacm-2.4.z
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Kevin Cormier
QA Contact: Xiang Yin
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-06-13 18:31 UTC by Thuy Nguyen
Modified: 2022-09-12 17:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-23 15:21:19 UTC
Target Upstream Version:
Embargoed:
bot-tracker-sync: rhacm-2.4.z+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 23205 0 None None None 2022-06-13 22:02:16 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.