Seems like something is broken in the "package=" mechanism behaviour.
The no longer running plugins that we have identified coincide with recent 
package add commit :

18ab068 [dbus] add missing packages list
3d0ea25 [cron] add missing packages list
0348833 [acpid] add missing packages list
....

After a bisect the upstream offending commit is :
82e4ee2 [sosreport] add per-plugin package verification lists

- Eric

-- 
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1734983

Title:
  Request to backport sosreport v3.5

Status in sosreport package in Ubuntu:
  Fix Released
Status in sosreport source package in Trusty:
  New
Status in sosreport source package in Xenial:
  New
Status in sosreport source package in Zesty:
  New
Status in sosreport source package in Artful:
  New
Status in sosreport source package in Bionic:
  Fix Released

Bug description:
  *** DRAFT in progress ***
  [Impact]

  Canonical support team (AKA STS) largely depend on sosreport package
  to troubleshoot system.

  sosreport is always in constant development including new bugfixes,
  new features such as new plugins[1], .... that can be interesting to
  have in a support context.

  v3.5 is already found in devel release (bionic). We create this LP in
  the attempt to justify the SRU of v3.5 backport into current supported
  stable releases.

  [1] - New plugins for :
          * perl
          * boom
          * vdo
          * os_net_config
          * conntrackd
          * ovirt_imageio
          * nss
          * sas3ircu
          * openstack_aodh
          * docker_distribution
          * gluster_block
          * snappy

      Plugin API enhancements
          * Plugin triggers by executable name
          * Improved log size limit handling
          * Better handling of compressed log files
          * Per-plugin package verification lists

      Updates to 227 plugins

  [Test Case]

   * Install sosreport
     $ apt-get install sosreport

   * Run sosreport
     $ sosreport -a
     $ sosreport -o <PLUGIN>
     $ ...

   * Make sure it generate a tar.xz file in /tmp in the form of
     "/tmp/sosreport-<HOSTNAME>-<DATE>.tar.xz"

   * Extract files from archive
     tar Jxvf /tmp/sosreport-<HOSTNAME>-<DATE>.tar.xz

   * Look the content of sosreport, make sure the information is
  accurate and valid, ....

  [Regression Potential]

   * We don't expect regression, autopkgtest[2] didn't reveal any nor
  our testing.

  [2] - See Comment #1

  [Other Info]

   * Sosreport upstream :
     https://github.com/sosreport/sos

   * rmadison -u debian,ubuntu sosreport
  debian:
  sosreport  | 3.2-2                | oldstable          | source, amd64, 
arm64, armel, armhf, i386, mips, mipsel, powerpc, ppc64el, s390x
  sosreport  | 3.2-2                | oldstable-kfreebsd | source, 
kfreebsd-amd64, kfreebsd-i386
  sosreport  | 3.3+git50-g3c0349b-2 | stable             | source, amd64, 
arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
  sosreport  | 3.5-1                | testing            | source, amd64, 
arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
  sosreport  | 3.5-1                | unstable           | source, amd64, 
arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, 
mips64el, mipsel, powerpc, ppc64el, s390x
  ubuntu:
   sosreport | 3.0-1~ubuntu12.04.1          | precise-backports/universe | 
source, amd64, armel, armhf, i386, powerpc
   sosreport | 3.1-1ubuntu2                 | trusty                     | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.1-1ubuntu2.2               | trusty-security            | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.2-2~ubuntu14.04.1          | trusty-backports           | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.2+git276-g7da50d6-3ubuntu1 | xenial                     | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
   sosreport | 3.3+git50-g3c0349b-2         | zesty                      | 
source, amd64, arm64, armhf, i386, ppc64el, s390x
   sosreport | 3.4-1~ubuntu14.04.1          | trusty-updates             | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el
   sosreport | 3.4-1~ubuntu16.04.1          | xenial-updates             | 
source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
   sosreport | 3.4-1~ubuntu17.04.1          | zesty-updates              | 
source, amd64, arm64, armhf, i386, ppc64el, s390x
   sosreport | 3.4-1                        | artful                     | 
source, amd64, arm64, armhf, i386, ppc64el, s390x
   sosreport | 3.5-1                        | bionic                     | 
source, amd64, arm64, armhf, i386, ppc64el, s390x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1734983/+subscriptions

-- 
Mailing list: https://launchpad.net/~sts-sponsors
Post to     : sts-sponsors@lists.launchpad.net
Unsubscribe : https://launchpad.net/~sts-sponsors
More help   : https://help.launchpad.net/ListHelp

Reply via email to