** Description changed: [Impact] sosreport 3.6 has been released in June 2018 with further enhancements in core sosreport functionality. I already did the request for debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900818 and 3.6 has been uploaded in Debian since then (Thanks to caribou): sosreport | 3.6-1 | testing sosreport | 3.6-1 | unstable and I have synced sosreport (Debian->Ubuntu Disco). It would be great to have sosreport v3.6 SRU'd in supported stable releases once official release upstream, considering the fact that the release (especially LTSes) will be supported for a couple of years still: [https://www.ubuntu.com/about/release-cycle] Ubuntu 16.04 | support until 2023 Ubuntu 18.04 | support until 2024 sosreport is widely use by Canonical support team to troubleshoot UA customer and other vendors and community users. These improvement will benefit all of them. sosreport 3.6 contains a number of enhancements, new features, and bug fixes. (See "Release Note" below) Just like we did for v3.5 (LP: #1734983) [Test Case] * Install sosreport * Run sosreport - sosreport plugins are separated by subject (juju, MAAS, grub,zfs, ipsec, ...) 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. [Things identified during our testing] * [minor] juju plugin detection doesn't work if installed as a snap: https://github.com/sosreport/sos/issues/1475 Fix already submitted upstream. This is not a new thing, juju in sosreport have always been made for .deb so far. It's not a regression introduce in 3.6, and IMHO not a blocker for the current SRU. It could be patch later on when the upstream discussion/approval will be done. - * [major] Certain plugins may or may not substitute sensible - information such as password. Upstream fix found and applied : https://github.com/sosreport/sos/commit/b96bdab03f06408e162b1733b20e8ba9fbf8e012 + * [major] Certain plugins may or may not substitute sensible + information such as password. Upstream fix found and applied : https://github.com/sosreport/sos/commit/b96bdab03f06408e162b1733b20e8ba9fbf8e012 + d/p/fix-string-substitution-method.patch - * [minor] kernel plugin dont collect some tracing instance files + * [minor] kernel plugin dont collect some tracing instance files https://github.com/sosreport/sos/commit/d6379b5ba0f381ea8ec2403b9985100a946a5866 - Ubuntu Bug #1803735 - + Ubuntu Bug #1803735 + d/p/dont-collect-some-tracing-instance-files.patch + [Regression Potential] * Regression risk is low, as long as the core functionnality works (Package manager, ...) * autopkgtest reveal no regressions. * 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 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 collect system logs, debug information or anything this plugin was instructed to do, usually won't affect other plugin to perform as expected and/or sosreport to complete. [Other Info] [v3.6 Release notes] # https://github.com/sosreport/sos/releases/tag/3.6 [Original Description] sosreport 3.6 has been released in June 2018 with further enhancements in core sosreport functionality. A sync can be done since all Ubuntu patches has been integrated in 3.6 I already did the request for debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900818 and 3.6 has been uploaded in Debian since then (Thanks to caribou): sosreport | 3.6-1 | testing sosreport | 3.6-1 | unstable Now, it would be great to have sosreport v3.6 in Development Release & SRU'd in all supported stable release once official release upstream, considering the fact that the release will contain a number of enhancements, new features, and bug fixes and that sosreport is widely use by Canonical support team to troubleshoot UA customer. Just like we did for v3.5. [v3.6 Release notes] # https://github.com/sosreport/sos/releases/tag/3.6 The sos team is pleased to announce the release of sos-3.6. This is a significant release containing a number of enhancements, new features, and bug fixes, including: 29 new plugins: alternatives, ansible, btrfs, buildah, clear_containers, date, elastic, fibrechannel, host, kata_containers, lustre, memcached, mssql, networkmanager, nvme, omnipath_client, omnipath_manager, opendaylight, openstack_octavia, ovirt_provider_ovn, ovn_central, ovn_host, rear, release, runc, skydive, unpackaged, watchdog, wireless User and policy defined command line presets The ability to save and recall specific combinations of command line parameters Policy authors may define presets for specific situations, products or other uses (e.g. "cantboot", "rhel", "openshift" etc.). Size limits for external commands Certain commands produce large volumes of data, inflating report size (e.g. journalctl): the command collection interface now allows an arbitrary size limit to be applied, which includes memory used during the run (reducing sosreport's peak memory usage). Automatic file and command size limits Plugins that do not specify an explicit size limit for files or commands are now subject to the default value (specified with the --log-size command line option). Plugin authors may override this behaviour if needed Concurrent plugin execution Plugins are now run in parallel using a thread pool Reduces runtime by up to 50% (workload dependent) Command line --threads option to set the number of threads to use, or to disable parallel execution New profiles (including containers and the Apache webserver) major enhancements to core features and existing plugins: better package manager version information policy support for detecting package managed files fixed exit status propagation deprecated optparse replaced with argparse simplified and improved SoSOptions interface better error handling during interactive prompting allow journal collection by identifier allow collection of journal message catalogs support for collecting binary file data more fine-grained system plugins (date etc.) policy defined report file name patterns more human-readable report file names by default increased default log size (25MiB vs. 10MiB) support for forbidden path lists and forbid logging support for enabling plugins by kernel module name support for enabling plugins by executable name support for collecting eBPF (bpftool) data support for device information via add_udev_info() support for detecting and reporting unpackaged binaries optional collection of the RPMDB improved archive compression level and multithreading default log size increased from 10MiB to 25MiB improved debug logging and ENOSPC handling major updates to the IPA plugin major updates to the Docker plugin string decoding fixes DNF and Yum module support OpenShift 3.10 support Python3 fixes
** Description changed: [Impact] sosreport 3.6 has been released in June 2018 with further enhancements in core sosreport functionality. I already did the request for debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900818 and 3.6 has been uploaded in Debian since then (Thanks to caribou): sosreport | 3.6-1 | testing sosreport | 3.6-1 | unstable and I have synced sosreport (Debian->Ubuntu Disco). It would be great to have sosreport v3.6 SRU'd in supported stable releases once official release upstream, considering the fact that the release (especially LTSes) will be supported for a couple of years still: [https://www.ubuntu.com/about/release-cycle] Ubuntu 16.04 | support until 2023 Ubuntu 18.04 | support until 2024 sosreport is widely use by Canonical support team to troubleshoot UA customer and other vendors and community users. These improvement will benefit all of them. sosreport 3.6 contains a number of enhancements, new features, and bug fixes. (See "Release Note" below) Just like we did for v3.5 (LP: #1734983) [Test Case] * Install sosreport * Run sosreport - sosreport plugins are separated by subject (juju, MAAS, grub,zfs, ipsec, ...) 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. [Things identified during our testing] * [minor] juju plugin detection doesn't work if installed as a snap: https://github.com/sosreport/sos/issues/1475 Fix already submitted upstream. This is not a new thing, juju in sosreport have always been made for .deb so far. It's not a regression introduce in 3.6, and IMHO not a blocker for the current SRU. It could be patch later on when the upstream discussion/approval will be done. * [major] Certain plugins may or may not substitute sensible - information such as password. Upstream fix found and applied : https://github.com/sosreport/sos/commit/b96bdab03f06408e162b1733b20e8ba9fbf8e012 - d/p/fix-string-substitution-method.patch + information such as password. Upstream fix found and applied : + https://github.com/sosreport/sos/commit/b96bdab + - d/p/fix-string-substitution-method.patch * [minor] kernel plugin dont collect some tracing instance files - https://github.com/sosreport/sos/commit/d6379b5ba0f381ea8ec2403b9985100a946a5866 + https://github.com/sosreport/sos/commit/d6379b5 Ubuntu Bug #1803735 - d/p/dont-collect-some-tracing-instance-files.patch + - d/p/dont-collect-some-tracing-instance-files.patch [Regression Potential] * Regression risk is low, as long as the core functionnality works (Package manager, ...) * autopkgtest reveal no regressions. * 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 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 collect system logs, debug information or anything this plugin was instructed to do, usually won't affect other plugin to perform as expected and/or sosreport to complete. [Other Info] [v3.6 Release notes] # https://github.com/sosreport/sos/releases/tag/3.6 [Original Description] sosreport 3.6 has been released in June 2018 with further enhancements in core sosreport functionality. A sync can be done since all Ubuntu patches has been integrated in 3.6 I already did the request for debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900818 and 3.6 has been uploaded in Debian since then (Thanks to caribou): sosreport | 3.6-1 | testing sosreport | 3.6-1 | unstable Now, it would be great to have sosreport v3.6 in Development Release & SRU'd in all supported stable release once official release upstream, considering the fact that the release will contain a number of enhancements, new features, and bug fixes and that sosreport is widely use by Canonical support team to troubleshoot UA customer. Just like we did for v3.5. [v3.6 Release notes] # https://github.com/sosreport/sos/releases/tag/3.6 The sos team is pleased to announce the release of sos-3.6. This is a significant release containing a number of enhancements, new features, and bug fixes, including: 29 new plugins: alternatives, ansible, btrfs, buildah, clear_containers, date, elastic, fibrechannel, host, kata_containers, lustre, memcached, mssql, networkmanager, nvme, omnipath_client, omnipath_manager, opendaylight, openstack_octavia, ovirt_provider_ovn, ovn_central, ovn_host, rear, release, runc, skydive, unpackaged, watchdog, wireless User and policy defined command line presets The ability to save and recall specific combinations of command line parameters Policy authors may define presets for specific situations, products or other uses (e.g. "cantboot", "rhel", "openshift" etc.). Size limits for external commands Certain commands produce large volumes of data, inflating report size (e.g. journalctl): the command collection interface now allows an arbitrary size limit to be applied, which includes memory used during the run (reducing sosreport's peak memory usage). Automatic file and command size limits Plugins that do not specify an explicit size limit for files or commands are now subject to the default value (specified with the --log-size command line option). Plugin authors may override this behaviour if needed Concurrent plugin execution Plugins are now run in parallel using a thread pool Reduces runtime by up to 50% (workload dependent) Command line --threads option to set the number of threads to use, or to disable parallel execution New profiles (including containers and the Apache webserver) major enhancements to core features and existing plugins: better package manager version information policy support for detecting package managed files fixed exit status propagation deprecated optparse replaced with argparse simplified and improved SoSOptions interface better error handling during interactive prompting allow journal collection by identifier allow collection of journal message catalogs support for collecting binary file data more fine-grained system plugins (date etc.) policy defined report file name patterns more human-readable report file names by default increased default log size (25MiB vs. 10MiB) support for forbidden path lists and forbid logging support for enabling plugins by kernel module name support for enabling plugins by executable name support for collecting eBPF (bpftool) data support for device information via add_udev_info() support for detecting and reporting unpackaged binaries optional collection of the RPMDB improved archive compression level and multithreading default log size increased from 10MiB to 25MiB improved debug logging and ENOSPC handling major updates to the IPA plugin major updates to the Docker plugin string decoding fixes DNF and Yum module support OpenShift 3.10 support Python3 fixes ** Description changed: [Impact] sosreport 3.6 has been released in June 2018 with further enhancements in core sosreport functionality. I already did the request for debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900818 and 3.6 has been uploaded in Debian since then (Thanks to caribou): sosreport | 3.6-1 | testing sosreport | 3.6-1 | unstable and I have synced sosreport (Debian->Ubuntu Disco). It would be great to have sosreport v3.6 SRU'd in supported stable releases once official release upstream, considering the fact that the release (especially LTSes) will be supported for a couple of years still: [https://www.ubuntu.com/about/release-cycle] Ubuntu 16.04 | support until 2023 Ubuntu 18.04 | support until 2024 sosreport is widely use by Canonical support team to troubleshoot UA customer and other vendors and community users. These improvement will benefit all of them. sosreport 3.6 contains a number of enhancements, new features, and bug fixes. (See "Release Note" below) Just like we did for v3.5 (LP: #1734983) [Test Case] * Install sosreport * Run sosreport - sosreport plugins are separated by subject (juju, MAAS, grub,zfs, ipsec, ...) 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. [Things identified during our testing] * [minor] juju plugin detection doesn't work if installed as a snap: https://github.com/sosreport/sos/issues/1475 Fix already submitted upstream. This is not a new thing, juju in sosreport have always been made for .deb so far. It's not a regression introduce in 3.6, and IMHO not a blocker for the current SRU. It could be patch later on when the upstream discussion/approval will be done. * [major] Certain plugins may or may not substitute sensible - information such as password. Upstream fix found and applied : - https://github.com/sosreport/sos/commit/b96bdab + information such as password. Upstream fix found and applied : + https://github.com/sosreport/sos/commit/b96bdab - d/p/fix-string-substitution-method.patch * [minor] kernel plugin dont collect some tracing instance files - https://github.com/sosreport/sos/commit/d6379b5 - Ubuntu Bug #1803735 + https://github.com/sosreport/sos/commit/d6379b5 + LP: #1803735 - d/p/dont-collect-some-tracing-instance-files.patch [Regression Potential] * Regression risk is low, as long as the core functionnality works (Package manager, ...) * autopkgtest reveal no regressions. * 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 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 collect system logs, debug information or anything this plugin was instructed to do, usually won't affect other plugin to perform as expected and/or sosreport to complete. [Other Info] [v3.6 Release notes] # https://github.com/sosreport/sos/releases/tag/3.6 [Original Description] sosreport 3.6 has been released in June 2018 with further enhancements in core sosreport functionality. A sync can be done since all Ubuntu patches has been integrated in 3.6 I already did the request for debian : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900818 and 3.6 has been uploaded in Debian since then (Thanks to caribou): sosreport | 3.6-1 | testing sosreport | 3.6-1 | unstable Now, it would be great to have sosreport v3.6 in Development Release & SRU'd in all supported stable release once official release upstream, considering the fact that the release will contain a number of enhancements, new features, and bug fixes and that sosreport is widely use by Canonical support team to troubleshoot UA customer. Just like we did for v3.5. [v3.6 Release notes] # https://github.com/sosreport/sos/releases/tag/3.6 The sos team is pleased to announce the release of sos-3.6. This is a significant release containing a number of enhancements, new features, and bug fixes, including: 29 new plugins: alternatives, ansible, btrfs, buildah, clear_containers, date, elastic, fibrechannel, host, kata_containers, lustre, memcached, mssql, networkmanager, nvme, omnipath_client, omnipath_manager, opendaylight, openstack_octavia, ovirt_provider_ovn, ovn_central, ovn_host, rear, release, runc, skydive, unpackaged, watchdog, wireless User and policy defined command line presets The ability to save and recall specific combinations of command line parameters Policy authors may define presets for specific situations, products or other uses (e.g. "cantboot", "rhel", "openshift" etc.). Size limits for external commands Certain commands produce large volumes of data, inflating report size (e.g. journalctl): the command collection interface now allows an arbitrary size limit to be applied, which includes memory used during the run (reducing sosreport's peak memory usage). Automatic file and command size limits Plugins that do not specify an explicit size limit for files or commands are now subject to the default value (specified with the --log-size command line option). Plugin authors may override this behaviour if needed Concurrent plugin execution Plugins are now run in parallel using a thread pool Reduces runtime by up to 50% (workload dependent) Command line --threads option to set the number of threads to use, or to disable parallel execution New profiles (including containers and the Apache webserver) major enhancements to core features and existing plugins: better package manager version information policy support for detecting package managed files fixed exit status propagation deprecated optparse replaced with argparse simplified and improved SoSOptions interface better error handling during interactive prompting allow journal collection by identifier allow collection of journal message catalogs support for collecting binary file data more fine-grained system plugins (date etc.) policy defined report file name patterns more human-readable report file names by default increased default log size (25MiB vs. 10MiB) support for forbidden path lists and forbid logging support for enabling plugins by kernel module name support for enabling plugins by executable name support for collecting eBPF (bpftool) data support for device information via add_udev_info() support for detecting and reporting unpackaged binaries optional collection of the RPMDB improved archive compression level and multithreading default log size increased from 10MiB to 25MiB improved debug logging and ENOSPC handling major updates to the IPA plugin major updates to the Docker plugin string decoding fixes DNF and Yum module support OpenShift 3.10 support Python3 fixes ** Summary changed: - [sync][sru]sosreport v3.6 + [sync][sru] Backport of sosreport v3.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775195 Title: [sync][sru] Backport of sosreport v3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1775195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
