sts-sponsors team mailing list archive
-
sts-sponsors team
-
Mailing list archive
-
Message #03025
[Bug 1941745] Re: [sru] sos upstream 4.2
** Changed in: sosreport (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of STS
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1941745
Title:
[sru] sos upstream 4.2
Status in sosreport package in Ubuntu:
Fix Released
Status in sosreport source package in Bionic:
Confirmed
Status in sosreport source package in Focal:
Fix Released
Status in sosreport source package in Hirsute:
Fix Released
Status in sosreport source package in Impish:
Fix Released
Status in sosreport source package in Jammy:
Fix Released
Status in sosreport package in Debian:
Fix Released
Bug description:
[IMPACT]
The sos team is pleased to announce the release of sos-4.2. This
release contains numerous improvements and bug fixes to several
components within sos, including an overhaul to the project's test
suite and infrastructure.
[TEST PLAN]
Documentation for Special Cases:
https://wiki.ubuntu.com/SosreportUpdates
[WHERE PROBLEM COULD OCCUR]
Regression could occur at core functionality, which may prevent sos
(or its subcommand to work. I consider this regression type as 'low'.
That is generally well tested, and we would find a problem at an early
stage during the verification phase if it is the case.
On the other end, regression could happen and are some kind of
expected at plugins levels. As of today, sos has more than 300
plugins. It is nearly impossible to test them all.
If a regression is found in a plugin, it is rarely affecting sos core
functionalities nor other plugins. So mainly the impact would be
limited to that plugin. The impact being that the plugin can't or
partially can collect the information that it is instructed to gather.
A 3rd party vendor would then ask user/customer to collect the
information manually for that particular plugins.
Plugins are segmented by services and/or applications (e.g.
openstack_keystone, bcache, system, logs, ...) in order to collect
things accordingly to the plugin detected or intentionally requested
for.
Sosreport plugins philosophy is to (as much as possible) maintain
backward compatibility when updating a plugin. The risk that an
ancient version of a software has been dropped, is unlikely, unless it
was intended to be that way for particular reasons. Certain plugin
also support the DEB installation way and the snap one (MAAS, LXD,
...) so all Ubuntu standard installation types are covered.
[OTHER INFORMATION]
Release note:
https://github.com/sosreport/sos/releases/tag/4.2
Debian RFS:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994564
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1941745/+subscriptions