Comment 5 for bug 1913581

[VERIFICATION GROOVY]

In groovy, systemd is shipped as follows:

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

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

Each command run well and collected the desired output.

# sos.log
2021-02-18 14:31:58,715 INFO: [plugin:systemd] added cmd output 'resolvectl status'
2021-02-18 14:31:58,716 INFO: [plugin:systemd] added cmd output 'resolvectl statistics'
2021-02-18 14:32:00,962 INFO: [plugin:systemd] collecting output of 'resolvectl status'
2021-02-18 14:32:00,976 INFO: [plugin:systemd] collecting output of 'resolvectl statistics'

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

2021-02-18 14:33:43,819 INFO: [plugin:systemd] collecting output of 'systemd-resolve --status'
2021-02-18 14:33:43,832 INFO: [plugin:systemd] collecting output of 'systemd-resolve --statistics'