Comment 21 for bug 2003189

Kinetic SRU Verification:

The fix works, 2.4.54-2ubuntu1.5 fixes the bug.

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

I have installed apache2 using:

$ apt install apache2

Then I typed in:

$ apt policy apache2

The output:

apache2:
  Installed: 2.4.54-2ubuntu1.3
  Candidate: 2.4.54-2ubuntu1.3
  Version table:
 *** 2.4.54-2ubuntu1.3 500
        500 http://archive.ubuntu.com/ubuntu kinetic-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     2.4.54-2ubuntu1.2 500
        500 http://security.ubuntu.com/ubuntu kinetic-security/main amd64 Packages
     2.4.54-2ubuntu1 500
        500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages

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:

Serving HTTP on 127.0.0.1 port 8080 (http://127.0.0.1:8080/) ...
ProxyBalancer[0]Worker[0]Status: Init Ok
scripts: line 6: 203609 Killed python3 -m http.server --bind 127.0.0.1 8080
ProxyBalancer[0]Worker[0]Status: Init Err

Then, I enabled proposed.

Then I upgraded apache2 using:

$ apt install apache2=2.4.54-2ubuntu1.5

Later, I typed in:

$ apt policy apache2
to check if the installed version has changed, and we see that we have a new version installed (with a fix).

apache2:
  Installed: 2.4.54-2ubuntu1.5
  Candidate: 2.4.54-2ubuntu1.5
  Version table:
 *** 2.4.54-2ubuntu1.5 500
        500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     2.4.54-2ubuntu1.3 500
        500 http://archive.ubuntu.com/ubuntu kinetic-updates/main amd64 Packages
     2.4.54-2ubuntu1.2 500
        500 http://security.ubuntu.com/ubuntu kinetic-security/main amd64 Packages

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.

Jammy SRU Verification:

The same steps were performed for Jammy (obviously using Jammy container etc.). In Jammy - 2.4.52-1ubuntu4.6 fixes the bug and the problem does not exist anymore.