Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

When exporting on syncable format, the "listing" file is  supposed to have permissions 644. If the user running the export command has an umask too restrictive, the permissions of the listing file will follow.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Set umask to 0077
2. export a repository/cv/library on syncable format
3. check the permissions of the file

Actual results: file is created with permissions based on the umask


Expected results: file should have 644 regardless of umask for the user running the command


Additional info: Users that do the export and simply copy/rsync the exported content keeping permissions may have issues on the disconnected side while trying to enable repositories.

Connecting redmine issue https://projects.theforeman.org/issues/36689 from this bug

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36689 has been resolved.

Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.

Verified in 6.15.0 snap 7.0

Steps:
1) Sync some yum and file repos with immediate download policy.
2) Publish them in a CV.
3) Export the CV/repos/library in syncable format and check the permissions of the exported files.

All exported files had 0644 (-rw-r--r--) permissions. The only exception was metadata.json with 0600, which is expected.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.15.0 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2024:2010