Project

General

Profile

Bug #2289

smart-proxy should warn when it cannot read some puppet module file or directory

Added by Frederic Schaer over 8 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Puppet
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Hi,

I have my own git/puppet/foreman workflow, and I did chown git:git my environement modules and classes.
When testing the latest smart-proxy reinstalled from scratch , I did a mistake : I added the forman user to the git group, instead of the foreman-proxy user.

As a consequence, both the foreman web import or the rake tasks were telling me that nothing changed in my environments, and the envs and classes remained desperately empty.

Therefore, I would kindly ask if it would be possible to raise a warning in the smart proxy logs, when one of the (puppet) subdirectories it is setup to watch is not readable, or when a file is not readable inside a subdirectory for which it had been granted access ?

thanks && Regards


Related issues

Related to Foreman - Bug #3900: Class removed because invalid syntax validationNew2013-12-17
Related to Smart Proxy - Feature #15095: Add Puppet server environment_classes API supportClosed

History

#1 Updated by Dominic Cleal over 5 years ago

  • Related to Bug #3900: Class removed because invalid syntax validation added

#2 Updated by Dmitri Dolguikh about 5 years ago

  • Related to Feature #15095: Add Puppet server environment_classes API support added

#3 Updated by Dominic Cleal about 5 years ago

  • Description updated (diff)
  • Status changed from New to Resolved

I believe this has been resolved in the smart proxy under #15095, in that the proxy's new classes_and_errors API lists permission errors provided by Puppet Server:

  {
    "error": "Permission denied - /etc/puppetlabs/code/environments/production/modules/test/manifests/init.pp",
    "path": "/etc/puppetlabs/code/environments/production/modules/test/manifests/init.pp" 
  },

Though this isn't used yet in Foreman, once implemented in #3900 the error information should then be visible during import.

Thanks for the report!

Also available in: Atom PDF