Ubuntu
sosreport package

  1. Bug #1913581
  2. Comment #4

Comment 4 for bug 1913581

Revision history for this message
Eric Desrochers (slashd) wrote :

[VERIFICATION FOCAL]

In focal, systemd is shipped as follow:

ls -altr /usr/bin/systemd-resolve
lrwxrwxrwx 1 root root 10 Jan 6 20:47 /usr/bin/systemd-resolve -> resolvectl

With the proposed package of sosreport, the systemd plugin prefer 'resolvectl' over 'systemd-resolve' as it should.

# sos.log
2021-02-18 14:21:53,815 INFO: [plugin:systemd] added cmd output 'resolvectl status'
2021-02-18 14:21:53,815 INFO: [plugin:systemd] added cmd output 'resolvectl statistics'
2021-02-18 14:21:56,377 INFO: [plugin:systemd] collecting output of 'resolvectl status'
2021-02-18 14:21:56,391 INFO: [plugin:systemd] collecting output of 'resolvectl statistics'

ls -altr sos_commands/systemd/resolvectl_stat*
-rw-r--r-- 1 root root 1806 Feb 18 14:21 sos_commands/systemd/resolvectl_status
-rw-r--r-- 1 root root 391 Feb 18 14:21 sos_commands/systemd/resolvectl_statistics

Each command run well and collected the desired output.

If I intentionally remove of the equation and make 'resolvectl' no longer exist. The plugin is taking 'systemd-resolve' as fallback.

# sos.log
2021-02-18 14:25:30,816 INFO: [plugin:systemd] collecting output of 'systemd-resolve --status'
2021-02-18 14:25:30,830 INFO: [plugin:systemd] collecting output of 'systemd-resolve --statistics'