Bug 158788 - propagate traceback with multicast cluster
Summary: propagate traceback with multicast cluster
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: redhat-config-cluster
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jim Parsons
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-05-25 19:00 UTC by Corey Marthaler
Modified: 2009-04-16 20:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-05-31 15:58:38 UTC
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.