[VERIFICATION BIONIC, FOCAL, GROOVY] The ubuntu plugin in sos 4.1 found in -proposed is working as expected in both scenarios 'ubuntu-advantage' (deprecated) and 'ua' (new binary).
sosreport is check for the presence of 'ua' first and will default to 'ubuntu-advantage' if 'ua' not found. # cat path_to_sosreport/sos_commands/ubuntu/ua_status SERVICE AVAILABLE DESCRIPTION cc-eal no Common Criteria EAL2 Provisioning Packages esm-apps yes UA Apps: Extended Security Maintenance esm-infra yes UA Infra: Extended Security Maintenance fips no NIST-certified FIPS modules fips-updates no Uncertified security updates to FIPS modules livepatch yes Canonical Livepatch service This machine is not attached to a UA subscription. See https://ubuntu.com/advantage ** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-groovy ** Tags added: verification-done-bionic verification-done-focal verification-done-groovy -- 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/1906302 Title: [plugin][apt] Move unattended-upgrades log collection Status in sosreport package in Ubuntu: Fix Released Status in sosreport source package in Xenial: Won't Fix Status in sosreport source package in Bionic: Fix Committed Status in sosreport source package in Focal: Fix Committed Status in sosreport source package in Groovy: Fix Committed Status in sosreport source package in Hirsute: Fix Released Bug description: [Impact] Having u-u logs collection inside the apt plugin make more sense (instead of logs plugin) as it is using apt functionalities and python modules such as apt, apt_inst, apt_pkg. u-u is a mechanism to automatically install security upgrades on Debian/Ubuntu. It is enabled by default at installation. 'sos' philosophy is that each plugin should be taken care of its own logs. [Test case] * Deploy Ubuntu (A container will do) * Run sosreport and make sure the systemd plugin is executed ** sosreport -o apt * Look the content of the generated tarball under 'path_to_sosreport/var/log/unattended-upgrades/' * And under 'path_to_sosreport/sos_logs/sos.log' for the execution log of the 'apt' plugin: sos.log:2021-02-06 11:23:55,257 INFO: [plugin:apt] collecting path '/var/log/unattended-upgrades/..... [Where problem could occur] If a problem have to occur, it will only be impacting the apt plugin itself, not the core functionalities of 'sos' nor its other plugins. A third party vendor might have to break the habit to assume that the 'logs' plugin will take care of the 'u-u' logs, and that 'apt' is the way to move forward now. [Other information] https://github.com/sosreport/sos/commit/9f057fb43a949cabb496d06506a59e411ef17812 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1906302/+subscriptions -- Mailing list: https://launchpad.net/~sts-sponsors Post to : [email protected] Unsubscribe : https://launchpad.net/~sts-sponsors More help : https://help.launchpad.net/ListHelp
