Thanks for reporting the issue, and I can see this, as shown below
5350s /tmp/sosreport_test/var/log/boot.log:[[0;32m OK [0m] Started
[0;1;[email protected][0m - host0 root shell on ttyS1.
5350s /tmp/sosreport_test/var/log/boot.log:[[0;32m OK [0m] Started
[0;1;[email protected][0m - host0 root shell on ttyS1.
5350s /tmp/sosreport_test/var/log/boot.log:[[0;32m OK [0m] Started
[0;1;[email protected][0m - host0 root shell on ttyS1.
5350s /tmp/sosreport_test/var/log/boot.log:[[0;32m OK [0m] Started
[0;1;[email protected][0m - host0 root shell on ttyS1.
5350s /tmp/sosreport_test/var/log/boot.log:[[0;32m OK [0m] Started
[0;1;[email protected][0m - host0 root shell on ttyS1.
The problem here is that the hostname is actually autopkgtest, and is
falsely detecting that the hostname has not been obfuscated, and hence
you're getting this as a problem.
We will have a look at fixing this in the autopkgtest in the next
release
** Changed in: sos (Ubuntu)
Status: New => Confirmed
** Changed in: sos (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2109631
Title:
riscv64 autopkgtest failure due to incomplete hostname masking in
sosreport
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sos/+bug/2109631/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
