Red Hat Bugzilla – Bug 193907
cmirror init script is going to have to do something other than fail if gulm cluster is running
Last modified: 2010-04-27 10:53:27 EDT
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.
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.
Assuming this VERIFIED fix got released. Closing.
Reopen if it's not yet resolved.