Description of problem: Using the shell to connect to a single label domain fails. For example connecting using the command below fails. connect --url 'https://latest:443/api' --user 'admin@internal' --password 'redhat' -I The following error is obtained. Note that the url format matches. error: "https://latest:443/api" is invalid url format. valid format is http[s]://server:port/api. Version-Release number of selected component (if applicable): rhsc-cb7 How reproducible: every time Steps to Reproduce: 1. on the shell session for the machine hosting rhsc, enter command connect --url 'https://latest:443/api' --user 'admin@internal' --password 'redhat' -I 2. when prompted for password, enter password and hit enter 3. when prompted, type 'connect' and hit enter Actual results: error: "https://latest:443/api" is invalid url format. valid format is http[s]://server:port/api. Expected results: user is able to successfully connect Additional info:
Hi Dustin, Can you try the same with cb8? Also the command would be as below - connect --url 'https://hostname/api' --user 'admin@internal' --password 'redhat' -I. Note here port no not to be mentioned.
Still an issue in cb10: error: "https://latest:443/api" is invalid url format. valid format is http[s]://server:port/api.
Created attachment 832413 [details] screenshot of rhsc-shell connect
Dustin, I tried the below command in cb10 and it works fine connect --url 'https://10.70.42.167/api' --user 'admin@internal' --password 'redhat' -I Screenshot shared for reference. Request you to share the screenshot, the way you are trying to connect.
the bug is for a domain that only has a single hop dns lookup...for example: https://latest/api https://rhsc/api https://myrhsc/api https://thisismyrhsc/api
Created attachment 833163 [details] screenshot
Dustin, In case of oVirt the domain names like https://latest/api, https://rhsc/api are not supported and so the error. The domain names should be in the form like a.b.com. It should contain "." character. Its should be FQDN actually. If you access the same setup using the IP address it would work fine.
If FQDN format or IP address for host name is used and that works fine, then it's not a bug. Dustin, pls. confirm that.
FQDN or IP Address work fine.