Bug 159231

Summary: another propagate traceback issue
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-06-07 22:45:55 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-31 19:04:48 UTC
Description of problem:
I had a valid cluster up and running and then I deleted the config on one
machine, I then created a new config from scratch on that machine with a bunch
of BS node names and devices. On the MGMT tab I get the cman_tool error which I
would expect cuz the cluster is in a googfy state now, but when I went to
propagate this file I see a traceback:

Traceback (most recent call last):
  File "/usr/sbin/system-config-cluster", line 436, in propagate
    self.command_handler.propagateConfig(CLUSTER_CONF_PATH)
  File "/usr/share/system-config-cluster/CommandHandler.py", line 399, in
propagateConfig
    raise CommandError("FATAL",PROPAGATE_ERROR % (err))
TypeError: not enough arguments for format string

Granted a customer would never do this, but there still shouldn't be a case
which causes this behavior.

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

How reproducible:
everytime.

Comment 1 Jim Parsons 2005-05-31 19:58:50 UTC
All fixed up in 0.9.70.....good test, btw. More like this one!

Comment 2 Corey Marthaler 2005-06-07 22:45:55 UTC
fix verified.