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

[Jo Rhett (JIRA)]

Title: Message Title

Jo Rhett commented on PUP-5233   Re: puppet inspect is using wrong path for catalog data Do you mean the following patch? diff --git a/./puppet/lib/ruby/vendor_ruby/puppet/application/inspect.rb_orig b/./puppet/lib/ruby/vendor_ruby/puppet/application/inspect.rb index 3aec9fa..b630efa 100644 --- a/./puppet/lib/ruby/vendor_ruby/puppet/application/inspect.rb_orig +++ b/./puppet/lib/ruby/vendor_ruby/puppet/application/inspect.rb @@ -91,7 +91,7 @@ Copyright (c) 2011 Puppet Labs, LLC Licensed under the Apache 2.0 License set_log_level Puppet::Transaction::Report.indirection.terminus_class = :rest - Puppet::Resource::Catalog.indirection.terminus_class = :yaml + Puppet::Resource::Catalog.indirection.terminus_class = Puppet[:catalog_cache_terminus] || :json end def preinit Puppet inspect runs successfully, and it does properly determine which resources in the catalog have the audit attribute set, but it does not pick up on changes to the resources locally. # puppet inspect …snip… out_of_sync: false changed: false resource_type: File title: /tmp/testfile.txt skipped: false failed: false containment_path: - Stage[main] - Main - File[/tmp/testfile.txt] host: client.example.com   # puppet inspect --verbose Notice: Finished inspection in 3.99 seconds [root@client puppetlabs]# puppet agent --test Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Info: Caching catalog for client.example.com Info: Applying configuration version '1456228739' Notice: /Stage[main]/Main/File[/tmp/testfile.txt]/content: --- /tmp/testfile.txt 2016-02-23 11:55:43.037373981 +0000 +++ /tmp/puppet-file20160223-25544-zao9ck 2016-02-23 11:59:00.141887058 +0000 @@ -1,1 +1 @@ -I hacked this change in +jackrabbit! \ No newline at end of file Info: Computing checksum on file /tmp/testfile.txt Info: FileBucket got a duplicate file {md5}a84bd775b3d654ff165d86e9b733ef6e Info: /Stage[main]/Main/File[/tmp/testfile.txt]: Filebucketed /tmp/testfile.txt to puppet with sum a84bd775b3d654ff165d86e9b733ef6e Notice: /Stage[main]/Main/File[/tmp/testfile.txt]/content: content changed '{md5}a84bd775b3d654ff165d86e9b733ef6e' to '{md5}000a70d0ebea2001153c885c63cd2c23' Notice: /Stage[main]/Main/File[/tmp/testfile.txt]/owner: audit change: previously recorded value vagrant has been changed to root Notice: /Stage[main]/Main/File[/tmp/testfile.txt]/ctime: audit change: previously recorded value 2016-02-23 11:46:16 +0000 has been changed to 2016-02-23 11:55:43 +0000 Notice: /Stage[main]/Main/File[/tmp/testfile.txt]/mtime: audit change: previously recorded value 2016-02-23 11:46:09 +0000 has been changed to 2016-02-23 11:55:43 +0000 Notice: Applied catalog in 0.38 seconds So audit continues to work, but puppet inspect is blithely unaware of changes. Add Comment   This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.