Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Henrik Lindberg commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources Thanks Andrew Grimberg for coming back with that information. I will update the title to better reflect the actual problem. (BTW: There may be a problem with virtual resources as well). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Andrew Grimberg commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources Just following up. I finally managed to get some time to rewrite all the create_resources calls in the module. It looks like the problem is specific to create_resources for exported resources. Since create_resources is supposed to get a quoted resource name to create, any '@@something' ends up having this failure. Other create_resources work just fine. Switching to a lambda notation does appear to completely resolve the issue. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Henrik Lindberg commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources Angel L. Mateo I think it may be best if you hop onto Slack and the #puppet-dev channel to discuss with others that implements types and providers. Much easier to do a show and tell interactively there. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title
Angel L. Mateo commented on PUP-6698
Re: Puppet server 2.5.0 does not properly handle exported file resources
More info... Although I thought that changing create_resources for a loop solved the problem, it doesn't. It only solves it for the first puppet run, unless with my custom type. I have my own custom type called thruk_bp_node. This type creates a file in /opt/puppetlabs/puppet/cache/thruk path (among other things). The code in my puppet manifest is:
#
# Crea los nodos de BPs que pueda haber definidos
$thruk_bp_nodes.each |$name, $opts| {
@@thruk_bp_node {$name:
* => $opts,
}
}
Then I collect these exported resources in a node to actually create resources. As I said, in the first puppet execution it worked without any problem, but in the rests of executions I get the error:
Notice: /Stage[main]/Profile::Slapd/Thruk_bp_node[atica/Autenticación de usuarios/tlm_canis31]/ensure: created
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Angel L. Mateo commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources I have checked that replacing create_resources with a loop creating the resources fixes the problem. I have also tried with puppetserver 2.7.0 (with create_resources) and the problems seems to be fixed too. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Henrik Lindberg commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources One thing that has changed is that create_resources now uses the exact same evaluation order as if the corresponding resources were created in a manifest. This can have an effect on the order in which the resources are applied, but is primarily only an evaluation order difference. Earlier, all resources created with create_resources where fully evaluated and placed in the catalog at the time the create_resources call finishes. Now they are placed on the lazy resource evaluation queue just like resources created in manifests. If you happen to have logic that depends on resources being in the catalog, then it may produce something different after the change. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Andrew Grimberg commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources I'll have to do some testing for the catalogs but here's the answer for the other questions: All nodes are in the same environment IIRC this issues seems to only affect nagios exported resources. My environment uses exported resources liberally for setting up databases, webserver and haproxy proxy frontends, as well as backups, nfs, etc. When I get a chance today (maybe tomorrow if I have to) I'll try and run some scenarios in my test lab so I can answer that in more depth. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Henrik Lindberg commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources Can you compare the catalog from a successful run with one that is failing? (eliminate compiler) Are the exporting and importing nodes in the same environment? (eliminate finding old export made in importing env). Is the problem specific to one type of resource - does a test with an export of something like a notify or file work? (eliminate configuration problems) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Andrew Grimberg commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources I've given a trace from the client side as well. I'll point out that this only happens if the puppetserver is running on puppet-agent > 1.5.3. I have no issues with the recent puppet-agent against a puppet server that is configured with puppet-agent <= 1.5.3 So scenarios I've run: Server 1.5.3 Server 1.6.0 Server 1.7.0 Server 1.8.0 Remote Client 1.5.3 No issues Not tested Not tested Not tested Remote Client 1.6.0 No Issues Fails Fails Fails Remote Client 1.7.0
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Henrik Lindberg commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources The earlier gist indicates that the problem is on the agent: Error: Puppet::Util::FileType::FileTypeFlat could not write /etc/nagios/conf.d/host_puppet.home.bardicgrove.org_puppet.home.bardicgrove.org.cfg: No such file or directory @ rb_sysopen - /etc/nagios/conf.d/host_puppet.home.bardicgrove.org_p uppet.home.bardicgrove.org.cfg This is when it is applying the catalog. I don't think there is anything wrong with the compiling side (i.e. the call to create_resources is not to blame). The problem seems to be in nagios. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Angel L. Mateo commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources Small note, in your sample the construct @@omd_nagios_service should be quoted when given as an argument to create_resources - is it a typo in the ticket, or is that what you actually tried? It's a typo in the ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Andrew Grimberg commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources So I updated my test puppet master again and enabled tracing on the server per https://docs.puppet.com/puppetserver/latest/dev_trace_func.html at the top. I'm running the puppetserver AIO package and don't have a master.rb to modify to set a trace function. Here's the relevant portion from the server logs: https://gist.github.com/tykeal/cc9f22b5ab30b91260f4a96ee8fa0575 For my failing exported resource call it's this call here: https://github.com/tykeal/puppet-nagios/blob/master/manifests/resource/host.pp which all of my systems get you'll see that my create_resources call does have the @@nagios_host is quoted in my call. I don't see anything from the server log that is an actual trace, with or without the trace option enabled I get the same logs. The portion I gisted doesn't give any visible reason why the export would be trying to write to a local file. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Henrik Lindberg commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources And now I read up on previous comments - it seems like tests were made on latest version. To be able to help we need to understand what is happening on the master, not the agent. Exported resources are exported as well as imported during compilation - the agent is not involved, it only asks for the catalog from the master. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Henrik Lindberg commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources We have made a lot of refactoring of the code paths for resource creation in Puppet 4.7.0 to ensure that create_resources and resource creation using other language constructs follow the exact same code path. It would be of great value if you could test your sample on the latest available puppet version. Small note, in your sample the construct @@omd_nagios_service should be quoted when given as an argument to create_resources - is it a typo in the ticket, or is that what you actually tried? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title
Angel L. Mateo commented on PUP-6698
Re: Puppet server 2.5.0 does not properly handle exported file resources
One more test I've done... I'm creating exported resources with a create_resources call. Something like:
create_resources(@@omd_nagios_service, $services)
I have tried to change it to puppet 4 loop like:
$services.each |$s, $o| {
@@omd_nagios_service {$s:
* => $o,
}
}
With this code, the problem seems to be fixed, but I have to make a more exhaustive test to confirm it.
Add Comment
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Andrew Grimberg commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources Just an update since puppet-agent 1.8.0 just released. This is still a problem. It's blocking us from upgrading any of our puppet servers past puppet-agent v1.5.3 and puppetserver v2.4.0. Non-puppet server clients are not affected by this, it is something that is happening during manifest creation that is sent to the clients. As I was asked to do a trace and gist it (sorry for not doing so sooner) here's the trace using puppet-agent 1.8.0 I ran this on my test puppet server which is not a nagios server, just a client, so the paths that are trying to be written too for exported resources don't exist. Gist: https://gist.github.com/tykeal/505402e0d928a81bd813863bf1611a48 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Chris Price updated an issue Puppet / PUP-6698 Puppet server 2.5.0 does not properly handle exported file resources Change By: Chris Price Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Angel L. Mateo commented on PUP-6698 Re: Puppet server 2.5.0 does not properly handle exported file resources The problem is still present with puppet-agent 1.7.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
Jira (PUP-6698) Puppet server 2.5.0 does not properly handle exported file resources
Title: Message Title Kylo Ginsberg moved an issue Puppet / PUP-6698 Puppet server 2.5.0 does not properly handle exported file resources Change By: Kylo Ginsberg Affects Version/s: SERVER 2.5.0 Affects Version/s: SERVER 2.4.0 Affects Version/s: PUP 4.6.0 Key: SERVER PUP - 1495 6698 Project: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe
