Project

General

Profile

Bug #15795

Import of puppet module fails when using restrictive umask on the satellite server

Added by Andrew Kofink almost 6 years ago. Updated almost 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Content Uploads
Target version:
Difficulty:
medium
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1197802
Description of problem: Import of puppet modules fails when using an restrictive umask (0077) on the satellite 6 server.

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

How reproducible:
Always

Steps to Reproduce:
1. set umask to 0077
2. katello-service restart
3. create CV and add puppet modules to it
4. promote the CV
5. no new modules appears under Configure => Puppet Classes in the web UI
6. Listing /etc/puppet/environments/KT_CV_name_environment_X/modules
will show that the permission on the module dir's is set to apache:apache and 700

Actual results:

Expected results:
Permission on module dir's should be set to apache:foreman-proxy and 750 even though an restrictive umask is used.

Additional info:

History

#1 Updated by Brad Buckingham almost 6 years ago

  • Category changed from Web UI to Content Uploads

#2 Updated by Justin Sherrill almost 6 years ago

  • Status changed from New to Rejected
  • Legacy Backlogs Release (now unused) set to 166
  • Difficulty set to medium

This is either fixed or a pulp issue.

Also available in: Atom PDF