Bug 617587
| Summary: | Luci doesn't display underlying errors | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Andrew Beekhof <abeekhof> |
| Component: | luci | Assignee: | Ryan McCabe <rmccabe> |
| Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.0 | CC: | bbrock, cluster-maint |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | luci-0.23.0-12.el6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-05-19 13:56:13 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 617586 | ||
| Bug Blocks: | |||
This issue has been proposed when we are only considering blocker issues in the current Red Hat Enterprise Linux release. ** If you would still like this issue considered for the current release, ask your support representative to file as a blocker on your behalf. Otherwise ask that it be considered for the next Red Hat Enterprise Linux release. ** fix verified in luci-0.23.0-13.el6 I've checked this many times. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0655.html |
Description of problem: Possibly ricci doesn't expose them (in which case we can clone the bug for it too), but we should be able to give some feedback to users about the nature of faults. For example, I had no search line in /etc/resolv.conf which meant cman couldn't start. "service cman start" shows: Starting cluster: Checking Network Manager... [ OK ] Global setup... [ OK ] Loading kernel modules... [ OK ] Mounting configfs... [ OK ] Starting cman... Can't determine address family of nodename Unable to get the configuration Can't determine address family of nodename cman_tool: corosync daemon didn't start [FAILED] Which isn't perfect but quickly led me to think about name resolution and resolv.conf Luci just displayed "Node is not a member of the cluster" in red with no explanation. Similarly "Join Cluster" displayed no kind of error and the node simply retained the "not a member" status. Version-Release number of selected component (if applicable): luci-0.22.2-1.auto1279839662