Jira (PUP-11328) Puppet agent may download all plugins after updating
Title: Message Title Breno Fernandes commented on PUP-11328 Re: Puppet agent may download all plugins after updating Thank you, josh and gabriel.nagy for putting this together. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.421154.1635201319000.13059.1641386820033%40Atlassian.JIRA.
Jira (PUP-11328) Puppet agent may download all plugins after updating
Title: Message Title
Breno Fernandes commented on PUP-11328
Re: Puppet agent may download all plugins after updating
Oh, and by the way, this change seems to put the behaviour back in place working:
[root@server /usr/share/ruby/vendor_ruby/puppet]# git diff
diff --git a/configurer.rb b/configurer.rb
index b55ad5d..211b1d3 100644
--- a/configurer.rb
+++ b/configurer.rb
@@ -490,7 +490,7 @@ class Puppet::Configurer
converged_environment = summary['application']['converged_environment']
@last_server_specified_environment = converged_environment if initial_environment != converged_environment
Puppet.debug(_("Successfully loaded last environment from the lastrunfile"))
- @loaded_last_environment = true
+ @loaded_last_environment = false
end
Jira (PUP-11328) Puppet agent may download all plugins after updating
Title: Message Title Breno Fernandes commented on PUP-11328 Re: Puppet agent may download all plugins after updating Hi josh , like I was telling gabriel.nagy , we've been using puppet since puppet 3.X. And we've been using this feature like I described to Gabriel forever. I believe that probably at some point, someone changed the docs, but didn't change the behaviour of the feature. I'd like to gently ask you to consider putting back this feature, since it's something that was working before and was removed suddenly, and catch us and probably others out there, off the guard. I'm the official packager of puppet for Fedora and RedHat (EPEL). I'd like to also volunteer to submit a PR with the documents update. Would you consider putting the feature back? I ask some consideration in the name of the community. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.421154.1635201319000.3928.1639371900047%40Atlassian.JIRA.
Jira (PUP-11328) Puppet agent may download all plugins after updating
Title: Message Title Breno Fernandes commented on PUP-11328 Re: Puppet agent may download all plugins after updating Can you share your puppet.conf when you use the server separete from the agent? Because the external_nodes and node_terminus would be located in the [main] section, not in the [server]. Did you test it like so? Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.421154.1635201319000.144.1638890940090%40Atlassian.JIRA.
Jira (PUP-11328) Puppet agent may download all plugins after updating
Title: Message Title Breno Fernandes commented on PUP-11328 Re: Puppet agent may download all plugins after updating Well, I'm clearly seeing a bug on my end, like I shared. The only difference now is that I'm using the package we build in fedora. What's the version of puppetserver you're running and do you believe that would make a difference if I'm using an older version? Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.421154.1635201319000.132.1638889740046%40Atlassian.JIRA.
Jira (PUP-11328) Puppet agent may download all plugins after updating
Title: Message Title Breno Fernandes commented on PUP-11328 Re: Puppet agent may download all plugins after updating One relevant change is that I am using puppetserver and puppet agent in two different boxes. Don't you think that would make a difference? Specially because the actual environments (the files themselves) won't be present on puppet agent. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.421154.1635201319000.107.1638887340038%40Atlassian.JIRA.
Jira (PUP-11328) Puppet agent may download all plugins after updating
Title: Message Title Breno Fernandes commented on PUP-11328 Re: Puppet agent may download all plugins after updating Oh please, also share your puppet.conf Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.421154.1635201319000.77.1638885240033%40Atlassian.JIRA.
Jira (PUP-11328) Puppet agent may download all plugins after updating
Title: Message Title Breno Fernandes commented on PUP-11328 Re: Puppet agent may download all plugins after updating Do you mind sharing the output of your enc.sh? I'll do the exact same test on my end. Also, is this with puppet 7 or puppet 6? What about puppetserver? It doesn't seem like you have the issue. I am testing with puppet 6 from EPEL 8 [1]. I'm the packager, but from the previous version, not much has changed. I'm sharing the bootstrap file (spec) maybe you can spot an issue there? 1 https://src.fedoraproject.org/rpms/puppet/blob/rawhide/f/puppet.spec Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.421154.1635201319000.76.1638884760072%40Atlassian.JIRA.
Jira (PUP-11328) Puppet agent may download all plugins after updating
Title: Message Title Breno Fernandes commented on PUP-11328 Re: Puppet agent may download all plugins after updating Btw, if you are going to test it, switch the environment via node_terminus more than once. Ensure it works every single time. Because it works on the first time, but if you switch to another environment, it doesn't work anymore. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.421154.1635201319000.18161.1638390660025%40Atlassian.JIRA.
Jira (PUP-11328) Puppet agent may download all plugins after updating
Title: Message Title Breno Fernandes commented on PUP-11328 Re: Puppet agent may download all plugins after updating So that's what I am not having here. Can you confirm what you're saying is actually what is happening? In my tests with puppetserver 6.10 + puppet agent 6.25.1, and a client with puppet agent 6.25.1. Puppet agent will not use the env specified by node_terminus if the file $statedir/last_run_summary.yaml exists. If we just remove the converged environment line, puppet will try to apply the default environment. That's the behavior I have here with multiple different boxes. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.421154.1635201319000.18158.1638390360035%40Atlassian.JIRA.
Jira (PUP-11328) Puppet agent may download all plugins after updating
Title: Message Title Breno Fernandes commented on PUP-11328 Re: Puppet agent may download all plugins after updating Josh Cooper would you mind clarifying an issue I'm facing? I use node_terminus to specify dynamic environments (on the agent). After this ticket, now if last_run_summary.yaml has a converged_environment specified, puppet agent will not use the environment that node_terminus is telling the agent to use. It will use instead what's in last_run_summary.yaml which is very bad. If before running puppet I remove the last_run_summary.yaml file I have my expected behavior. If I remove the converged_environment line, puppet will try to apply the "production" (default) environment. Is that expected? And if so, why is that? The expected behavior IMO should be: if we have node_terminus configured, that will always have precedence over what is last_run_summary.yaml. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.421154.1635201319000.18094.1638386280033%40Atlassian.JIRA.
Jira (PUP-10957) Support ruby 3
Title: Message Title Breno Fernandes commented on PUP-10957 Re: Support ruby 3 Do we have any deadline for this? Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.390422.161530306.34057.1621262040031%40Atlassian.JIRA.
Jira (PUP-10957) Support ruby 3
Title: Message Title Breno Fernandes commented on PUP-10957 Re: Support ruby 3 PUP-10247 may fix PUP-10957. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.390422.161530306.160829.1615303800067%40Atlassian.JIRA.
Jira (PUP-10957) Support ruby 3
Title: Message Title Breno Fernandes created an issue Puppet / PUP-10957 Support ruby 3 Issue Type: Epic Affects Versions: PUP 7.4.1 Assignee: Unassigned Created: 2021/03/09 7:17 AM Priority: Normal Reporter: Breno Fernandes Hi, Fedora 34 ships ruby 3.0. Very soon it will be on Redhat, Centos and Rockylinux. It would be really cool if we could fix what is remaining to make puppet work with ruby 3. Here is what I get when I try to run it on a fedora 34 and ruby 3: ruby --version ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-linux] puppet --version /usr/share/ruby/vendor_ruby/puppet/util.rb:476:in `uri_encode': undefined method `escape' for URI:Module (NoMethodError) from /usr/share/ruby/vendor_ruby/puppet/util.rb:344:in `path_to_uri' from /usr/share/ruby/vendor_ruby/puppet/pops/model/ast.rb:4957:in `register_pcore_types' from /usr/share/ruby/vendor_ruby/puppet/pops.rb:120:in `' from /usr/share/ruby/vendor_ruby/puppet/pops.rb:1:in `' from :85:in `require' from :85:in `require' from /usr/share/ruby/vendor_ruby/puppet/parser/compiler.rb:8:in `' from :85:in `require' from :85:in `require' from /usr/share/ruby/vendor_ruby/puppet/parser.rb:6:in `' from :85:in `require' from :85:in `require' from /usr/share/ruby/vendor_ruby/puppet.rb:360:in `' from :85:in `require' from :85:in `require' from /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:12:in `' from :85:in `require' from :85:in `require' from /usr/bin/puppet:4:in `'
Jira (PUP-10247) Support ruby 2.7
Title: Message Title Breno Fernandes commented on PUP-10247 Re: Support ruby 2.7 Hi, Fedora 34 ships ruby 3.0. It would be really cool if we could fix what is remaining to make puppet work with ruby 3. Here is what I get when I try to run it on a fedora 34 and ruby 3: ruby --version ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-linux] puppet --version /usr/share/ruby/vendor_ruby/puppet/util.rb:476:in `uri_encode': undefined method `escape' for URI:Module (NoMethodError) from /usr/share/ruby/vendor_ruby/puppet/util.rb:344:in `path_to_uri' from /usr/share/ruby/vendor_ruby/puppet/pops/model/ast.rb:4957:in `register_pcore_types' from /usr/share/ruby/vendor_ruby/puppet/pops.rb:120:in `' from /usr/share/ruby/vendor_ruby/puppet/pops.rb:1:in `' from :85:in `require' from :85:in `require' from /usr/share/ruby/vendor_ruby/puppet/parser/compiler.rb:8:in `' from :85:in `require' from :85:in `require' from /usr/share/ruby/vendor_ruby/puppet/parser.rb:6:in `' from :85:in `require' from :85:in `require' from /usr/share/ruby/vendor_ruby/puppet.rb:360:in `' from :85:in `require' from :85:in `require' from /usr/share/ruby/vendor_ruby/puppet/util/command_line.rb:12:in `' from :85:in `require' from :85:in `require' from /usr/bin/puppet:4:in `' Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs"
Jira (PUP-8419) Agent's node request fails if environment directory doesn't exist locally
Title: Message Title Breno Fernandes commented on PUP-8419 Re: Agent's node request fails if environment directory doesn't exist locally I can still replicate this issue on puppet 6 on el8. Red Hat Enterprise Linux release 8.1 (Ootpa) puppet --version 6.9.0 This is the puppet.conf file I am using: [main] http_compression = true pluginsync = true node_terminus = exec external_nodes = /path-to-my/enc.sh usecacheonfailure = false If I "manually" create the directory of that dynamic environment locally (under its default location), it works. So, I believe that this issue is not fully fixed. Please, let me know if you need more information. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.235343.1517910596000.48363.1574976120586%40Atlassian.JIRA.
