Description of problem:
I was attempting to use a VG that wasn't cluster, so the script saw that and attempted to fall back to the local locking/tag based method. The problem was that all it told me was:
Aug 19 15:16:27 taft-02 rgmanager: HA LVM: Improper setup detected
Aug 19 15:16:27 taft-02 rgmanager: WARNING: An improper setup can cause data corruption!
Version-Release number of selected component (if applicable):
*** This bug has been marked as a duplicate of bug 633856 ***
This is because the log messages started with -, causing weird getopt behavior.
These messages all exist -- just that they were getting eaten by getopt; this is resolved by changing the - to * as per bug 633856