Bug 158788

Summary: propagate traceback with multicast cluster
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-05-31 15:58:38 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:

Description Corey Marthaler 2005-05-25 19:00:21 UTC
Description of problem:
I had a gulm cluster which then I switched to a DLM multicast cluster and then
saw this error after propagating the file. The file did actually get propagated
however.

[root@morph-04 ~]# Traceback (most recent call last):
  File "/usr/sbin/system-config-cluster", line 447, in propagate
    self.command_handler.propagateCmanConfig(version)
  File "/usr/share/system-config-cluster/CommandHandler.py", line 393, in
propagateCmanConfig
    raise CommandError("FATAL",PROPAGATE_ERROR2 % (err))
NameError: global name 'PROPAGATE_ERROR2' is not defined


Version-Release number of selected component (if applicable):
-60

Comment 1 Jim Parsons 2005-05-25 21:48:00 UTC
Fixed in 0.9.64-1.0

Comment 2 Corey Marthaler 2005-05-31 15:58:38 UTC
fix verified.