Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 154847

Summary: switching from DLM to GuLM causes traceback
Product: [Retired] Red Hat Cluster Suite Reporter: Corey Marthaler <cmarthal>
Component: redhat-config-clusterAssignee: Jim Parsons <jparsons>
Status: CLOSED NEXTRELEASE QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: cluster-maint
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-04-15 19:45:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Corey Marthaler 2005-04-14 15:25:34 UTC
Description of problem:
Traceback (most recent call last):
  File "/usr/sbin/system-config-cluster", line 370, in change_lockserver
    self.model_builder.switch_lockservers()
  File "/usr/share/system-config-cluster/ModelBuilder.py", line 532, in
switch_lockservers
    self.cluster_ptr.removeChild(self.CMAN_ptr)
  File "/usr/share/system-config-cluster/TagObject.py", line 17, in removeChild
    self.children.remove(child)
ValueError: list.remove(x): x not in list


Version-Release number of selected component (if applicable):
[root@tank-03 ~]# rpm -qa | grep system-config-cluster
system-config-cluster-0.9.30-1.0

Comment 1 Jim Parsons 2005-04-14 21:10:52 UTC
This error was caused as part of another action: Creating a DLM cluster from
scratch and then converting it. The code that creates a new DLM cluster was not
saving a pointer to the cman object. This is fixed now in 0.9.31-1.0

Comment 2 Corey Marthaler 2005-04-15 19:45:44 UTC
fix verified.