-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
-
False
-
-
False
-
-
-
-
USER PROBLEM
What is the user experiencing as a result of the bug? Include steps to reproduce.
- The user experience could be improved for the case where the user fails to provide the central endpoint for any command that requires connectivity to central
- sample command: podman run -it registry.redhat.io/advanced-cluster-security/rhacs-roxctl-rhel8:4.8.4 central loginĀ
- returned error: ERROR: verifying login auth providers: requesting login auth providers: error when doing http request: dial tcp [::1]:8443: connect: connection refused
CONDITIONS
What conditions need to exist for a user to be affected? Is it everyone? Is it only those with a specific integration? Is it specific to someone with particular database content? etc.
- missing endpoint information (env var or explicit command line parameter)
- no central instance listening on port 8443 on localhost
ROOT CAUSE
What is the root cause of the bug?
- in case the endpoint information is not specified, roxctl uses localhost:8443 as default value
FIX
How was the bug fixed (this is more important if a workaround was implemented rather than an actual fix)?
- (one possibility) - keep in the command context the fact that roxctl reverted to default, possibly use a shorter timeout in this case, and catch timeout/connection refused errors to return some more meaningful error than the raw technical error