| 2019-04-16 15:42:08 |
Eric Desrochers |
bug |
|
|
added bug |
| 2019-04-16 15:42:18 |
Eric Desrochers |
nominated for series |
|
Ubuntu Ee-series |
|
| 2019-04-16 15:42:18 |
Eric Desrochers |
bug task added |
|
sosreport (Ubuntu Ee-series) |
|
| 2019-04-16 15:42:25 |
Eric Desrochers |
sosreport (Ubuntu Ee-series): assignee |
|
Eric Desrochers (slashd) |
|
| 2019-04-16 15:42:28 |
Eric Desrochers |
sosreport (Ubuntu Ee-series): importance |
Undecided |
Low |
|
| 2019-04-16 15:42:30 |
Eric Desrochers |
sosreport (Ubuntu Ee-series): status |
New |
In Progress |
|
| 2019-04-16 15:42:46 |
Eric Desrochers |
bug |
|
|
added subscriber Bryan Quigley |
| 2019-04-16 15:43:00 |
Eric Desrochers |
nominated for series |
|
Ubuntu Xenial |
|
| 2019-04-16 15:43:00 |
Eric Desrochers |
bug task added |
|
sosreport (Ubuntu Xenial) |
|
| 2019-04-16 15:43:00 |
Eric Desrochers |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-04-16 15:43:00 |
Eric Desrochers |
bug task added |
|
sosreport (Ubuntu Bionic) |
|
| 2019-04-16 15:43:00 |
Eric Desrochers |
nominated for series |
|
Ubuntu Disco |
|
| 2019-04-16 15:43:00 |
Eric Desrochers |
bug task added |
|
sosreport (Ubuntu Disco) |
|
| 2019-04-16 15:43:00 |
Eric Desrochers |
nominated for series |
|
Ubuntu Trusty |
|
| 2019-04-16 15:43:00 |
Eric Desrochers |
bug task added |
|
sosreport (Ubuntu Trusty) |
|
| 2019-04-16 15:43:00 |
Eric Desrochers |
nominated for series |
|
Ubuntu Cosmic |
|
| 2019-04-16 15:43:00 |
Eric Desrochers |
bug task added |
|
sosreport (Ubuntu Cosmic) |
|
| 2019-04-16 16:10:28 |
Eric Desrochers |
tags |
|
sts |
|
| 2019-04-16 18:08:50 |
Eric Desrochers |
sosreport (Ubuntu Disco): assignee |
|
Eric Desrochers (slashd) |
|
| 2019-04-16 18:08:52 |
Eric Desrochers |
sosreport (Ubuntu Cosmic): assignee |
|
Eric Desrochers (slashd) |
|
| 2019-04-16 18:08:54 |
Eric Desrochers |
sosreport (Ubuntu Bionic): assignee |
|
Eric Desrochers (slashd) |
|
| 2019-04-16 18:08:56 |
Eric Desrochers |
sosreport (Ubuntu Xenial): assignee |
|
Eric Desrochers (slashd) |
|
| 2019-04-16 18:08:59 |
Eric Desrochers |
sosreport (Ubuntu Bionic): importance |
Undecided |
Low |
|
| 2019-04-16 18:09:01 |
Eric Desrochers |
sosreport (Ubuntu Cosmic): importance |
Undecided |
Low |
|
| 2019-04-16 18:09:03 |
Eric Desrochers |
sosreport (Ubuntu Disco): importance |
Undecided |
Low |
|
| 2019-04-16 18:09:55 |
Eric Desrochers |
summary |
v3.7 is now the latest release |
[sru] Backport of sosreport v3.7 |
|
| 2019-04-16 18:16:51 |
Eric Desrochers |
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
--- |
[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: #775195)
[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 (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]
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
--- |
|
| 2019-04-16 18:22:24 |
Eric Desrochers |
description |
[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: #775195)
[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 (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]
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
--- |
[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 (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]
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
--- |
|
| 2019-04-16 18:24:27 |
Eric Desrochers |
description |
[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 (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]
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
--- |
[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, ...)
* 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.
[Other information]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.7 |
|
| 2019-04-16 19:00:17 |
Eric Desrochers |
description |
[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, ...)
* 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.
[Other information]
* Release note:
https://github.com/sosreport/sos/releases/tag/3.7 |
[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]
* 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.7 |
|
| 2019-04-18 14:31:44 |
Eric Desrochers |
bug watch added |
|
https://github.com/sosreport/sos/issues/1653 |
|
| 2019-04-18 17:22:32 |
Eric Desrochers |
description |
[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]
* 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.7 |
[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]
* 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.7
* 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. |
|
| 2019-04-26 14:30:12 |
Eric Desrochers |
description |
[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]
* 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.7
* 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. |
[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
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.7
* 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. |
|
| 2019-04-26 20:05:55 |
Eric Desrochers |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928049 |
|
| 2019-04-26 20:06:12 |
Eric Desrochers |
bug task added |
|
sosreport (Debian) |
|
| 2019-04-26 20:08:31 |
Eric Desrochers |
sosreport (Ubuntu Trusty): status |
New |
Won't Fix |
|
| 2019-04-26 20:10:30 |
Eric Desrochers |
summary |
[sru] Backport of sosreport v3.7 |
[sru] new sosreport v3.7 |
|
| 2019-04-26 22:44:15 |
Bug Watch Updater |
sosreport (Debian): status |
Unknown |
New |
|
| 2019-05-13 23:18:33 |
Eric Desrochers |
bug |
|
|
added subscriber David Negreira |
| 2019-05-13 23:35:13 |
Eric Desrochers |
tags |
sts |
sosreport37 sts |
|
| 2019-08-27 18:12:24 |
Eric Desrochers |
summary |
[sru] new sosreport v3.7 |
[sru] Update sosreport to 3.7 || 3.8 |
|
| 2019-09-09 21:47:30 |
Eric Desrochers |
summary |
[sru] Update sosreport to 3.7 || 3.8 |
[sru] Update sosreport to 3.8 |
|
| 2019-09-09 23:48:40 |
Eric Desrochers |
bug task deleted |
sosreport (Debian) |
|
|
| 2019-09-09 23:48:51 |
Eric Desrochers |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939900 |
|
| 2019-09-09 23:48:51 |
Eric Desrochers |
bug task added |
|
sosreport (Debian) |
|
| 2019-09-09 23:54:11 |
Eric Desrochers |
description |
[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
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.7
* 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. |
[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-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
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. |
|
| 2019-09-10 04:20:43 |
Bug Watch Updater |
sosreport (Debian): status |
Unknown |
New |
|
| 2019-09-16 14:21:55 |
Bug Watch Updater |
sosreport (Debian): status |
New |
Fix Released |
|
| 2019-09-16 14:40:25 |
Eric Desrochers |
nominated for series |
|
Ubuntu Ff-series |
|
| 2019-09-16 14:40:25 |
Eric Desrochers |
bug task added |
|
sosreport (Ubuntu Ff-series) |
|
| 2019-09-16 14:40:32 |
Eric Desrochers |
sosreport (Ubuntu Ff-series): status |
New |
In Progress |
|
| 2019-09-16 14:40:35 |
Eric Desrochers |
sosreport (Ubuntu Ff-series): importance |
Undecided |
Medium |
|
| 2019-09-16 14:40:38 |
Eric Desrochers |
sosreport (Ubuntu Ff-series): assignee |
|
Eric Desrochers (slashd) |
|
| 2019-10-18 12:17:03 |
Eric Desrochers |
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-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
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. |
[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. |
|
| 2019-10-25 18:23:21 |
Eric Desrochers |
sosreport (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2019-10-25 18:50:26 |
Launchpad Janitor |
sosreport (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2019-11-12 11:24:13 |
Launchpad Janitor |
sosreport (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2019-11-12 11:24:13 |
Launchpad Janitor |
sosreport (Ubuntu Bionic): status |
New |
Confirmed |
|
| 2019-11-12 11:24:13 |
Launchpad Janitor |
sosreport (Ubuntu Cosmic): status |
New |
Confirmed |
|
| 2019-11-12 11:24:13 |
Launchpad Janitor |
sosreport (Ubuntu Disco): status |
New |
Confirmed |
|
| 2019-11-12 11:25:30 |
Andrea Ieri |
bug |
|
|
added subscriber Canonical IS BootStack |
| 2019-11-12 11:25:39 |
Andrea Ieri |
bug |
|
|
added subscriber The Canonical Sysadmins |
| 2019-11-12 13:40:20 |
Eric Desrochers |
sosreport (Ubuntu Cosmic): status |
Confirmed |
Won't Fix |
|
| 2019-12-11 21:47:32 |
Eric Desrochers |
sosreport (Ubuntu Disco): status |
Confirmed |
Won't Fix |
|
| 2019-12-11 21:47:52 |
Eric Desrochers |
sosreport (Ubuntu Xenial): status |
Confirmed |
Won't Fix |
|
| 2019-12-11 21:48:00 |
Eric Desrochers |
sosreport (Ubuntu Bionic): status |
Confirmed |
In Progress |
|
| 2019-12-11 21:50:56 |
Eric Desrochers |
sosreport (Ubuntu Xenial): status |
Won't Fix |
In Progress |
|
| 2019-12-11 21:51:01 |
Eric Desrochers |
sosreport (Ubuntu Xenial): importance |
Undecided |
Low |
|
| 2019-12-13 15:34:16 |
Eric Desrochers |
bug watch added |
|
https://github.com/sosreport/sos/issues/1892 |
|
| 2020-01-29 20:19:07 |
Eric Desrochers |
summary |
[sru] Update sosreport to 3.8 |
[sru] Update sosreport to 3.9 |
|
| 2020-02-11 19:36:20 |
Eric Desrochers |
summary |
[sru] Update sosreport to 3.9 |
[sru] Update sosreport to 3.8 |
|
| 2020-02-11 19:36:20 |
Eric Desrochers |
tags |
sosreport37 sts |
sts |
|
| 2020-02-11 19:36:58 |
Eric Desrochers |
sosreport (Ubuntu Xenial): status |
In Progress |
Won't Fix |
|
| 2020-02-11 19:37:08 |
Eric Desrochers |
sosreport (Ubuntu Bionic): status |
In Progress |
Won't Fix |
|
| 2020-02-11 19:37:18 |
Eric Desrochers |
sosreport (Ubuntu Eoan): status |
In Progress |
Won't Fix |
|
