Issue #2803 has been updated by Lawrence Ludwig.

*fileserver.conf*
<pre>
[plugins]
allow 127.0.0.1/32
allow 192.168.10.0/24
allow 192.168.11.0/24
[modules]
allow 127.0.0.1/32
allow 192.168.10.0/24
allow 192.168.11.0/24
</pre>

*puppet.conf*
<pre>
[main]
vardir=/var/lib/puppet
logdir=/var/log/puppet
rundir=/var/run/puppet
ssldir=/var/lib/puppet/ssl

# plugin sync
pluginsync=true
factpath=/var/lib/puppet/lib/facter

# production
environment = production
modulepath = /home/puppet/production/modules
templatedir = /home/puppet/production/templates
manifestdir = /home/puppet/production/manifests
manifest = /home/puppet/production/manifests/site.pp

[development]
modulepath = 
/home/puppet/development/modules/site:/home/puppet/development/modules/dist
templatedir = /home/puppet/development/templates
manifestdir = /home/puppet/development/manifests
manifest = /home/puppet/development/manifests/site.pp

[testing]
modulepath = /home/puppet/testing/modules
templatedir = /home/puppet/testing/templates
manifestdir = /home/puppet/testing/manifests
manifest = /home/puppet/testing/manifests/site.pp

[puppetd]
classfile = /var/lib/puppet/classes.txt
localconfig = /var/lib/puppet/localconfig
report=true
listen=true
debug=true
verbose=true
catalog_format=marshal
bindaddress=<INTERNAL>
certname=<PUPPETMASTER>
server=<PUPPETMASTER>

[puppetmasterd]
ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY
environments=production
autosign=false
certname=<PUPPETMASTER>
reports=store
node_terminus=ldap
ldapserver=<LDAPSERVER>
ldapport=636
ldapssl=true
ldaptls=false
ldapbase = <LDAPBASE>
ldapuser = <LDAPUSER>
ldappassword=<LDAPPASSWORD>
</pre>

*line 73 of base.pp*
<pre>
    # track hosts
    file { "hosts":
        name     => "/etc/hosts",
        ensure   => present,
        replace  => true,
        owner    => 'root',
        group    => 'root',
        mode     => '0444',
        source   => [
            "puppet:///network-config/hosts/hosts.${hostname}",
            "puppet:///network-config/hosts/hosts.${fqdn}",
            "puppet:///network-config/hosts.${l}",
            "puppet:///network-config/hosts.conf"
        ],
    }
</pre>
----------------------------------------
Bug #2803: Issue with permissions with 0.25.1 -> 0.25.1 setup
http://projects.reductivelabs.com/issues/2803

Author: Lawrence Ludwig
Status: Unreviewed
Priority: Normal
Assigned to: 
Category: 
Target version: 
Affected version: 0.25.1
Keywords: 
Branch: 


I have a 0.25.1 puppetmaster that works fine with 0.24.8 nodes.  When I test 
with a 0.25.1 client, I get these errors with my existing puppet code.

Nov  4 14:43:35 devcentos5 puppetd[26099]: (//network-config::base/File
[hosts]) Failed to retrieve current state of resource: Error 400 on
SERVER: Not authorized to call find on /file_metadata/network-config/
hosts/hosts.devcentos5 Could not retrieve file metadata for
puppet:///network-config/hosts/hosts.devcentos5: Error 400 on SERVER:
Not authorized to call find on /file_metadata/network-config/hosts/
hosts.devcentos5 at /home/puppet/development/modules/dist/network-
config/manifests/base.pp:73
Nov  4 14:43:35 devcentos5 puppetd[26099]: (//network-config::base/File
[resolv.conf]) Failed to retrieve current state of resource: Error 400
on SERVER: Not authorized to call find on /file_metadata/network-
config/hosts/resolv.devcentos5.conf Could not retrieve file metadata
for puppet:///network-config/hosts/resolv.devcentos5.conf: Error 400
on SERVER: Not authorized to call find on /file_metadata/network-
config/hosts/resolv.devcentos5.conf at /home/puppet/development/
modules/dist/network-config/manifests/base.pp:44
Nov  4 14:43:35 devcentos5 puppetd[26099]: (//network-config::base/File
[host.conf]) Failed to retrieve current state of resource: Error 400
on SERVER: Not authorized to call find on /file_metadata/network-
config/hosts/host.devcentos5.conf Could not retrieve file metadata for
puppet:///network-config/hosts/host.devcentos5.conf: Error 400 on
SERVER: Not authorized to call find on /file_metadata/network-config/
hosts/host.devcentos5.conf at /home/puppet/development/modules/dist/
network-config/manifests/base.pp:58
Nov  4 14:43:35 devcentos5 puppetd[26099]: (//network-config::base/File
[nsswitch.conf]) Failed to retrieve current state of resource: Error
400 on SERVER: Not authorized to call find on /file_metadata/network-
config/hosts/nsswitch.devcentos5.conf Could not retrieve file metadata
for puppet:///network-config/hosts/nsswitch.devcentos5.conf: Error 400
on SERVER: Not authorized to call find on /file_metadata/network-
config/hosts/nsswitch.devcentos5.conf at /home/puppet/development/
modules/dist/network-config/manifests/base.pp:29

while the server gives off the error:
Not authorized to call find on /file_metadata/network-config/hosts/
hosts.devcentos5
Not authorized to call find on /file_metadata/network-config/hosts/
resolv.devcentos5.conf
Not authorized to call find on /file_metadata/network-config/hosts/
host.devcentos5.conf

I'm using passenger and do not have an auth.conf file.. 

More details can be found here:

http://groups.google.com/group/puppet-users/browse_thread/thread/977af0de79b99931

If it's not a bug then documentation is needed to explain how someone should 
allow 0.24.x and 0.25 nodes on the same puppetmaster.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to