[Bug 1927996] Autopkgtest regression report (update-notifier/3.192.1.11)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted update-notifier (3.192.1.11) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

update-manager/1:18.04.11.13 (i386, s390x, arm64, armhf, ppc64el, amd64)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#update-notifier

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-notifier in Ubuntu.
https://bugs.launchpad.net/bugs/1927996

Title:
  /usr/lib/update-notifier/apt_check.py:FileNotFoundError:/usr/lib
  /update-
  notifier/apt_check.py at 16:check_output:run:__init__:_execute_child

Status in update-notifier package in Ubuntu:
  Fix Released
Status in update-notifier source package in Xenial:
  Fix Committed
Status in update-notifier source package in Bionic:
  Fix Committed
Status in update-notifier source package in Focal:
  Fix Committed
Status in update-notifier source package in Hirsute:
  Fix Committed

Bug description:
  update-notifier-common does not depend on lsb-release and both
  apt_check.py and apt-cdrom-check both utilize lsb_release.

  The Ubuntu Error Tracker has been receiving reports about a problem regarding update-notifier.  This problem was most recently seen with package version 3.192.40.1, the problem page at https://errors.ubuntu.com/problem/b26aeaa1e162c894747c195ce1b13a70c981e3eb contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

  --------------------------------------------------------------------------

  [Impact]
  Because update-notifier does not explicit have the `lsb-release` package as a dependency, users may install the package and rely on `apt-cdrom-check` to work, but it will fail, since it runs
  the `lsb_release -sr` command on it.

  [Test case]

  To reproduce the issue:

  1. Launch a xenial container
  2. Install update-notifier on it
  3. Run apt-cache depends update-notifier-common
  4. Verify that lsb-release does not appear

  To verify that the error is fixed:

  1. Install the new update-notifier from this ppa:
  https://launchpad.net/~lamoura/+archive/ubuntu/update-notifier-test-ppa/
  2. Run apt-cache depends update-notifier-common
  3. Verify that lsb-release will now appear as a dependency

  [Where problems could occur]

  We are only adding a missing dependency to the package. I cannot think
  of a problem that this might cause to the users of this package.

  [Discussion]

  We can verify that `apt-cdrom-check` does make use of the
  `lsb_release` command. Since we don't have that dependency on the
  package control file, errors can appear when users are
  executing/relying on that script.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1927996/+subscriptions