Verification for Resolute on Ubuntu 26.04 LTS (amd64), QEMU/KVM guest (q35), stock linux kernel 7.0.0-1017.
I tested sos 4.11.2-0ubuntu0.1 from resolute-proposed against 4.10.2-1 from release. sos report Both versions ran to completion with --batch --all-logs. Archives and checksums appeared under /var/tmp and the checksums matched the hashes sos printed. The warning output from grep -v "INFO:" sos_logs/sos.log is the same on both versions apart from the lxd change noted below. Every warning is a legitimate skip for a service or kernel module this VM does not have, covering fwupd, lxd, nf_tables and tls. Neither version produced a plugin error file. sos_logs holds only sos.log and ui.log. Zero-size files came to 400 on 4.10.2 and 404 on 4.11.2. I looked through them. They are empty AppArmor local overrides and write-only /proc triggers such as drop_caches and stat_refresh. Changes I could confirm --compression-type=none wrote an uncompressed .tar at 58.18MiB, against 4.73MiB for the same run as .tar.xz. The post-processing message now shows after plugins finish. The lxd plugin attempts 13 commands where 4.10.2 attempted 5, and it scopes them to local:. The new getent plugin loaded and ran without error. sos clean I ran it against the 4.11.2 archive. It produced all four expected artifacts and created /etc/sos/cleaner/default_mapping on first run. It reported removing 58 unprocessable files. Obfuscation works. The host MAC that appears in the collected netplan config is absent from the obfuscated archive, and default_mapping records the substitution. Landscape, and one thing worth flagging I registered landscape-client against a standalone server and ran sos report -o landscape. It collected client.conf, the landscape logs and the client state files without error. A registration_key value in /etc/landscape/client.conf is collected in clear text. I confirmed this on both 4.10.2 and 4.11.2, so it is not a regression from this update and does not block it. The cause looks like a rename. The plugin's postproc substitutes registration_password in client config, and its key list covering password, store_password, secret-token and the oidc entries applies to /etc/landscape/service.conf rather than client.conf. Current clients write registration_key, which nothing matches. I tested with a fake key and it survived into the archive intact. I will report this upstream separately. What I did not cover Physical hardware and containers, since this was a VM only. amd64 only. sos collect and sos upload. The netplan secret redaction change, because this VM has a DHCP ethernet config with no secret-bearing keys in it. No Cloud, Ceph, MAAS, sunbeam or juju environment was available. Leaving the tag as verification-needed-resolute, since the test plan calls for testing across physical hardware, containers and managed environments that I could not provide. Happy for someone with broader coverage to flip it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2156921 Title: [sru] sos upstream 4.11.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sos/+bug/2156921/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
