Hi Andreas,

I don't think the mask autopkgtest failure is a blocker. It only is seen on ppc64le and when I tried on that architecture I could not reproduce it (earlier comment)

I've restarted that test on focal in case its an infra issue. 

As for the failure due to the loading of the tls module, that is a real issue. It appears sos has been causing loading of the "tls" module for a long time now, in fact all the way back to the 4.2-1ubuntu2 version jammy onwards and it started when we moved to python 3.10. For eg - https://autopkgtest.ubuntu.com/packages/sosreport/jammy/amd64 shows the first failure on 2022-01-14,  

4.2-1ubuntu2	python3-defaults/3.10.1-0ubuntu1	2022-01-14 15:03:07 UTC	0h 06m 52s	-	fail	log   artifacts   ♻
4.2-1ubuntu2	python3-defaults/3.9.7-4	2021-11-07 06:17:56 UTC	0h 03m 04s	-	pass	log   artifacts  

We've finally realized this after you flagged it, so thank you! It seems we never got these autopkgtest failures reported on the SRU bugs for each sos release due to the fact that they were no longer regressions since they were happening since some time.  However I am not sure why we never got autopkgtest results (even if it was a "no regressions" report for any release other than focal on the sru bugs for sos releases.)

I will open an upstream issue for this, and we've also tracked it down to the ubuntu plugin.

# lsmod | grep tls
# sos report -o ubuntu

sosreport (version 4.5.3)

This command will collect system configuration and diagnostic
information from this Ubuntu system.

For more information on Canonical visit:

        Community Website  : https://www.ubuntu.com/
        Commercial Support : https://www.canonical.com

The generated archive may contain data considered sensitive and its
content should be reviewed by the originating organization before being
passed to any third party.

No changes will be made to system configuration.


Press ENTER to continue, or CTRL-C to quit.

Optionally, please enter the case id that you are generating this report for []: 

 Setting up archive ...
 Setting up plugins ...
 Running plugins. Please wait ...

  Starting 1/1   ubuntu          [Running: ubuntu]                                        

  Finished running plugins                                                               
Creating compressed archive...

Your sosreport has been generated and saved in:
    /tmp/sosreport-nikhil-XXXX-dolysxz.tar.xz

 Size    9.52KiB
 Owner    root
 sha256    0e693d420391ef1c20503a90b706f440bfb5882bcabda3981a8a93cf26296718

Please send this file to your support representative.

# 
# lsmod | grep tls
tls                   147456  0

The command the triggers it is the "ua status" command,

# lsmod | grep tls
# ua status

No Ubuntu Pro services are available to this system.

For a list of all Ubuntu Pro services, run 'pro status --all'

This machine is not attached to an Ubuntu Pro subscription.
See https://ubuntu.com/pro

Supported livepatch kernels are listed here: https://ubuntu.com/security/livepatch/docs/kernels
# lsmod | grep tls
tls                   147456  0

Given that this is such an old issue, we still think the release should go ahead, but with this documented somewhere, so we will discuss this in detail and update the bug with more information.
Alternately, we can SRU a fix (in the worst case just remove that collection for now..) but that would further delay our sos 4.5.6 release, and we have already had the last 2 releases scrapped due to upstream bugs found in our testing.
 
Please let me know what you think.

-Nikhil.