Jira (PUP-5506) Making the source parameter authoritative for the gem package provider
Title: Message Title Alan Schwarzenberger commented on PUP-5506 Re: Making the source parameter authoritative for the gem package provider Worth stating specifically that we should align how the three providers work ... gem, puppet_gem and puppetserver_gem. 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-5506) Making the source parameter authoritative for the gem package provider
Title: Message Title Alan Schwarzenberger commented on PUP-5506 Re: Making the source parameter authoritative for the gem package provider The Ruby documentation states that --sources appends to the list of sources. So in fact it is the --clear-sources that is positionally dependent. This is the same problem as MODULES-4815 which was for the puppetserver gem provider. You might like to copy that solution, or if there is a better solution here to refactor the solution there. There I proposed that install_options should always be put on the command line before the source option (if present). That seems to work and have no side effects because I could not find any other parameters for the gem command which were positionally dependent. 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-5868) yumrepo does not remove repo file
Title: Message Title
Alan Schwarzenberger commented on PUP-5868
Re: yumrepo does not remove repo file
Hi, also an issue for us on Oracle Linux 6.x and 7.x. Currently running Puppet 4.3.2, but will be upgrading shortly. What 'more information' is needed on this ticket as indicated by the status? I'd be happy to run some tests and supply it. A simple minimal test is:
puppet apply -e "yumrepo { test: ensure=>'present', baseurl=>'http://fakeyumprovider.com/testrepo'}"
Which creates /etc/yum.repos.d/test.repo with content. Then run
puppet apply -e "yumrepo { 'test': ensure=>'absent', }"
Which leaves /etc/yum.repos.d/test.repo as zero bytes.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6376) Add `server_urls` option to puppet with agent failover logic
Title: Message Title Alan Schwarzenberger commented on PUP-6376 Re: Add `server_urls` option to puppet with agent failover logic Answering my own question ... server line is ignored if server_list is present ... see https://github.com/puppetlabs/puppet/blob/master/lib/puppet/defaults.rb#L1405-L1425 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-6376) Add `server_urls` option to puppet with agent failover logic
Title: Message Title Alan Schwarzenberger commented on PUP-6376 Re: Add `server_urls` option to puppet with agent failover logic Please could someone explain, and hopefully add to documentation, what the precedence order of server_list and server lines in puppet.conf is? 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-6809) http report processor does not show error messages from remote server
Title: Message Title Alan Schwarzenberger commented on PUP-6809 Re: http report processor does not show error messages from remote server You may be correct, and I was clearly wrong about the documentation However, the REST API endpoint being used here was sending back HTTP/1.1 400 Bad Request as well as a json response body, as I checked that with curl, yet in the puppetserver log there was never any output after the closing square bracket on the code. Unless you think this merits further investigation I'll be happy for this to be closed as specific to the endpoint the http report provider was trying to send to. 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-6809) http report processor does not show error messages from remote server
Title: Message Title
Alan Schwarzenberger created an issue
Puppet / PUP-6809
http report processor does not show error messages from remote server
Issue Type:
Bug
Affects Versions:
PUP 4.7.0
Assignee:
Unassigned
Created:
2016/10/11 10:12 AM
Environment:
Any. I tested this on Puppet 4.3.2 on Oracle Linux 6.5.1, but I think you can verify the error and fix on any version, or theoretically by looking at the documentation or code for
Priority:
Normal
Reporter:
Alan Schwarzenberger
Code at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/reports/http.rb#L28 contains a coding error.
Puppet.err "Unable to submit report to #{Puppet[:reporturl].to_s} [#{response.code}] #{response.msg}"
Jira (PUP-6809) http report processor does not show error messages from remote server
Title: Message Title Alan Schwarzenberger updated an issue Puppet / PUP-6809 http report processor does not show error messages from remote server Change By: Alan Schwarzenberger Environment: Any. I tested this on Puppet 4.3.2 on Oracle Linux 6.5.1, but I think you can verify the error and fix on any version, or theoretically by looking at the documentation or code for a post to a Puppet::Network::HttpPool.http_instance object. 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-6211) Bad behavior of getvar() from stdlib when strict_variables is set to true
Title: Message Title
Alan Schwarzenberger commented on PUP-6211
Re: Bad behavior of getvar() from stdlib when strict_variables is set to true
Henrik Lindberg we use getvar('::some_fact') as a way of testing if a fact is defined with --strict_variables turned on, which would be broken by your suggestion. Is there a better way to check if a fact is defined?
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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.
