[tests/selinux] pr775-checkpolicy-revdeps: Metadata update for systemd-sysctl-and-similar test and adding NoRHIVOS tag

[tests/selinux] pr775-checkpolicy-revdeps: Metadata update for systemd-sysctl-and-similar test and adding NoRHIVOS tag

[Jan Onderka]

A new commit has been pushed.

Repo   : tests/selinux
Branch : pr775-checkpolicy-revdeps
Commit : f5e7b111526eaa149f250d73a2d22c29fe64cd19
Author : Jan Onderka <jonderka@redhat.com>
Date   : 2025-03-12T17:02:44+01:00
Stats  : +30/-0 in 3 file(s)
URL    : https://src.fedoraproject.org/tests/selinux/c/f5e7b111526eaa149f250d73a2d22c29fe64cd19?branch=pr775-checkpolicy-revdeps

Log:
Metadata update for systemd-sysctl-and-similar test and adding NoRHIVOS tag

---
diff --git a/selinux-policy/chronyd-and-similar/main.fmf b/selinux-policy/chronyd-and-similar/main.fmf
index caf9836..6ada2ed 100644
--- a/selinux-policy/chronyd-and-similar/main.fmf
+++ b/selinux-policy/chronyd-and-similar/main.fmf
@@ -41,6 +41,7 @@ tag:
   - TipWaived6
   - f33friendly
   - targeted
+  - NoRHIVOS
 tier: '3'
 link:
   - relates: https://bugzilla.redhat.com/show_bug.cgi?id=974992

diff --git a/selinux-policy/policykit-general/main.fmf b/selinux-policy/policykit-general/main.fmf
index 655a4ab..4055ac8 100644
--- a/selinux-policy/policykit-general/main.fmf
+++ b/selinux-policy/policykit-general/main.fmf
@@ -38,6 +38,7 @@ tag:
   - f31friendly
   - f32friendly
   - targeted
+  - NoRHIVOS
 tier: '2'
 link:
   - relates: https://bugzilla.redhat.com/show_bug.cgi?id=960669

diff --git a/selinux-policy/systemd-sysctl-and-similar/PURPOSE b/selinux-policy/systemd-sysctl-and-similar/PURPOSE
index 6660acb..b98a257 100644
--- a/selinux-policy/systemd-sysctl-and-similar/PURPOSE
+++ b/selinux-policy/systemd-sysctl-and-similar/PURPOSE
@@ -3,3 +3,31 @@ Author: Milos Malik <mmalik@redhat.com>
 
 Does the systemd-sysctl work correctly under SELinux confinement?
 
+Inputs
+
+new system service file definition
+selinux labels for various files
+selinux rules present at the system
+
+Outputs
+
+Test passes or fail based on presence of specific selinux labels or rules
+or failures related to starting and stopping systemd-sysctl service
+
+Expected log output example
+
+::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
+::   real scenario
+::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
+
+:: [ 15:14:27 ] :: [   PASS   ] :: Command 'service systemd-sysctl start' (Expected 0, got 0)
+:: [ 15:14:46 ] :: [   PASS   ] :: Command 'service systemd-sysctl status' (Expected 0,1,3, got 0)
+:: [ 15:15:15 ] :: [   PASS   ] :: Command 'restorecon -Rv /etc /run /var -e /var/ARTIFACTS' (Expected 0-255, got 0)
+:: [ 15:15:19 ] :: [   PASS   ] :: Command 'service systemd-sysctl restart' (Expected 0, got 0)
+:: [ 15:15:38 ] :: [   PASS   ] :: Command 'service systemd-sysctl status' (Expected 0,1,3, got 0)
+:: [ 15:15:57 ] :: [   PASS   ] :: Command 'service systemd-sysctl stop' (Expected 0, got 0)
+:: [ 15:16:15 ] :: [   PASS   ] :: Command 'service systemd-sysctl status' (Expected 0,1,3, got 3)
+::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
+::   Duration: 127s
+::   Assertions: 7 good, 0 bad
+::   RESULT: PASS (real scenario)