Bug 193907 - cmirror init script is going to have to do something other than fail if gulm cluster is running
Summary: cmirror init script is going to have to do something other than fail if gulm ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: cmirror
Version: 4
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Jonathan Earl Brassow
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks: 180185
TreeView+ depends on / blocked
 
Reported: 2006-06-02 20:21 UTC by Corey Marthaler
Modified: 2010-04-27 14:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-27 14:53:27 UTC
Embargoed:

Attachments (Terms of Use)

Description Corey Marthaler 2006-06-02 20:21:18 UTC 
Description of problem:
This is related to bz 193597. Gulm users/customers who are going to upgrade to
the latest rhel4u4 cluster code will now have an init script failure at start
up. This is bad. It should check and then warn just like the case when the cman
and fenced init scripts run during a gulm config and vice versa.
Comment 2 Jonathan Earl Brassow 2006-07-06 04:22:47 UTC 
This won't take but a couple minutes... I just haven't gotten to it yet.

The cmirror init script isn't in the cluster tree, Chris Feist keeps the main copy.  If he would be willing, 
he could copy what is done in the other scripts.  Otherwise, I will do it when I get back and he'll need to 
rebuild that package.
Comment 3 Corey Marthaler 2006-07-07 21:02:15 UTC 
fix verified.
Comment 5 Alasdair Kergon 2010-04-27 14:53:27 UTC 
Assuming this VERIFIED fix got released.  Closing.
Reopen if it's not yet resolved.
Note You need to log in before you can comment on or make changes to this bug.