group.of.nepali.translators team mailing list archive

[Eric Desrochers <eric.desrochers@xxxxxxxxxxxxx>]

** Summary changed:

- [sru] Update sosreport to 3.9
+ [sru] Update sosreport to 3.8

** Tags removed: sosreport37

** Changed in: sosreport (Ubuntu Xenial)
       Status: In Progress => Won't Fix

** Changed in: sosreport (Ubuntu Bionic)
       Status: In Progress => Won't Fix

** Changed in: sosreport (Ubuntu Eoan)
       Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1825010

Title:
  [sru] Update sosreport to 3.8

Status in sosreport package in Ubuntu:
  Fix Released
Status in sosreport source package in Trusty:
  Won't Fix
Status in sosreport source package in Xenial:
  Won't Fix
Status in sosreport source package in Bionic:
  Won't Fix
Status in sosreport source package in Cosmic:
  Won't Fix
Status in sosreport source package in Disco:
  Won't Fix
Status in sosreport source package in Eoan:
  Won't Fix
Status in sosreport source package in Focal:
  Fix Released
Status in sosreport package in Debian:
  Fix Released

Bug description:
  [Impact]

  sosreport 3.8 has been released including further enhancements in core sosreport functionality:
  https://github.com/sosreport/sos/releases/tag/3.8

  It would be great to find sosreport v3.8 in supported stable releases,
  considering the fact that the release (especially LTSes) will be
  supported for a couple of years still:

  sosreport is widely use by Canonical support team to troubleshoot UA
  customer, other vendors and community users. These improvement will
  benefit all of them.

  sosreport 3.8 contains a number of enhancements, new features, and bug
  fixes. (See "Release Note" below)

  Just like we did for :
  - v3.5 (LP: #1734983)
  - v3.6 (LP: #1775195)

  [Test Case]

   * Install sosreport
   * Run sosreport
     - sosreport plugins are separated by subject (juju, MAAS, grub, zfs,...) and allow the capability to detect (based on file and package) if it exist and/or installed and then only run the necessary plugins based on the detection made.

  It creates a files under /tmp in the form of :
  /tmp/sosreport-sos38X-20190416160152.tar.xz      # Actual sosreport
  /tmp/sosreport-sos38X-20190416160152.tar.xz.md5  # MD5 checksum

  Only accessible by root user:
  -rw------- 1 root root 1619000 Apr 16 16:07 /tmp/sosreport-sos38X-20190416160152.tar.xz

  Ideally, since we can't test all plugins, it would be good to have a
  few testers using different HW, kernel, installation with a focus on
  juju, MAAS, LXD, canonical-livepatch, ....

  Looking for any error on the terminal while sosreport is running or
  post-sosreport run in /tmp/sosreport-*/sos_logs/

  [Regression Potential]

   * Risk is low.

   * We did some dogfooding on sosreport, but we can't test each
  individual plugins and scenarios one by one, that would just be
  impossible but we have tested the ones we considered important and
  Ubuntu/Canonical related (canonical-livepatch, MAAS, juju, snappy),
  Openstack, mandatory file (logs, dmidecode, installed-debs and so on)

   * Plugin bug is an eventuality, but they are usually easy to fix and
  the impact will be isolated to the plugin itself or section of the
  plugin. If a plugin has a bug the worst that could happen is that this
  particular plugin won't (or partially) collect information.

  [Other information]

  * Release note:
  https://github.com/sosreport/sos/releases/tag/3.8

  * Plugins:
  sosreport contains in total: 284 plugins

  - 185 plugins that used UbuntuPlugin and/or DebianPlugin that might
  been triggered at sosreport run.

  -  97 plugins not using UbuntuPlugin and/or DebianPlugin. Basically
  useless in a Ubuntu context.

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