[sru] sos upstream 4.2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sosreport (Debian) |
Fix Released
|
Unknown
|
|||
sosreport (Ubuntu) |
Fix Released
|
Medium
|
Eric Desrochers | ||
Bionic |
Won't Fix
|
Low
|
Unassigned | ||
Focal |
Fix Released
|
Medium
|
Eric Desrochers | ||
Hirsute |
Fix Released
|
Medium
|
Eric Desrochers | ||
Impish |
Fix Released
|
Medium
|
Eric Desrochers | ||
Jammy |
Fix Released
|
Medium
|
Eric Desrochers |
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:/
[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:/
Debian RFS:
https:/
description: | updated |
Changed in sosreport (Debian): | |
status: | Unknown → New |
description: | updated |
description: | updated |
Changed in sosreport (Ubuntu Jammy): | |
status: | New → In Progress |
assignee: | nobody → Eric Desrochers (slashd) |
importance: | Undecided → Medium |
summary: |
- [FFe][sync][sru] sos upstream 4.2 + [sru] sos upstream 4.2 |
Changed in sosreport (Ubuntu Impish): | |
status: | New → In Progress |
assignee: | nobody → Eric Desrochers (slashd) |
importance: | Undecided → Medium |
Changed in sosreport (Ubuntu Hirsute): | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Eric Desrochers (slashd) |
description: | updated |
Changed in sosreport (Ubuntu Focal): | |
status: | New → Confirmed |
Changed in sosreport (Ubuntu Bionic): | |
status: | New → Incomplete |
status: | Incomplete → Confirmed |
tags: | added: upgrade-software-version |
Changed in sosreport (Ubuntu Bionic): | |
importance: | Undecided → Low |
Changed in sosreport (Ubuntu Focal): | |
importance: | Undecided → Low |
Changed in sosreport (Ubuntu Focal): | |
status: | Confirmed → Triaged |
status: | Triaged → In Progress |
assignee: | nobody → Eric Desrochers (slashd) |
importance: | Low → Medium |
description: | updated |
Changed in sosreport (Debian): | |
status: | New → Fix Released |
# Note
Currently facing a problem with dh_auto_test: while running test w/ avocado-framework.
Avocado is not packaged in Ubuntu/Debian, and requires to be installed via 'pip3 install avocado-framework' which doesn't seem to be accepted by the builder.
Tried severals scenarios such as:
# d/rules: dh_auto_ test: cleaner, collect, report, vendor} _tests
override_
pip3 install avocado-framework
export PYTHONPATH=tests/
avocado run -t stageone tests/{
but got the following error at build time from my PPA:
debian/rules override_ dh_auto_ test nonexistent/ .cache/ pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag. rror('< urllib3. connection. HTTPSConnection object at 0x7f5a4cd153d0>: Failed to establish a new connection: [Errno -2] Name or service not known')': /simple/ avocado- framework/ rror('< urllib3. connection. HTTPSConnection object at 0x7f5a4cc68cd0>: Failed to establish a new connection: [Errno -2] Name or service not known')': /simple/ avocado- framework/ rror('< urllib3. connection. HTTPSConnection object at 0x7f5a4cc680a0>: Failed to establish a new connection: [Errno -2] Name or service not known')': /simple/ avocado- framework/ rror('< urllib3. connection. HTTPSConnection object at 0x7f5a4cc685b0>: Failed to establish a new connection: [Errno -2] Name or service not known')': /simple/ avocado- framework/ rror('< urllib3. connection. HTTPSConnection object at 0x7f5a4cc68760>: Failed to establish a new connection: [Errno -2] Name or service not known')': /simple/ avocado- framework/
make[1]: Entering directory '/<<PKGBUILDDIR>>'
pip3 install avocado-framework
WARNING: The directory '/sbuild-
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionE
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionE
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionE
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionE
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionE
ERROR: Could not find a version that satisfies the requirement avocado-framework
ERROR: No matching distribution found for avocado-framework
Still under investigation.
I might have no other option but to package avocado-framework and add it as a Build-Depends, as I'm not a fan of disabling dh_auto_test: .
- Eric