Description of problem: Connection test to check the ‘libvirt URI’ parameter at the ‘provider connection’ settings in a BM deployment, running into errors on a wrong parameter value only on the cluster creation process (hive container logs) which take another 10-15 min. On my deployment attempts, I tried 5-10 different parameters and the feedback for incorrect value is on the creation cluster, it can be helpful to have an immediate check while entering the parameter or before approving/adding the new ‘provider connection’ to the list. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Create a new provider connection for BM 2.create a new cluster 3. Actual results: Expected results: Additional info:
I can start, by documenting how customer can manually verify their libvirt URL to be passed to ACM
@cdoan thank you that does sound like the right starting point. I wonder if the assisted installer service provides this kind of checking?
Close this issue since examples for the libvirtURL that customers can define have been documented.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days