** Description changed: [Impact] sosreport 3.7 has been released including further enhancements in core sosreport functionality: https://github.com/sosreport/sos/releases/tag/3.7 It would be great to find sosreport v3.7 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.7 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-sos37xenial-20190416160152.tar.xz # Actual sosreport /tmp/sosreport-sos37X-20190416160152.tar.xz.md5 # MD5 checksum Only accessible by root user: -rw------- 1 root root 1619000 Apr 16 16:07 /tmp/sosreport-sos37X-20190416160152.tar.xz [Regression Potential] - * Regression risk is low, as long as the core functionality works - (Package manager, ...) + * Risk is low. * We did some dogfooding on sosreport, but we can't test each - individual plugins and scenarios one by one, that would be impossible - but we have tested the ones we considered important and Ubuntu/Canonical - related (canonical-livepatch, MAAS, juju, openstack, ...). + 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 system logs, debug - information or anything this plugin was instructed to do. It won't - affect other plugins to run as expected. + particular plugin won't (or partially) collect information. [Other information] * Release note: https://github.com/sosreport/sos/releases/tag/3.7
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825010 Title: [sru] Backport of sosreport v3.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1825010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
