Bug 1377258
| Summary: | rhui-manager crashes if the hostname of a CDS or LB instance which is being added can't be resolved | ||
|---|---|---|---|
| Product: | Red Hat Update Infrastructure for Cloud Providers | Reporter: | Radek Bíba <rbiba> |
| Component: | Tools | Assignee: | bizhang |
| Status: | CLOSED ERRATA | QA Contact: | Radek Bíba <rbiba> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.0.0 | CC: | bizhang, pcreech |
| Target Milestone: | --- | ||
| Target Release: | 3.0.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-03-01 22:13:16 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Radek Bíba
2016-09-19 10:14:03 UTC
Bihan, With the update included in ISO 20161122, rhui-manager doesn't terminate, but I get the following output: ==== [localhost] local: nc asd.example.com 22 < /dev/null Fatal error: local() encountered an error (return code 2) while executing 'nc asd.example.com 22 < /dev/null' Aborting. Something happened, check the log file for more information: ~/.rhui/rhui.log ==== The log file then contains a traceback with the same message in a RhuiException. The message doesn't say what kind of error occurred, which one would see if they ran nc by hand: # nc asd.example.com 22 < /dev/null Ncat: Could not resolve hostname "asd.example.com": Name or service not known. QUITTING. Is the unspecified error and the reference to the log file containing only the traceback all that could be reasonably reported to the user? Or could rhui-manager be more informative? Radek, We are currently capture the error message returned from the fabric api. Since it doesn't return the default nc error message there's really no way for us to capture and display the nc error message. I think the RHUI error message in the log file is sufficient as it does state that it failed to connect to a server... RhuiException: Failed to connect to adsf.example.com: local() encountered an error (return code 2) while executing 'nc adsf.example.com 22 < /dev/null'. Okay, thanks for clarifying that. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:0367 |