Description of problem:
luci reports "unknown" as cluster name if cluster creation fails (not
reproducible at will)
For example - in debugging the problem described in
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=217724, I did see this
problem of an "unknown" cluster a couple of times. luci didn;t write anything
interesting to its debug log.
Jim Parsons suggested that I log this bz - even though it's not yet reproducible
ar will - while I'm looking at determining the exact cause/sequence of actions
to recreate the bug.
Version-Release number of selected component (if applicable):
Intermittent - maybe 20% of the time
Steps to Reproduce:
1. Create a new cluster, but have that cluster creation fail - for example, due
to the bug described in https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=217724
See the first attachment.
A more helpful error message.
Created attachment 142569 [details]
Screen shot of "unknown" cluster
I believe this occurs when ricci is unable to get information about the cluster
from modclusterd because modclusterd (and/or cluster infrastructure) is not
running. What luci should do is use the information about the cluster (name,
nodes, etc.) that is does have in its database instead of simply printing
'[unknown]' and nothing else.
The fix for this is in -HEAD now. I'll commit it to -RHEL5 once all the
appropriate flags are set.
Unable to exactly recreate the problem - but, I never was able to. Tried to
cause the problem by killing modclusterd, and the "unknown" error did not
result. Marking the bz as verified.
A package has been built which should help the problem described in
this bug report. This report is therefore being closed with a resolution
of CURRENTRELEASE. You may reopen this bug report if the solution does
not work for you.