QA (public) » openQA Project (public) » openQA Tests (public)

Motivation¶

We need to be able to test setroubleshoot automatically so we could catch downgrades or issues in advance to bring better usability to the users.

What should be tested:

• setroubleshootd
  • systemd service has no issue when called
  • daemon is dbus activated
  • policykit restrict direct usage only to setroubleshoot user

Acceptance Criteria¶

1. Create a test that runs on SELinux enabled Tumbleweed system, with auditd
2. Install the package setroubleshoot-server, check that it installs setroubleshoot-plugins automatically
3. Check setroubleshootd DBus activation via systemd service. Check if is-active shows inactive at first, then after restart shows active at first but after about 15 seconds it should be no longer active again.
4. Check setroubleshootd invoking via polkit as root, see /usr/share/dbus-1/system.d/org.fedoraproject.SetroubleshootFixit.conf

Further Information¶

Ask for details from for example Zdenek Kubala if something is unclear, or from this ticket's author.