I did some research, pieced some commands together and got it working.
Just in case someone else has the same problem and stumbles on this 
thread, here is what I did:

# crm configure property maintenance-mode=true
# crm resource
# cleanup <resource-name>
# quit
# crm configure delete <resource-name>
Confirm status and configuration with `# crm status` and `# crm 
configure show` on both nodes.
# crm configure property maintenance-mode=false

Now check status again on both to make sure everything is OK and you're 
done!
I feel a lot better knowing that my failover is ready again.

Thanks for all the help,

Josh

On 12/25/2012 10:02 AM, Josh Bowling wrote:
> Apparently my last email's formatting went haywire, so I'm just sending
> it out again to make sure it's easy to read and (hopefully) respond to.
>
> Sorry for the late response, been really busy lately.
>
> What happened was that I was being stupid and changed some VMs around
> while Pacemaker/Corosync was running.
> When I forced one of the old VMs down, it triggered a failover. The
> secondary server didn't have the new VM data/settings yet, so I had to
> switch back to the primary.  The only problem was when I moved back to
> the primary server, it tried to start up one of the old VMs that no
> longer existed (they should have existed as far as CRM was concerned),
> so it was flagged as UNCLEAN.
>
> So, in order to get everything back on track, I need to switch to
> maintenance-mode?
> The secondary server is also running and `crm status` returns that the
> primary is UNCLEAN (online) and secondary is online.
>
> I've cleaned up the data/settings for the VMs on both servers to be the
> same and synced DRBD, but I'm not sure what I need to do to get the
> cluster perfect again. Mainly, like I said before, just get primary
> clean again and the crm configuration mirrored on both nodes.
>
> I have little experience with HA clusters (hence the rookie mistake
> noted above) so I'm a bit concerned as to how I can get everything right
> without making some stupid mistake again.
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to