Jira (PUP-3266) Puppet does not recompile catalog after failure
Title: Message Title Felix Frank commented on an issue Re: Puppet does not recompile catalog after failure Thomas Rasmussen this can also occur if you still rely on import statements. Do you? Add Comment Puppet / PUP-3266 Puppet does not recompile catalog after failure I have a setup which works, puppet master compiles catalog and client applies this. Then I make a typo in an included class for my node. Rerun puppet agent on client, it will (sometimes) create an error like this: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class Some.class.name for node.name If I t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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.
Jira (PUP-3266) Puppet does not recompile catalog after failure
Title: Message Title Thomas Rasmussen commented on an issue Re: Puppet does not recompile catalog after failure Andy Parker yes when I restart apache, it will actually generate the new manifests, I have not tested the environment_timeout option, but i'm quite sure that it will do the trick as well. However, why does apache cache a failed catalog? Would it be possible to have apache recreate the catalog every time it has failed? Add Comment Puppet / PUP-3266 Puppet does not recompile catalog after failure I have a setup which works, puppet master compiles catalog and client applies this. Then I make a typo in an included class for my node. Rerun puppet agent on client, it will (sometimes) create an error like this: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class Some.class.name for node.name If I t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-3266) Puppet does not recompile catalog after failure
Title: Message Title Andy Parker commented on an issue Re: Puppet does not recompile catalog after failure Thomas Rasmussen, it isn't caching a failed catalog. The catalog is the output of running the puppet manifests and it has cached manifests that, when run, will produce an error. It is possible that we could have it invalidate that cache if there was an error, but that could lead to extra load on the master in some situations. Add Comment Puppet / PUP-3266 Puppet does not recompile catalog after failure I have a setup which works, puppet master compiles catalog and client applies this. Then I make a typo in an included class for my node. Rerun puppet agent on client, it will (sometimes) create an error like this: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class Some.class.name for node.name If I t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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,
Jira (PUP-3266) Puppet does not recompile catalog after failure
Title: Message Title Andy Parker commented on an issue Re: Puppet does not recompile catalog after failure Thomas Rasmussen, it sounds like you are encountering puppet's cacheing of manifests. Puppet will only reread a manifest file if a certain amount of time has elapsed (controlled by environment_timeout when directory environments are in effect). Before that timeout has expired it will continue to use the bad manifests and you'll get catalog errors. There are two development workflows that you can use that work well: 1. Set the environment_timeout to 0, which causes it to always reread the manifests 2. Restart apache, or gracefully restart apache, or touch restart.txt if you are using passenger when you want the changes you have made to be picked up: edit - restart - run agent. Does this address the problem you are having? Add Comment Puppet / PUP-3266 Puppet does not recompile catalog after failure I have a setup which works, puppet master compiles catalog and client applies this. Then I make a typo in an included class for my node. Rerun puppet agent on client, it will (sometimes) create an error like this: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class Some.class.name for node.name If I t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3266) Puppet does not recompile catalog after failure
Title: Message Title Andy Parker assigned an issue to Thomas Rasmussen Puppet / PUP-3266 Puppet does not recompile catalog after failure Change By: Andy Parker Assignee: KyloGinsberg ThomasRasmussen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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.
Jira (PUP-3266) Puppet does not recompile catalog after failure
Title: Message Title Thomas Rasmussen created an issue Puppet / PUP-3266 Puppet does not recompile catalog after failure Issue Type: Bug Affects Versions: 3.7.1 Assignee: Kylo Ginsberg Components: Catalog Application Created: 17/Sep/14 12:38 AM Environment: Ubuntu 14.04.01 LTS Puppet installed from puppetlabs ubuntu repo puppet 3.7.1-1puppetlabs1 Running puppet master via Passenger Priority: Normal Reporter: Thomas Rasmussen I have a setup which works, puppet master compiles catalog and client applies this. Then I make a typo in an included class for my node. Rerun puppet agent on client, it will (sometimes) create an error like this: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class Some.class.name for node.name If I then correct the introduced error (undo the typo) and run 'puppet agent -t' on my client, it will continue to produce the error message. All I can do to get it working again is either:
Jira (PUP-3266) Puppet does not recompile catalog after failure
Title: Message Title Thomas Rasmussen commented on an issue Re: Puppet does not recompile catalog after failure On some more testing, I found that it does not only apply to errors on compile... it also is visible when making changes to manifests, then if a puppet run has been run in the last few minutes, then it will use a cached version of the catalog and not a newly compiled one (with the changes applied) Add Comment Puppet / PUP-3266 Puppet does not recompile catalog after failure I have a setup which works, puppet master compiles catalog and client applies this. Then I make a typo in an included class for my node. Rerun puppet agent on client, it will (sometimes) create an error like this: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class Some.class.name for node.name If I t... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
