[TEST CASE]
I used the same setup and procedure as described in the bug report above:
1. Monitor the failover with `crm_mon -rf` and `tail -f /var/log/pacemaker/pacemaker.log` on passive node (node02)
2. Stop Pacemaker and Corosync service on promoted node (node01) to trigger a failover to passive node (node02).
3. Restart the two services on the now stopped node (node01)
And then the same in the opposite direction:
4. Monitor the failover with `crm_mon -rf` and `tail -f /var/log/pacemaker/pacemaker.log` on passive node (node01)
5. Stop Pacemaker and Corosync service on promoted node (node02) to trigger a failover to passive node (node01).
6. Restart the two services on the now stopped node (node02)
[VERIFICATION DONE]
The failovers were triggered immediately and the migration of the services was successful.
The result was as expected.
Hi Steve
Thanks for the update.
I tested the package from the jammy-proposed repository and can confirm that the bug is fixed with this version.
[PACKAGE VERSION] 1ubuntu1~ ppa1 15.0-1ubuntu1~ ppa1 500 /ppa.launchpadc ontent. net/sergiodj/ drbd-utils/ ubuntu jammy/main amd64 Packages archive. ubuntu. com/ubuntu jammy-proposed/main amd64 Packages dpkg/status /mirror. nine.ch/ ubuntu jammy/main amd64 Packages
drbd-utils:
Installed: 9.15.0-1ubuntu0.1
Candidate: 9.15.0-
Version table:
9.
500 https:/
*** 9.15.0-1ubuntu0.1 500
500 http://
100 /var/lib/
9.15.0-1build2 500
500 https:/
[TEST CASE]
I used the same setup and procedure as described in the bug report above:
1. Monitor the failover with `crm_mon -rf` and `tail -f /var/log/ pacemaker/ pacemaker. log` on passive node (node02)
2. Stop Pacemaker and Corosync service on promoted node (node01) to trigger a failover to passive node (node02).
3. Restart the two services on the now stopped node (node01)
And then the same in the opposite direction:
4. Monitor the failover with `crm_mon -rf` and `tail -f /var/log/ pacemaker/ pacemaker. log` on passive node (node01)
5. Stop Pacemaker and Corosync service on promoted node (node02) to trigger a failover to passive node (node01).
6. Restart the two services on the now stopped node (node02)
[VERIFICATION DONE]
The failovers were triggered immediately and the migration of the services was successful.
The result was as expected.