Red Hat Bugzilla – Bug 617587
Luci doesn't display underlying errors
Last modified: 2016-04-26 10:18:23 EDT
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:
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
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):
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.