Bug 1297741

Summary: [RFE] Satellite 6 to validate permissions on puppet modules when ingesting into a repository.
Product: Red Hat Satellite Reporter: Matthew York <myork>
Component: Content ManagementAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: low    
Version: UnspecifiedCC: bbuckingham
Target Milestone: UnspecifiedKeywords: RFE
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-04 15:01:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Matthew York 2016-01-12 11:04:23 UTC 
Description of problem:
Hi, I wonder if we can look at a possible RFE to improve the way satellite repositories validate puppet modules that are uploaded and or synchronised from a 3rd party puppet repository.

Some modules when provided externally, have been packaged with incorrect permissions (700). This means that some puppet runs will fail, as content cannot be accessed.

These permissions persist and we end up in a situation where particular modules in 
/etc/puppet/environments/*/modules/ have the wrong permissions.

It would be really helpful, so when we either sync a puppet repo, or upload a puppet module manually, that each module is sanity checked for a few basic tasks such as...

1) File permissions
2) puppet parser validate

I believe by spotting these issues as we ingest, will avoid any workarounds such as  systemd file permission monitoring scripts later on. 

Many thanks

Matt