Then I repeated the steps from the [Test Plan] section.
I've noticed that nothing has changed there, so the problem still exists because, as we could see in the output, the package version is not the one where the fix is.
Output:
INFO: Don't check /var/lib/postgresql/14/main during probe
WARNING: wal receiver process is not running
Then, I enabled proposed.
Then I upgraded resource-agents using:
$ apt install resource-agents=1:4.7.0-1ubuntu7.2
Later, I typed in:
$ apt policy resource-agents
to check if the installed version has changed, and we see that we have a new version installed (with a fix).
Jammy SRU Verification:
The fix works, 1:4.7.0-1ubuntu7.2 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 have installed resource-agents using:
$ apt install resource-agents
Then I typed in:
$ apt policy resource-agents
The output:
resource-agents: archive. ubuntu. com/ubuntu jammy-updates/ universe amd64 Packages dpkg/status 4.7.0-1ubuntu7 500 archive. ubuntu. com/ubuntu jammy/universe amd64 Packages
Installed: 1:4.7.0-1ubuntu7.1
Candidate: 1:4.7.0-1ubuntu7.1
Version table:
*** 1:4.7.0-1ubuntu7.1 500
500 http://
100 /var/lib/
1:
500 http://
Then I repeated the steps from the [Test Plan] section.
I've noticed that nothing has changed there, so the problem still exists because, as we could see in the output, the package version is not the one where the fix is.
Output:
INFO: Don't check /var/lib/ postgresql/ 14/main during probe
WARNING: wal receiver process is not running
Then, I enabled proposed.
Then I upgraded resource-agents using:
$ apt install resource- agents= 1:4.7.0- 1ubuntu7. 2
Later, I typed in:
$ apt policy resource-agents
to check if the installed version has changed, and we see that we have a new version installed (with a fix).
resource-agents: archive. ubuntu. com/ubuntu jammy-proposed/ universe amd64 Packages dpkg/status 4.7.0-1ubuntu7. 1 500 archive. ubuntu. com/ubuntu jammy-updates/ universe amd64 Packages
Installed: 1:4.7.0-1ubuntu7.2
Candidate: 1:4.7.0-1ubuntu7.2
Version table:
*** 1:4.7.0-1ubuntu7.2 500
500 http://
100 /var/lib/
1:
500 http://
Finally, when I repeated the steps from the [Test Plan] the problem did not exist; the warning was not present in the output. So the fix works.