Fix umask setting fixture

[vsedmik]

Problem Statement

Default umask settings defined in /etc/bashrc (used for non-login shell, which is what robottelo use for target_sat.execute(...)) is different in RHEL8 and RHEL9.

In RHEL8 we can find:

    if [ $UID -gt 199 ] && [ "`/usr/bin/id -gn`" = "`/usr/bin/id -un`" ]; then
       umask 002
    else
       umask 022
    fi

while in RHEL9:

    # Set default umask for non-login shell only if it is set to 0
    [ `umask` -eq 0 ] && umask 022

That [ ] test is important there, since it prevents umask setting if it's non-zero already (yes it is) and thus blocks the fixture to set it more restrictively with sed (as used before) when running against RHEL9 based Satellite.

Solution

Override it no matter what previous code is and return it back on tear-down.

PRT test Cases example

trigger: test-robottelo
pytest: tests/foreman/cli/test_satellitesync.py -k with_permissions

[vsedmik]

trigger: test-robottelo
pytest: tests/foreman/cli/test_satellitesync.py -k with_permissions

[Satellite-QE]

PRT Result

Build Number: 7471
Build Status: SUCCESS
PRT Comment: pytest tests/foreman/cli/test_satellitesync.py -k with_permissions --external-logging
Test Result : ========== 1 passed, 33 deselected, 42 warnings in 787.93s (0:13:07) ===========

[damoore044]

nice fix!