Jira (PUP-5233) puppet inspect is using wrong path for catalog data

[Jo Rhett (JIRA)]

Title: Message Title

Jo Rhett created an issue   Puppet / PUP-5233 puppet inspect is using wrong path for catalog data Issue Type: Bug Affects Versions: PUP 4.2.1 Assignee: Unassigned Created: 2015/09/14 12:35 AM Priority: Major Reporter: Jo Rhett Deploying Puppet 4 at a client which makes heavy use of puppet inspect and found that Puppet 4 uses the wrong path to find the client catalog. [vagrant@client ~]$ sudo puppet agent --test Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Info: Caching catalog for client.example.com Info: Applying configuration version '1442215415' Notice: /Stage[main]/Main/File[/etc/hosts]/content: audit change: previously recorded value {md5}e2b06541983600068fff455f8c11861a has been changed to {md5}28c9f9f5a3d060a500d4b57f9875ba32 Notice: Applied catalog in 0.39 seconds   [vagrant@client ~]$ sudo puppet inspect Error: Could not run: Could not find catalog for client.example.com Strace shows us that it's looking in the client_yaml directory instead of client_data. [pid 7817] lstat("/opt/puppetlabs", {st_mode=S_IFDIR|0755, st_size=42, ...}) = 0 [pid 7817] lstat("/opt/puppetlabs/puppet", {st_mode=S_IFDIR|0755, st_size=102, ...}) = 0 [pid 7817] lstat("/opt/puppetlabs/puppet/lib", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 [pid 7817] lstat("/opt/puppetlabs/puppet/lib/ruby", {st_mode=S_IFDIR|0755, st_size=47, ...}) = 0 [pid 7817] lstat("/opt/puppetlabs/puppet/lib/ruby/vendor_ruby", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 [pid 7817] lstat("/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 [pid 7817] lstat("/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 [pid 7817] lstat("/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/yaml.rb", {st_mode=S_IFREG|0644, st_size=1940, ...}) = 0 [pid 7817] stat("/etc/puppetlabs/puppet/routes.yaml", 0x7fff96c96bd0) = -1 ENOENT (No such file or directory) [pid 7817] stat("/opt/puppetlabs/puppet/cache/client_yaml/catalog/client.example.com.yaml", 0x7fff96c96bd0) = -1 ENOENT (No such file or directory) [pid 7817] write(2, "\33[1;31mError: Could not run: Cou"..., 78Error: Could not run: Could not find catalog for client.example.com) = 78 The catalog is actually stored in /opt/puppetlabs/puppet/cache/client_data/catalog/. Workaround implemented for the client: file { '/opt/puppetlabs/puppet/cache/client_yaml/catalog': ensure => link, target => '/opt/puppetlabs/puppet/cache/client_data/catalog', } Add Comment   This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.