hacluster charm doesn't check on the upgrade whether pacemaker resources are configured

[Tytus Kurek]

Let's assume I have the hacluster charm from some old release (for example 17.02). When I deploy designate application and designate-hacluster application from this old charm, and when I relate them:

juju deploy designate
juju deploy <old hacluster charm> designate-hacluster
juju add-relation designate designate-hacluster

the designate-hacluster application does not setup pacemaker resources:

root@juju-2a1df2-6-lxd-13:~# crm status
Last updated: Fri May 4 08:53:37 2018
Last change: Fri May 4 08:40:20 2018 via cibadmin on juju-2a1df2-7-lxd-10
Stack: corosync
Current DC: juju-2a1df2-6-lxd-13 (1005) - partition with quorum
Version: 1.1.10-42f2063
3 Nodes configured
0 Resources configured

Online: [ juju-2a1df2-6-lxd-13 juju-2a1df2-7-lxd-10 juju-2a1df2-8-lxd-10 ]

I don't know why it happens, but I'd expect upgrading to the latest stable charm version (18.02) would fix the problem. However, upgrading doesn't fix the problem - I have to fully re-deploy everything. In my opinion the hacluster charm should check on the upgrade whether the resources are configured and attempt to configure them if they're missing.

[James Page (james-page)]

Indeed the hacluster charm does not re-asses the hanode relation in the event that the charm is upgraded.

I'm going to mark this as a Low priority; we had changes in the hanode relation to support py3 which was a bit of a one-off exercise; any previous deployed environments (with matching charm versions) should upgrade OK.