Closed Satellite-QE closed 1 week ago
trigger: test-robottelo pytest: tests/foreman/installer/test_installer.py -k test_capsule_installation
PRT Result
Build Number: 9332
Build Status: UNSTABLE
PRT Comment: pytest tests/foreman/installer/test_installer.py -k test_capsule_installation --external-logging
Test Result : ========== 1 failed, 23 deselected, 48 warnings in 1702.49s (0:28:22) ==========
trigger: test-robottelo pytest: tests/foreman/installer/test_installer.py -k test_capsule_installation
PRT Result
Build Number: 9333
Build Status: UNSTABLE
PRT Comment: pytest tests/foreman/installer/test_installer.py -k test_capsule_installation --external-logging
Test Result : ========== 1 failed, 23 deselected, 48 warnings in 1718.02s (0:28:38) ==========
trigger: test-robottelo pytest: tests/foreman/installer/test_installer.py -k test_capsule_installation
PRT Result
Build Number: 9363
Build Status: SUCCESS
PRT Comment: pytest tests/foreman/installer/test_installer.py -k test_capsule_installation --external-logging
Test Result : ========== 1 passed, 23 deselected, 48 warnings in 8150.42s (2:15:50) ==========
Cherrypick of PR: https://github.com/SatelliteQE/robottelo/pull/16895
Problem Statement
There is a bug (https://issues.redhat.com/browse/SAT-29311) in fapolicyd, which freezes the machine and our tests didn't catch it. While this change will probably not surface that bug (we are still unsure how to reliably trigger it), it should at least assert fapolicyd is actually running (and didn't crash, which it sometimes does!) after policy loading.
Solution
assert systemd things fapolicyd is running
Related Issues
https://issues.redhat.com/browse/SAT-29311