Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-4440

puppet changes executable facts.d files to non-executable before running

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: PUP 4.0.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:
    • Template:

      Description

      I have a new RHEL6 machine with puppet-agent & puppetserver installed. I've checked out our existing 3.7 codebase and am trying to run it. Our custom facts are deployed but then marked non-executable, so they don't run properly:

      # /opt/puppetlabs/bin/puppet agent -to --server `hostname`
      Info: Retrieving pluginfacts
      Notice: /File[/opt/puppetlabs/puppet/cache/facts.d/dec_dc.sh]/mode: mode changed '0755' to '0644'
      Notice: /File[/opt/puppetlabs/puppet/cache/facts.d/dec_env.sh]/mode: mode changed '0755' to '0644'
      Info: Retrieving plugin
      Info: Loading facts
      Warning: Facter: Fact file /opt/puppetlabs/puppet/cache/facts.d/dec_dc.sh was parsed but returned an empty data set
      Warning: Facter: Fact file /opt/puppetlabs/puppet/cache/facts.d/dec_env.sh was parsed but returned an empty data set
      Info: Caching catalog for server.fqdn.com
      Info: Applying configuration version '1429520640'
      Notice: Applied catalog in 0.07 seconds

      I've not changed any settings from their default, except:

      # puppet config print environmentpath
      /var/puppet/environments

      There's no difference in behaviour with cfactor enabled or disabled.

      These facts are marked +x in the git repo, and are +x in the environmentpath Puppet is reading them from.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              alex.jurkiewicz Alex Jurkiewicz
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support