[Linux-cluster] on exiting maintenance mode

Andrew Beekhof andrew at beekhof.net
Tue Aug 26 07:40:50 UTC 2014


On 22 Aug 2014, at 10:37 am, Ferenc Wagner <wferi at niif.hu> wrote:

> Hi,
> 
> While my Pacemaker cluster was in maintenance mode, resources were moved
> (by hand) between the nodes as I rebooted each node in turn.  In the end
> the crm status output became perfectly empty, as the reboot of a given
> node removed from the output the resources which were located on the
> rebooted node at the time of entering maintenance mode.  I expected full
> resource discovery on exiting maintenance mode,

Version and logs?

The discovery usually happens at the point the cluster is started on a node.
Maintenance mode just prevents the cluster from doing anything about it.

> but it probably did not
> happen, as the cluster started up resources already running on other
> nodes, which is generally forbidden.  Given that all resources were
> running (though possibly migrated during the maintenance), what would
> have been the correct way of bringing the cluster out of maintenance
> mode?  This should have required no resource actions at all.  Would
> cleanup of all resources have helped?  Or is there a better way?
> -- 
> Thanks,
> Feri.
> 
> -- 
> Linux-cluster mailing list
> Linux-cluster at redhat.com
> https://www.redhat.com/mailman/listinfo/linux-cluster

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://listman.redhat.com/archives/linux-cluster/attachments/20140826/dd66ebe8/attachment.sig>


More information about the Linux-cluster mailing list