** 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 : + Just like we did for : - v3.5 (LP: #1734983) - - v3.6 (LP: #775195) + - 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. + * 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 : + 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 functionnality works + * Regression risk is low, as long as the core functionnality works (Package manager, ...) - * We did some dogfooding on sosreport, but we can't test each + * 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, ...). - * Plugin bug is an eventuality, but they are usually easy to fix and + * 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. [Original Description] https://github.com/sosreport/sos/releases/tag/3.7 --- The sos team is pleased to announce the release of sos-3.7. This is a significant release containing a large number of enhancements, new features, and bug fixes, including: New distribution policies for CentOS and Amazon Linux 19 new plugins: candlepin, cifs, cockpit, composer, crio, gssproxy, katello, openstack_novajoin, ovirt_node, peripety, podman, pulp, rasdaemon, rhcos, rhv_analyzer, rpmostree, ruby, stratis, sudo Obsolete IPSec plugin removed (in favour of OpenSwan) Support for passphrase and key based encryption of the report archive Ability to encrypt the archive using GPG, with either a key or passphrase New --encrypt-key and --encrypt-pass arguments to sosreport Improved handling of paths containing directory symbolic links (for e.g. /sys) Previous versions of sos would replace intermediate path components that contain a symbolic link to a directory in the host file system with an actual directory in the report archive. The host file system structure is now reflected properly in the report directory structure. New InitSystem abstraction Allows plugin and collection enablement based on the presence of a service, and methods to test whether a given service is currently running LVM2 plugin enhancements Locking fixes for LVM2 metadata and reporting output capture Additional LVM2 logical volume manager report data Append plugin exceptions to sos_logs/*-plugin-exception.txt Previous versions of sos would overwrite earlier exceptions if more than one exception occurred while running a plugin (for example, when an exception occurs in both setup() and postproc() phases). Dry run mode (--dry-run) Allows sos to run without collecting data, or executing commands, and proving a log of actions that would have been taken by a normal run on the current system configuration. Plugin API enhancements SoSPredicates for gating collection on service and kernel module presence, and during dry-run mode Significant enhancements to core features and existing plugins Fixes to threaded exception handling, and interactive debugging with --debug Support for OpenShift 3.10 deployments Improved multipath data collection Fixed RHEL Atomic default command line preset Support for PowerPC DLPAR and LPM logs Additional FIPS and crypto-policies data collection Test suite and CI support for Python-3.7 final Additional systemd listings and statuses Support for user-controlled per-plugin timeouts Do not leave report artefacts in TMP when executing list commands Improvements to command termination in the event of plugin timeouts Policy support for Red Hat Enterprise Linux 8.0 Improved STONITH and watchdog data collection for Pacemaker clusters Support for Debian journald logging in the logs plugin New built-in 'cantboot' preset for collecting information relevant to failed boots Ability to disable default presets on the command line (--preset=none) Support for setting all sosreport command line options (including global and plugin options) in the sos.conf configuration file The deprecated XML reporting module has been removed Continuous integration with the LGTM static analyser (rated 'A') Apache plugin fixed to support --log-size global option Native support for collecting foreman-debug equivalent data in sos ---
** 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 functionnality works + * Regression risk is low, as long as the core functionality works (Package manager, ...) * 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, ...). * 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. - [Original Description] + [Other information] + + * Release note: https://github.com/sosreport/sos/releases/tag/3.7 - - --- - The sos team is pleased to announce the release of sos-3.7. This is a significant release containing a large number of enhancements, new features, and bug fixes, including: - - New distribution policies for CentOS and Amazon Linux - - 19 new plugins: - candlepin, cifs, cockpit, composer, crio, gssproxy, katello, openstack_novajoin, ovirt_node, peripety, podman, pulp, rasdaemon, rhcos, rhv_analyzer, rpmostree, ruby, stratis, sudo - - Obsolete IPSec plugin removed (in favour of OpenSwan) - - Support for passphrase and key based encryption of the report archive - - Ability to encrypt the archive using GPG, with either a key or passphrase - New --encrypt-key and --encrypt-pass arguments to sosreport - Improved handling of paths containing directory symbolic links (for e.g. /sys) - - Previous versions of sos would replace intermediate path components that contain a symbolic link to a directory in the host file system with an actual directory in the report archive. The host file system structure is now reflected properly in the report directory structure. - New InitSystem abstraction - - Allows plugin and collection enablement based on the presence of a service, and methods to test whether a given service is currently running - LVM2 plugin enhancements - - Locking fixes for LVM2 metadata and reporting output capture - Additional LVM2 logical volume manager report data - Append plugin exceptions to sos_logs/*-plugin-exception.txt - - Previous versions of sos would overwrite earlier exceptions if more than one exception occurred while running a plugin (for example, when an exception occurs in both setup() and postproc() phases). - Dry run mode (--dry-run) - - Allows sos to run without collecting data, or executing commands, and proving a log of actions that would have been taken by a normal run on the current system configuration. - Plugin API enhancements - - SoSPredicates for gating collection on service and kernel module presence, and during dry-run mode - Significant enhancements to core features and existing plugins - - Fixes to threaded exception handling, and interactive debugging with - --debug - - Support for OpenShift 3.10 deployments - - Improved multipath data collection - - Fixed RHEL Atomic default command line preset - - Support for PowerPC DLPAR and LPM logs - - Additional FIPS and crypto-policies data collection - - Test suite and CI support for Python-3.7 final - - Additional systemd listings and statuses - - Support for user-controlled per-plugin timeouts - - Do not leave report artefacts in TMP when executing list commands - - Improvements to command termination in the event of plugin timeouts - - Policy support for Red Hat Enterprise Linux 8.0 - - Improved STONITH and watchdog data collection for Pacemaker clusters - - Support for Debian journald logging in the logs plugin - - New built-in 'cantboot' preset for collecting information relevant to - failed boots - - Ability to disable default presets on the command line (--preset=none) - - Support for setting all sosreport command line options (including global - and plugin options) in the sos.conf configuration file - - The deprecated XML reporting module has been removed - - Continuous integration with the LGTM static analyser (rated 'A') - - Apache plugin fixed to support --log-size global option - - Native support for collecting foreman-debug equivalent data in sos - --- -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
