Bug 2253289

Summary:	Installer doesn't set correct permissions of /pub/ files
Product:	Red Hat Satellite	Reporter:	David C. Bradley <david.c.bradley>
Component:	Installation	Assignee:	Eric Helms <ehelms>
Status:	CLOSED MIGRATED	QA Contact:	Lukas Pramuk <lpramuk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.13.6	CC:	ahumbe, ehelms, lpramuk, rlavi, zhunting
Target Milestone:	stream	Keywords:	MigratedToJIRA, Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 16:37:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David C. Bradley 2023-12-06 16:49:26 UTC

When running the installer on a fresh system, some of the contents of the /pub directory are not accessible. Trying to download the consumer RPM from "https://satellite.example.com/pub/katello-ca-consumer-latest.noarch.rpm" results in a "403 Forbidden" error. From looking at the file on the system, it seems like the installer is not setting to correct permissions on the files it generated. There isn't read access for the "apache" user:

# ll -a /var/www/html/pub
total 120
drwxr-xr-x. 2 apache apache  4096 Dec  6 01:37 .
drwxr-xr-x. 3 root   root      82 Dec  5 01:28 ..
-rw-r--r--. 1 root   root   74211 Apr 26  2022 bootstrap.py
-rw-------. 1 root   root   12056 Nov 30 17:40 katello-ca-consumer-satellite.example.com-1.0-1.noarch.rpm
-rw-------. 1 root   root   11312 Nov 30 17:40 katello-ca-consumer-satellite.example.com-1.0-1.src.rpm
lrwxrwxrwx. 1 root   root      94 Nov 30 17:40 katello-ca-consumer-latest.noarch.rpm -> /var/www/html/pub/katello-ca-consumer-satellite.example.com-1.0-1.noarch.rpm
-rwx------. 1 root   root    8240 Nov 30 17:40 katello-rhsm-consumer
-rw-r--r--. 1 root   root    2706 Nov 30 17:40 katello-server-ca.crt

It seems to be using the default umask for the system:

# umask
0077

This can be fixed by adding global read access to the files, but it seems like the installer should be doing this.

Reproducible: Always

Steps to Reproduce:
1. Start with a fresh system
2. Have the umask set to 0077
3. Run `satellite-installer --scenario satellite`
4. Try to access "https://satellite.example.com/pub/katello-ca-consumer-latest.noarch.rpm"
Actual Results:  
"403 Forbidden" error

Expected Results:  
RPM file is downloaded

# cat /etc/os-release
NAME="Red Hat Enterprise Linux"
VERSION="8.9 (Ootpa)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="8.9"
PLATFORM_ID="platform:el8"

Comment 5 Lukas Pramuk 2024-03-01 15:08:29 UTC

FailedQA.

@Satellite Stream Snap49
foreman-installer-3.10.0-0.4.develop.20240216114125git4d26118.el8sat.noarch

by using the following manual reproducer:

1) Set umask 0077 permanently (logout and login afterwards)
# echo 'umask 0077' > /etc/profile.d/umask.sh

2) Install Satellite rpms and run the installer

3) Check file perms of rpms stored in /pub
# ll -a /var/www/html/pub
total 116
drwxr-xr-x. 2 apache apache  4096 Mar  1 09:13 .
drwxr-xr-x. 3 root   root      17 Aug 17  2023 ..
-rw-r--r--. 1 root   root   74211 Apr 26  2022 bootstrap.py
-rw-r--r--. 1 root   root       0 Mar  1 09:13 katello-ca-consumer-sat.example.com
-rw-------. 1 root   root   10356 Mar  1 09:13 katello-ca-consumer-sat.example.com-1.0-1.noarch.rpm
-rw-------. 1 root   root    9615 Mar  1 09:13 katello-ca-consumer-sat.example.com-1.0-1.src.rpm
lrwxrwxrwx. 1 root   root     103 Mar  1 09:13 katello-ca-consumer-latest.noarch.rpm -> /var/www/html/pub/katello-ca-consumer-sat.example.com-1.0-1.noarch.rpm
-rw-r--r--. 1 root   root    8121 Mar  1 09:13 katello-rhsm-consumer
-rw-r--r--. 1 root   root    2594 Mar  1 09:13 katello-server-ca.crt

>>> rpms in /pub are not group/world readable

Comment 6 Eric Helms 2024-06-06 16:37:49 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.