Various "unowned" rules have broken `.fail.sh` unit tests

[comps]

Description of problem:

Something recently (1 day ago) broke these unit tests:

file_permissions_ungroupowned/unowned_file_tmp.fail
file_permissions_unauthorized_world_writable/world_writable_tmp.fail
no_files_unowned_by_user/unowned_file_tmp.fail

which are now unable to set up the test scenarios in a way to FAIL the subsequent scan, since the scan PASSes even without any remediation.

SCAP Security Guide Version:

master @ 3a149cf

The issue probably happened between 0efc6e4 (1 day ago) and the commit above, see https://github.com/ComplianceAsCode/content/compare/0efc6e4f5a1d8156f06c5ec451c58a9ea6924c56..3a149cff834f81738ca6b3efe75f5fb20409d761 .

That seems to suggest #13758 to be the culprit.

Operating System Version:

RHEL 10, 9, 8

Steps to Reproduce:

1. Run /per-rule/oscap/from-env from Contest, give it RULE="file_permissions_ungroupowned no_files_unowned_by_user file_permissions_unauthorized_world_writable"

Actual Results:

The tests set up the scan to fail

Expected Results:

The tests set up the scan to pass

Additional Information/Debugging Steps:

[jan-cerny]

Information:

This isn't reproducible with Automatus. But, it's reproducible with contest.

The issue is only with test scenarios that work with /tmp. There are other test scenarios which are very similar and don't work with /tmp and these test scenarios pass.

I guess there can be some difference about /tmp between automatus VM backends and contest VMs.