Bug 233633
| Summary: | Wrong cluster members are displayed in system-config-clusters | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Robert Hell <robert.hell> | ||||
| Component: | system-config-cluster | Assignee: | Jim Parsons <jparsons> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Cluster QE <mspqa-list> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 5.0 | CC: | cluster-maint | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2007-09-12 20:40:51 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
Robert Hell
2007-03-23 15:08:49 UTC
Created attachment 150765 [details]
Screenshot of the problem
Yuk. Sorry - still getting used to new cman_tool syntax. There will be an async errata release for s-c-cluster very soon - I would strongly suspect that a fix for this will be in there :) Do you want a quick patched version of the app that fixes this issue (that is, not officially released yet)? If this will help, I'll move this to the top of the list and post it here...just say the word. No thanks, no problem at all. I'll be waiting for the errata. I have another problem with s-c-cluster - because it's similar to the reported
in this bugzilla and concerns the same source file (CommandHandler.py), i'm not
creating a new bugzilla.
After simulating one cluster node dead (by unplugging it from the network) the
cluster node which is still alive fences the node. After that it's not possible
to open s-c-cluster on the remaining cluster node:
Traceback (most recent call last):
File "/usr/sbin/system-config-cluster", line 690, in ?
runFullGUI()
File "/usr/sbin/system-config-cluster", line 672, in runFullGUI
baseapp = basecluster(glade_xml, app)
File "/usr/sbin/system-config-cluster", line 133, in __init__
self.mgmttab = MgmtTab(glade_xml, self.model_builder,self.winMain)
File "/usr/share/system-config-cluster/MgmtTab.py", line 117, in __init__
self.prep_tree()
File "/usr/share/system-config-cluster/MgmtTab.py", line 184, in prep_tree
nodes = self.command_handler.getNodesInfo(self.model_builder.getLockType())
File "/usr/share/system-config-cluster/CommandHandler.py", line 327, in
getNodesInfo
nd = NodeData(words[1],words[3],words[4])
IndexError: list index out of range
Here is some output from the cluster status tools:
[root@pg-ba-001 ~]# /usr/sbin/clustat
Member Status: Quorate
Member Name ID Status
------ ---- ---- ------
pg-hba-001 1 Online, Local, rgmanager
pg-hba-002 2 Offline
Service Name Owner (Last) State
------- ---- ----- ------ -----
service:pg-ba-vts1 pg-hba-001 started
service:pg-ba-vts2 (pg-hba-001) failed
[root@pg-ba-001 ~]# /usr/sbin/cman_tool nodes
Node Sts Inc Joined Name
1 M 4 2007-03-27 18:37:24 pg-hba-001
2 X 8 pg-hba-002
Maybe this could be fixed in the upcoming errate too. By the way: can you tell
me when this errata can be expected?
Kind regards,
Robert Hell
Fixing Product Name. Cluster Suite components were integrqated into Enterprise Linux Version 5.0. |