Hi, Did you run the ha update like a rolling update, so one node with current version online, the other down. Than updating the offline node, reentering the cluster again? In this case I would think the cluster is ok but still only supports the old options. Its different from the situation'when you would restart both nodes with only one system updated. If I got it corredctly only the first method is recommended.
Besst regards Fabian Ulrich Windl <[email protected]> schrieb: >Hi! > >when trying to restart a Xen VM after installing updates in the gust I see >some funny messages (one node is at SLES11 SP2, while the other node is at >SLES11 SP3): > >First attempt: >h05:~ # crm resource restart prm_xen_v04 >INFO: ordering prm_xen_v04 to stop >No messages received in 30 seconds.. aborting >WARNING: crmadmin -S h01 unexpected output: (exit code: 253) >h05:~ # crmadmin -S 01 >Status of crmd@h01: S_IDLE (ok) > >Second attempt: >h05:~ # crm resource restart prm_xen_v04 >INFO: ordering prm_xen_v04 to stop >No messages received in 30 seconds.. aborting >WARNING: can't find DC > >However both nodes are online: >h05:~ # crm_mon -1Arf >Last updated: Mon Dec 23 11:52:44 2013 >Last change: Mon Dec 23 11:49:59 2013 by root via cibadmin on h05 >Stack: openais >Current DC: h01 - partition with quorum >Version: 1.1.7-77eeb099a504ceda05d648ed161ef8b1582c7daf >2 Nodes configured, 2 expected votes >18 Resources configured. > > >Online: [ h01 h05 ] >[...] > >Is it when running the new crm shell (SP3) for a DC that is still SP2? > >Regards, >Ulrich > > >_______________________________________________ >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
