toll13445
2010-Aug-28 09:46 UTC
[Puppet Users] getting "Failed to retrieve current state of resource: Mounts without paths are not usable Could not describe ..." only on debian
Hi, I have puppetmaster and some puppet clients, running CentOs 5.4 and debian lenny 5.0.3 The Centos ones are picking up files fine, but the debian ones, which are running; # dpkg -l puppet Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/ Trig-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name Version Description +++-=================================- =================================- =================================================================================ii puppet 0.24.5-3 centralised configuration management for networks are failing with the following message; # puppetd --test info: Caching catalog at /var/lib/puppet/state/localconfig.yaml notice: Starting catalog run err: //Node[default]/File[/etc/puppet/puppet.conf]: Failed to retrieve current state of resource: Mounts without paths are not usable Could not describe /modules/bpcommon/basenode/etc/puppet/puppet.conf: Mounts without paths are not usable at /etc/puppet/manifests/nodes.pp:33 notice: //puppet/Service[puppet]/ensure: ensure changed ''stopped'' to ''running'' err: //Node[default]/File[/etc/puppet/test.file]: Failed to retrieve current state of resource: Mounts without paths are not usable Could not describe /modules/bpcommon/basenode/etc/puppet/test.file: Mounts without paths are not usable at /etc/puppet/manifests/nodes.pp:10 notice: Finished catalog run in 0.53 seconds I have checked that both the paths exist, and it works for the RHEL/ CentOS boxes, so I am wondering if its something to do with the version of puppet installed ie 0.24.5-3 Any suggestions Thanks Tom -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Patrick
2010-Aug-28 15:41 UTC
Re: [Puppet Users] getting "Failed to retrieve current state of resource: Mounts without paths are not usable Could not describe ..." only on debian
On Aug 28, 2010, at 2:46 AM, toll13445 wrote:> Hi, > > I have puppetmaster and some puppet clients, running CentOs 5.4 and > debian lenny 5.0.3 > The Centos ones are picking up files fine, but the debian ones, which > are running; > # dpkg -l puppet > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/ > Trig-pend > |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: > uppercase=bad) > ||/ Name > Version Description > +++-=================================- > =================================- > =================================================================================> ii puppet > 0.24.5-3 centralised configuration management > for networks > > are failing with the following message; > # puppetd --test > info: Caching catalog at /var/lib/puppet/state/localconfig.yaml > notice: Starting catalog run > err: //Node[default]/File[/etc/puppet/puppet.conf]: Failed to retrieve > current state of resource: Mounts without paths are not usable Could > not describe /modules/bpcommon/basenode/etc/puppet/puppet.conf: Mounts > without paths are not usable at /etc/puppet/manifests/nodes.pp:33 > notice: //puppet/Service[puppet]/ensure: ensure changed ''stopped'' to > ''running'' > err: //Node[default]/File[/etc/puppet/test.file]: Failed to retrieve > current state of resource: Mounts without paths are not usable Could > not describe /modules/bpcommon/basenode/etc/puppet/test.file: Mounts > without paths are not usable at /etc/puppet/manifests/nodes.pp:10 > notice: Finished catalog run in 0.53 seconds > > > I have checked that both the paths exist, and it works for the RHEL/ > CentOS boxes, so I am wondering if its something to do with the > version of puppet installed ie 0.24.5-3That''s a very very old client. If at all possible you should upgrade to 0.25.x or at least 0.24.8. Try running puppet with --verbose and --debug. What''s piece from the manifest that its failing on? Is the server 2.6.x? II don''t think that backward compatibility is preserved between 2 major versions. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
James Cammarata
2010-Aug-28 22:02 UTC
Re: [Puppet Users] getting "Failed to retrieve current state of resource: Mounts without paths are not usable Could not describe ..." only on debian
On Sat, 28 Aug 2010 02:46:24 -0700 (PDT), toll13445 <thomas.hodder@gmail.com> wrote:> Hi, > > I have puppetmaster and some puppet clients, running CentOs 5.4 and > debian lenny 5.0.3 > The Centos ones are picking up files fine, but the debian ones, which > are running; > # dpkg -l puppet > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/ > Trig-pend > |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: > uppercase=bad) > ||/ Name > Version Description > +++-=================================- > =================================- >=================================================================================> ii puppet> 0.24.5-3 centralised configuration management > for networks > > are failing with the following message; > # puppetd --test > info: Caching catalog at /var/lib/puppet/state/localconfig.yaml > notice: Starting catalog run > err: //Node[default]/File[/etc/puppet/puppet.conf]: Failed to retrieve > current state of resource: Mounts without paths are not usable Could > not describe /modules/bpcommon/basenode/etc/puppet/puppet.conf: Mounts > without paths are not usable at /etc/puppet/manifests/nodes.pp:33 > notice: //puppet/Service[puppet]/ensure: ensure changed ''stopped'' to > ''running'' > err: //Node[default]/File[/etc/puppet/test.file]: Failed to retrieve > current state of resource: Mounts without paths are not usable Could > not describe /modules/bpcommon/basenode/etc/puppet/test.file: Mounts > without paths are not usable at /etc/puppet/manifests/nodes.pp:10 > notice: Finished catalog run in 0.53 seconds > > > I have checked that both the paths exist, and it works for the RHEL/ > CentOS boxes, so I am wondering if its something to do with the > version of puppet installed ie 0.24.5-3 > > Any suggestionsI have seen that error when the puppetmaster is upgraded but the puppet client is not. For instance, we went from 0.24.x to 0.25.4 and started receiving this error on clients that were still 0.24.x. They are not compatible, so as mentioned in another reply you need to upgrade. Keeping all servers/clients the same version is not a bad idea. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.