Add test for syncable export with restrictive permissions

[vsedmik]

Problem Statement

Coverage for BZ#2233162 is missing

Solution

This PR.
metadata.json is the only exception where restrictive permissions are expected

PRT test Cases example

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

[vsedmik]

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

[Satellite-QE]

PRT Result

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

[rmynar]

Can we be sure that all involved components (services) use the modified umask settings? May it be useful to launch satellite-maintain service restart when changing umask?

[vsedmik]

Can we be sure that all involved components (services) use the modified umask settings? May it be useful to launch satellite-maintain service restart when changing umask?

The issue was that the rights of the user executing the export command were used for the exported files. This way we set it globally for whatever user is used by target_sat.execute(), so IMHO no service restart is necessary.

[rmynar]

Can we be sure that all involved components (services) use the modified umask settings? May it be useful to launch satellite-maintain service restart when changing umask?

The issue was that the rights of the user executing the export command were used for the exported files. This way we set it globally for whatever user is used by target_sat.execute(), so IMHO no service restart is necessary.

Sounds good, ACK :)