Bug 249291
| Summary: | delete node task fails to do all items listed in the help document | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Corey Marthaler <cmarthal> | ||||
| Component: | conga | Assignee: | Ryan McCabe <rmccabe> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 5.0 | CC: | cluster-maint, jparsons, kanderso, kupcevic, rmccabe | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | RHSA-2007-0640 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2007-11-07 15:38:25 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: | |||||||
| Attachments: |
|
||||||
|
Description
Corey Marthaler
2007-07-23 15:24:26 UTC
More delete stuff...
After attempting to re-add the deleted node I see the following from conga:
Status messages:
* Host taft-04.lab.msp.redhat.com is already authenticated
The following errors occurred:
* taft-04.lab.msp.redhat.com reports it is already a member of cluster
"taft_cluster"
Which version of cman do you have? This looks like it might be the same problem fixed here https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=244867 cman-2.0.69-1.el5 With the latest, all I see when attempting to delete is the following: Deletion of node "taft-03.lab.msp.redhat.com" from cluster "TAFT_CLUSTER" failed And nothing happens at all. When this happens, it's an indication that at least one cluster service on the node could not be stopped. The delete procedure tries to stop all cluster services, then delete the cluster.conf and propagate a new conf to the remaining cluster members. If the first step fails, luci bails out. When the node couldn't be deleted, were there any init scripts hung trying to stop? If not, are you able to stop cluster services manually? If you edit /var/lib/luci/Extensions/conga_constants, at the bottom of the file, there are three constants that control debugging output. If you set LUCI_DEBUG_MODE to True and LUCI_DEBUG_VERBOSITY to something >= 3, and configure syslogd to log authpriv.debug, luci will produce (a lot) of debugging output that should indicate what went wrong. Sorry, that should read /var/lib/luci/Extensions/conga_constants.py above. Created attachment 161700 [details]
log from luci server
Here is the log that you requested during a delete attempt. Again, all I saw
was, "Deletion of node "link-08.lab.msp.redhat.com" from cluster "LINK_278"
failed"
Thanks for the log. Turns out the bug has nothing specific to do with node deletion; the real problem is luci is not properly handling clusters whose names are not all lowercase in a few places. Fix committed to CVS and will be in the next build. fix verified in 0.10.0-5.el5. 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 the 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/RHSA-2007-0640.html |