Comment 10 for bug 2012740

Fix works, 2.1.2-1ubuntu3.1 fixes the bug.

I've created the jammy container using steps from the [Test Plan] section listed above in the Bug Description and inside that container I typed in:

$ apt policy pacemaker

The output:

pacemaker:
  Installed: 2.1.2-1ubuntu3
  Candidate: 2.1.2-1ubuntu3.1
  Version table:
     2.1.2-1ubuntu3.1 500
        500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
 *** 2.1.2-1ubuntu3 500
        500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        100 /var/lib/dpkg/status

Then I repeated steps from [Test Plan] section.

I've noticed that nothing has changed there, so the problem still existed, because as we could see in the output, the package version was not the one where the fix is.

Then I've upgraded pacemaker using:
$ apt install pacemaker=2.1.2-1ubuntu3.1

Later I've typed in:

$ apt policy pacemaker
to check if installed version is changed and we see that we have new version installed (with fix)

pacemaker:
  Installed: 2.1.2-1ubuntu3.1
  Candidate: 2.1.2-1ubuntu3.1
  Version table:
 *** 2.1.2-1ubuntu3.1 500
        500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     2.1.2-1ubuntu3 500
        500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

Finally when I repeated steps from the [Test Plan] the problem did not exist, no crash file at /var/crash/. So the fix works.