Bind9 service file for 20.04 and older is missing Restart parameter

I think this should be included in the first Focal MRE we will have for bind. The MRE does not cover bionic, so for that I think we should use block-proposed-bionic and piggy-back this update on whatever the next bigger update for bind9 in bionic is.

I added the tags. I wanted to accept focal, but there is a focal bind9 package in proposed already, pending SRU verification[1]. Since the block-proposed tags are in place, I will accept the bionic upload even though the focal one won't be there yet. As soon as the pending focal sru verification is done, we can either accept this focal upload into proposed, or perhaps by then the focal bind9 MRE update will be done, and will include this fix.

1. https://launchpad.net/bugs/1997375

Hello Blažej, or anyone else affected,

Accepted bind9 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bind9/1:9.11.3+dfsg-1ubuntu1.19 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Blažej, or anyone else affected,

Accepted bind9 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bind9/1:9.16.1-0ubuntu2.14 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Slight change of plans: the focal upload is including the fix for #1997375, which was in proposed already, so these two can be verified together and I'm dropping the block-proposed tag for focal.

I verified this one with the following steps:

focal)

On a clean install:

Install bind9 and verify the named service is running:

# systemctl status named

Kill the named process

# pkill -9 named

and verify it is not automatically re-started:

# systemctl status named

Restart the service

# systemctl start named

and install the proposed fixed bind9 package in the -proposed pocket.

Verify that the named service is running. Then, kill it again

# pkill -9 named

Now, the service should re-start automatically.

bionic)

Same steps as with focal, but the systemd service name is now bind9.

This bug was fixed in the package bind9 - 1:9.16.1-0ubuntu2.14

---------------
bind9 (1:9.16.1-0ubuntu2.14) focal; urgency=medium

  * d/bind9.named.service: restart the named service on failure.
    (LP: #2006054)

bind9 (1:9.16.1-0ubuntu2.13) focal; urgency=medium

  * d/p/lp1997375-segfault-isc-nm-tcp-send.patch: Fix segfault on
    isc__nm_tcpdns_send by moving the tcpdns processing to another
    thread. (LP: #1997375)

 -- Athos Ribeiro <email address hidden> Fri, 03 Mar 2023 12:37:25 -0300

The verification of the Stable Release Update for bind9 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Andreas: seeing that bionic is going EOL, I see two options for this package: we either release it to -updates (dropping the block-proposed tag) or we remove it from -proposed and make sure to land it through the ESM PPA. Which one do you prefer?

Leave it in proposed, with the blocked tag, and the ESM team can pick it up the next time bind9 will have a security update in bionic.

For ESM purposes we concluded that we would like to leave this in -proposed please, following discussions with the ESM product manager and the SRU team.