For full changelog reference:
This bug was fixed in the package sosreport - 4.3-1ubuntu2
---------------
sosreport (4.3-1ubuntu2) jammy; urgency=medium
* d/p/0003-mention-sos-help-in-sos-manpage.patch:
Fix sos-help manpage.
-- Eric Desrochers <[email protected]> Wed, 16 Feb 2022 13:05:13 -0500
---------------
sosreport (4.3-1ubuntu1) jammy; urgency=medium
* New 4.3 upstream. (LP: #1960996)
* For more details, full release note is available here:
- https://github.com/sosreport/sos/releases/tag/4.3
* New patches:
- d/p/0002-fix-setup-py.patch:
Add python sos.help module, it was miss in
upstream release.
* Former patches, now fixed:
- d/p/0002-report-implement_estimate-only.patch
- d/p/0003-ceph-add-support-for-containerized-ceph-setup.patch
- d/p/0004-ceph-split-plugin-by-components.patch
- d/p/0005-openvswitch-get-userspace-datapath-implementations.patch
- d/p/0006-report-check-for-symlink-before-rmtree.patch
* Remaining patches:
- d/p/0001-debian-change-tmp-dir-location.patch:
-- Eric Desrochers <[email protected]> Tue, 15 Feb 2022 23:10:27 -0500
** Description changed:
[IMPACT]
The sos team is pleased to announce the release of sos-4.3. This release
includes a number of quality-of-life changes to both end user experience
and for contributors dealing with the plugin API.
[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.
* Problem found and fixed during the packaging process:
- ** sos-help module wasn't part of the build process
- ** sos-help man page wasn't also not part of the build process nor mention
in main sos man page
+ ** sos-help module wasn't part of the build process
+ ** sos-help man page wasn't also not part of the build process nor mention
in main sos man page
Bug:
https://github.com/sosreport/sos/issues/2860
- PR:
+ Both commits of PR need to be part of 4.3 Ubuntu package:
https://github.com/sosreport/sos/pull/2861
[OTHER INFORMATION]
Release note:
https://github.com/sosreport/sos/releases/tag/4.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960996
Title:
[sru] sos upstream 4.3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1960996/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
