Bug 2032000 - RFE Unable to deploy cluster on VMware - hive controller error 400 Bad Request
Summary: RFE Unable to deploy cluster on VMware - hive controller error 400 Bad Request
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Console
Version: rhacm-2.4
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
: ---
Assignee: Christian Stark
QA Contact: Eveline Cai
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-13 20:20 UTC by Ryan Spagnola
Modified: 2023-09-15 01:18 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-16 17:28:24 UTC
Target Upstream Version:
Embargoed:
dhuynh: qe_test_coverage?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github open-cluster-management backlog issues 18470 0 None None None 2021-12-13 22:06:07 UTC

Description Ryan Spagnola 2021-12-13 20:20:11 UTC
Description of the problem:
When attempting to deploy a new cluster to VMware, ACM accepts the parameters and goes into a perpetual state of "Installing", but no activity happens in VMware and no logs are available from the cluster status page.  Upon investigating the hive-controller/manager shows multiple "400 Bad Request" errors causing "failed to create vSphere client", and "Reconciler Error".

Release version:
2.4

Operator snapshot version:

OCP version:
4.8.22

Browser Info:

Steps to reproduce:
1. https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.4/html/clusters/managing-your-clusters#creating-a-cluster-on-vmware-vsphere

Actual results:
400 Bad Request Error

Expected results:
Cluster deployed to VMware environment

Additional info:
This is a disconnected environment.

There is a proxy in this environment, however adding or ommitting the proxy info from the install-config makes no difference in the behavior or observed errors, and the proxy has been confirmed working for deployment to VMware via Azure Pipeline.

Comment 3 Samson Wick 2021-12-14 19:50:54 UTC
Determined the root cause of this issue was an incorrectly formatted provider credential.  The "vCenter server" value was entered as a URL rather than a raw hostname.

Would like to turn this into an RFE to do one of the following:

1. rename the field to "vCenter server fqdn" or similar to indicate a URL is not appropriate

OR

2. add a constraint to the "vCenter server" field which does not allow for URLs to be input

OR

3. add logic to reformat the input if it is entered as a URL

AND

Add a function to the credential creation form which validates the credential at creation time.

Comment 4 Sho 2022-01-11 15:11:17 UTC
I created an issue in the RHACM backlog to prioritize this RFE:

https://issues.redhat.com/browse/ACM-1139

Do we normally close out the BZs, once RFEs are created in Jira @cstark ?

Comment 6 Sho 2022-01-11 16:29:48 UTC
@

Comment 7 Sho 2022-01-11 16:30:56 UTC
We've never treated absence of these kind of things as a bug; there's more than just this one field for validation that could be implemented for forms across the UI.

Comment 8 Kevin Cormier 2022-03-16 17:28:24 UTC
Not a bug. Tracking as an enhancement request at https://issues.redhat.com/browse/ACM-1139

Comment 9 Red Hat Bugzilla 2023-09-15 01:18:08 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days


Note You need to log in before you can comment on or make changes to this bug.