Dell Unity: SUSE limitation of Pacemaker (HA service) when user upgrades from pre-Unity v5.1 to Unity v5.1 (User Correctable)

Pacemaker compatibility issues seen during upgrade from pre-Unity v5.1 to Unity v5.1.

The Pacemaker compatibility issues can be seen during an upgrade from pre-Unity v5.1 to Unity v5.1. The issue is caused while the CIB (Cluster Information Base) is being upgraded to the new version. The older version cannot join the cluster again if it quits unexpectedly. 

Users may observe symptoms like this when one SP is running the older version of Unity OE while the other SP is running a newer version. This can happen when the option to "Automatically Reboot Storage Processors" is deselected for the upgrade, and an unexpected SP reboot occurs on the SP that has not yet been upgraded.

No action needed for NDU upgrade to v5.1 using the default "Automatically Reboot Storage Processors" option.  The issue will automatically resolve itself once the upgrade is completed.

If "Automatically Reboot Storage Processors" was deselected for the upgrade, resume the NDU to Unity v5.1 immediately, which should resolve the issue.

Please note: The default option during a software upgrade is to automatically reboot both storage processors, one-at-a-time, as soon as the software upgrade image is staged and the system is prepared for upgrade.

SUSE has no plans currently to fix this known Pacemaker compatible limitation.