Bug 159231 - another propagate traceback issue
another propagate traceback issue
Status: CLOSED NEXTRELEASE
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: redhat-config-cluster (Show other bugs)
4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jim Parsons
Cluster QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-31 15:04 EDT by Corey Marthaler
Modified: 2009-04-16 16:09 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-06-07 18:45:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Corey Marthaler 2005-05-31 15:04:48 EDT
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 15:58:50 EDT
All fixed up in 0.9.70.....good test, btw. More like this one!
Comment 2 Corey Marthaler 2005-06-07 18:45:55 EDT
fix verified.

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