Jira (PUP-6217) site.pp with file resource containing UTF8 failing on certain platforms
Title: Message Title Ethan Brown commented on PUP-6217 Re: site.pp with file resource containing UTF8 failing on certain platforms Stacktrace points to the `.gsub` at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/colors.rb#L92 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.
Jira (PUP-6217) site.pp with file resource containing UTF8 failing on certain platforms
Title: Message Title Eric Thompson commented on PUP-6217 Re: site.pp with file resource containing UTF8 failing on certain platforms --trace: jzhs4gu5sg0xuan.delivery.puppetlabs.net (jzhs4gu5sg0xuan.delivery.puppetlabs.net) 20:48:30$ puppet agent -t --trace --environment supports_utf8_nykihbtf --server szl38k2b9kcl48n.delivery.puppetlabs.net Info: Using configured environment 'supports_utf8_nykihbtf' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Caching catalog for jzhs4gu5sg0xuan.delivery.puppetlabs.net Info: Applying configuration version '1461296915' Error: invalid byte sequence in US-ASCII /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/colors.rb:92:in `gsub' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/colors.rb:92:in `console_color'
Jira (PUP-6217) site.pp with file resource containing UTF8 failing on certain platforms
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-6217
site.pp with file resource containing UTF8 failing on certain platforms
Change By:
Eric Thompson
{code} jzhs4gu5sg0xuan.delivery.puppetlabs.net (sles10-64-1) 20:41:15$ puppet agent -t --environment supports_utf8_y3vl7m8o --server szl38k2b9kcl48n.delivery.puppetlabs.net Info: Using configured environment 'supports_utf8_y3vl7m8o' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Caching catalog for jzhs4gu5sg0xuan.delivery.puppetlabs.net Info: Applying configuration version '1461296478' Error: invalid byte sequence in US-ASCII Error: /Stage[main]/Main/File[/tmp/supports_utf8_y3vl7m8o.xW6229]/content: change from {md5}d41d8cd98f00b204e9800998ecf8427e to {md5}f1c1271f5e21eba48374b96e43caddc1 failed: invalid byte sequence in US-ASCII Notice: Applied catalog in 0.13 seconds{code} see:https://github.com/puppetlabs/puppet/blob/stable/acceptance/tests/direct_puppet/supports_utf8.rb(we can't use expect_failure() in that test, so test will have to be unskipped when this is fixed)failing on: * arista4-32* cumulus25-64* osx1009* osx1010* osx1011* sles10
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
Jira (PUP-6210) Report overall status should not be noop because of only one noop resource
Title: Message Title Verne Lindner commented on PUP-6210 Re: Report overall status should not be noop because of only one noop resource Karel Brezina With the new CM dashboard run status designations, are we ignoring resource no-op flags when determining run status? 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.
Jira (FACT-1357) puppet-agent build fails on facter unit test if bundle is installed
Title: Message Title Branan Riley commented on FACT-1357 Re: puppet-agent build fails on facter unit test if bundle is installed I'm inclined to make this a p-a ticket and just run the bundle install. That seems like the lowest-resistance path to cleaning it up 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.
Jira (PUP-5891) Impossible to see the difference in the logs between a refreshed exec that has run and one that has not run
Title: Message Title Branan Riley commented on PUP-5891 Re: Impossible to see the difference in the logs between a refreshed exec that has run and one that has not run I think this falls into the same bucket as our failure to report well on service refreshes. We need to better integrate "Stuff that happens due to a refresh" into the overall logging and reporting structure, and this is just one facet of that 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.
Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory.
Title: Message Title Branan Riley commented on PUP-2608 Re: An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory. From the PUP-3655 notes, I'm inclined to say that we shouldn't 404 if there are no modules on disc. "There's nothing to pluginsync" is an empty metadata set, not a missing metadata set. 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.
Jira (PDB-2648) Add a basic checking of the "query" parameter in the function puppetdb_query()
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2648 Add a basic checking of the "query" parameter in the function puppetdb_query() Change By: Kenneth Barber Fix Version/s: PDB 4.1.0 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.
Jira (PDB-2648) Add a basic checking of the "query" parameter in the function puppetdb_query()
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2648 Add a basic checking of the "query" parameter in the function puppetdb_query() Change By: Kenneth Barber Issue Type: Bug Task 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.
Jira (FACT-935) Move http wrapper library to Leatherman
Title: Message Title Michael Smith commented on FACT-935 Re: Move http wrapper library to Leatherman Wow, that was pretty ambiguous. Pretty sure this was Leatherman curl bindings. 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.
Jira (FACT-935) Move http wrapper library to Leatherman
Title: Message Title Branan Riley commented on FACT-935 Re: Move http wrapper library to Leatherman Michael Smith Can you toss a bit more info into this ticket? 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.
Jira (PDB-2621) PDB should return content type for errors
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2621 PDB should return content type for errors Change By: Kenneth Barber Affects Version/s: PDB 4.0.0 Fix Version/s: PDB 4.0.2 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.
Jira (PUP-5544) Resource type zpool create options
Title: Message Title Branan Riley assigned an issue to Eric Sorenson Puppet / PUP-5544 Resource type zpool create options Change By: Branan Riley Status: Ready for Engineering Accepted 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.
Jira (PUP-4682) Deprecate Cisco types/providers
Title: Message Title Branan Riley assigned an issue to Eric Sorenson Puppet / PUP-4682 Deprecate Cisco types/providers Change By: Branan Riley Status: Ready for Engineering Accepted 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.
Jira (PUP-6218) puppet resource service extremely slow on Solaris
Title: Message Title Branan Riley moved an issue Puppet / PUP-6218 puppet resource service extremely slow on Solaris Change By: Branan Riley Fix Version/s: PE 3.y Affects Version/s: PE 3.0.0 Component/s: Platform Key: PE PUP - 809 6218 Project: Puppet Enterprise [Internal] 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
Jira (PUP-6216) Puppet agent run is not clearing USER environment variable on VIO AIX
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6216 Puppet agent run is not clearing USER environment variable on VIO AIX Change By: Kylo Ginsberg Sprint: Client Triage 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.
Jira (PUP-6216) Puppet agent run is not clearing USER environment variable on VIO AIX
Title: Message Title Adam Bottchen commented on PUP-6216 Re: Puppet agent run is not clearing USER environment variable on VIO AIX Kylo Ginsberg I agree. I do not understand why it mattered, but in my testing it seemed to. 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.
Jira (PDB-2648) Add a basic checking of the "query" parameter in the function puppetdb_query()
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2648 Add a basic checking of the "query" parameter in the function puppetdb_query() Issue Type: Bug Assignee: Unassigned Created: 2016/04/21 3:27 PM Priority: Normal Reporter: gepetto-bot To be compatible with Puppet 4.0.0 where recursive types are not possible, the type checked here is not accurate. Ideally, the type should be: Variant[String[1], StringTree] where StringTree is defined (recursively) by: StringTree = Array[Variant[String, StringTree]] Add Comment This message was sent by Atlassian JIRA
Jira (PUP-6113) `puppet resource user` on Solaris fails when LDAP users are present
Title: Message Title Branan Riley updated an issue Puppet / PUP-6113 `puppet resource user` on Solaris fails when LDAP users are present Change By: Branan Riley Release Notes Summary: Puppet will no longer attempt to retrieve the nonexistent password_min_age property from LDAP users on Solaris. 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.
Jira (PUP-6113) `puppet resource user` on Solaris fails when LDAP users are present
Title: Message Title Branan Riley updated an issue Puppet / PUP-6113 `puppet resource user` on Solaris fails when LDAP users are present Change By: Branan Riley Release Notes: Bug Fix 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.
Jira (NPUP-28) Integrate Onigmo for maximum regex compatibility with existing Puppet regular expressions
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-28 Integrate Onigmo for maximum regex compatibility with existing Puppet regular expressions Change By: Peter Huene Scope Change Category: Adopted Scope Change Reason: Adopted into the sprint as deemed an important feature to implement Sprint: Language Triage 2016-05-04 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.
Jira (PUP-6197) Is the Jira tidy-up done for this release and prepared for the next one? (PUP 3.8.7)
Title: Message Title Kylo Ginsberg commented on PUP-6197 Re: Is the Jira tidy-up done for this release and prepared for the next one? (PUP 3.8.7) Jorie Tappa links! * Fixes for puppet 3.8.7: https://tickets.puppetlabs.com/issues/?filter=19117 Introduced in puppet 3.8.7: https://tickets.puppetlabs.com/issues/?filter=19118 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.
Jira (PUP-6217) site.pp with file resource containing UTF8 failing on certain platforms
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6217 site.pp with file resource containing UTF8 failing on certain platforms Change By: Eric Thompson see:https://github.com/puppetlabs/puppet/blob/stable/acceptance/tests/direct_puppet/supports_utf8.rb (we can't use expect_failure() in that test, so test will have to be unskipped when this is fixed) failing on: * arista4-32* cumulus25-64* osx1009* osx1010* osx1011* sles10 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.
Jira (PUP-6113) `puppet resource user` on Solaris fails when LDAP users are present
Title: Message Title Kylo Ginsberg commented on PUP-6113 Re: `puppet resource user` on Solaris fails when LDAP users are present Branan Riley can you drop a release note summary on this one? 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.
Jira (HI-511) ability to work with complex datatypes from facter
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-511 ability to work with complex datatypes from facter Change By: Henrik Lindberg Scrum Team: Language 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.
Jira (PUP-6217) site.pp with file resource containing UTF8 failing on certain platforms
Title: Message Title
Sean Griffin commented on PUP-6217
Re: site.pp with file resource containing UTF8 failing on certain platforms
If I run the test by hand with a sles-10-x86_64 client, it fails the same way it does in jenkins: Info: Applying configuration version '1461273474' Error: invalid byte sequence in US-ASCII Error: /Stage[main]/Main/File[/tmp/supports_utf8_kl9eg6or.mL6355]/content: change from {md5}d41d8cd98f00b204e9800998ecf8427e to {md5}
f1c1271f5e21eba48374b96e43caddc1 failed: invalid byte sequence in US-ASCII
But: If I stop the test in with pry at the point where it makes its first call to puppet agent -t, then run that command on the client, the catalog applies successfully. Removing the target file and continuing the stopped test, it completes successfully too!
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.
Jira (PUP-6217) site.pp with file resource containing UTF8 failing on certain platforms
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6217 site.pp with file resource containing UTF8 failing on certain platforms Change By: Kylo Ginsberg Labels: i18n utf-8 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.
Jira (PUP-6216) Puppet agent run is not clearing USER environment variable on VIO AIX
Title: Message Title Kylo Ginsberg commented on PUP-6216 Re: Puppet agent run is not clearing USER environment variable on VIO AIX Hmm, I'm missing why that needs to be done outside the fork, and why the same environment variable change a few lines down inside the fork isn't doing what you expect. But the crontab provider and the parsedfile provider it inherits from have some historical assumptions so this might take some archaeology to sort out. 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.
Jira (PDB-773) Add primary keys to 'edges' and 'resource_events'
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-773 Add primary keys to 'edges' and 'resource_events' Change By: Wyatt Alt Assignee: Wyatt Alt 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.
Jira (PUP-6217) site.pp with file resource containing UTF8 failing on certain platforms
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6217 site.pp with file resource containing UTF8 failing on certain platforms Change By: Kylo Ginsberg Labels: i18n 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.
Jira (PUP-6217) site.pp with file resource containing UTF8 failing on certain platforms
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6217 site.pp with file resource containing UTF8 failing on certain platforms Change By: Eric Thompson Summary: cached catalog site.pp with file resource containing UTF8 failing on certain platforms 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.
Jira (PUP-6217) cached catalog containing UTF8 failing on certain platforms
Title: Message Title Eric Thompson created an issue Puppet / PUP-6217 cached catalog containing UTF8 failing on certain platforms Issue Type: Bug Assignee: Unassigned Created: 2016/04/21 1:50 PM Priority: Normal Reporter: Eric Thompson see: https://github.com/puppetlabs/puppet/blob/stable/acceptance/tests/direct_puppet/supports_utf8.rb failing on: arista4-32 cumulus25-64 osx1009 osx1010 osx1011 sles10
Jira (FACT-1392) Facter fails when locale files are missing for specified locale on CentOS 7
Title: Message Title John Duarte commented on FACT-1392 Re: Facter fails when locale files are missing for specified locale on CentOS 7 Unable to reproduce issue on OpenStack CentOS image. Steps to reproduce Verify that LOCALE is not properly configured -bash-4.2# locale -a locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_COLLATE to default locale: No such file or directory C POSIX Remove facter 2.4.1 The reported affected version is 3.1.0, so the previously installed facter 2.4.1 will be removed. yum -y remove facter Install puppet-agent 1.2.6 The affected version is
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Nate McCurdy updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Nate McCurdy CS Priority: Needs Priority 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.
Jira (PDB-2647) automatic updating of documented ERD diagram
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2647 automatic updating of documented ERD diagram Issue Type: Task Assignee: Unassigned Created: 2016/04/21 12:18 PM Priority: Normal Reporter: Wyatt Alt dbvis has a command line interface that should make this possible – not sure if this is a build pipeline thing or a cron job we run somewhere, but we should automatically pick up schema changes and commit a new diagram to the repo. If this introduces repo size concerns (seems unlikely given image sizes and low frequency of change) then we'll need to figure something else out (maybe GH large file storage or something, or maybe there's a text based representation we could be rendering in the browser). Add Comment
Jira (PDB-2646) consider dropping experimental status of the root endpoint
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2646 consider dropping experimental status of the root endpoint Issue Type: Task Assignee: Unassigned Created: 2016/04/21 12:02 PM Priority: Normal Reporter: Wyatt Alt PQL is experimental, but realistically the root endpoint is not going away – the only change that could occur to the root endpoint itself would be to relocate it, and I'd be comfortable committing to not doing that outside a major at this point. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (NPUP-28) Integrate Onigmo for maximum regex compatibility with existing Puppet regular expressions
Title: Message Title Peter Huene assigned an issue to Peter Huene Native Puppet / NPUP-28 Integrate Onigmo for maximum regex compatibility with existing Puppet regular expressions Change By: Peter Huene Assignee: Peter Huene 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.
Jira (PUP-6216) Puppet agent run is not clearing USER environment variable on VIO AIX
Title: Message Title Adam Bottchen created an issue Puppet / PUP-6216 Puppet agent run is not clearing USER environment variable on VIO AIX Issue Type: Bug Affects Versions: PUP 4.4.1 Assignee: Kylo Ginsberg Components: Client Created: 2016/04/21 11:23 AM Priority: Normal Reporter: Adam Bottchen Puppet agent is not clearing the USER environment variable before executing crontab -l on AIX VIO servers. This leads to errors during puppet runs: # /opt/puppetlabs/bin/puppet agent -t Info: Using configured environment 'production'
Jira (HI-512) My Organization have an a DNS Puppet and I need insert an CNAME record
Title: Message Title Julio Gustavo Cañete created an issue Hiera / HI-512 My Organization have an a DNS Puppet and I need insert an CNAME record Issue Type: Task Assignee: Unassigned Components: Community Created: 2016/04/21 11:20 AM Priority: Normal Reporter: Julio Gustavo Cañete Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) --
Jira (PUP-6215) puppet apply --noop triggers services on file audit content changes
Title: Message Title
Brad Rubenstein created an issue
Puppet / PUP-6215
puppet apply --noop triggers services on file audit content changes
Issue Type:
Bug
Affects Versions:
PUP 3.6.2
Assignee:
Unassigned
Created:
2016/04/21 11:16 AM
Environment:
CentOS 7 puppet-3.6.2-3.el7.noarch
Priority:
Normal
Reporter:
Brad Rubenstein
To reproduce: site.pp:
file { $myfile: ensure => present, audit => 'content'; }
File[$myfile] ~> Service[$myservice]
# rm $myfile # puppet apply --noop --test site.pp
Expected: the output would show what would be done, but nothing would be done Actual: the ensure is marked "noop", but the audit change is not. The service is triggered. Partial command output [redacted]: Notice: .../File[myfile]/ensure: current_value absent, should be file (noop) Notice: .../File[myfile]/content: audit change: previously recorded value has been changed to absent Info: .../File[myfile]: Scheduling refresh of Service[myservice] Notice: ../Service[myservice]: Triggered 'refresh' from 2 events
Jira (PUP-6125) verbose agent runs result data being sent console and syslog
Title: Message Title Charlie Sharpsteen commented on PUP-6125 Re: verbose agent runs result data being sent console and syslog It seems undesirable to have verbose/debug/show-diff going to syslog as a default, as they're more likely to contain secrets. I think we should be careful not to overload these. Leaving them as simple switches which enable or disable a certain kind of output seems like the most understandable and maintainable behavior. For the case of sensitive data, I think PUP-5832 is the right way to approach this by allowing users to mark resources or parameters as sensitive and letting the system respond appropriately by redacting related log messages and suppressing diffs. For the case of logdest, I agree that we shouldn't be recording output in syslog when users don't expect it. For example, puppet agent -t probably shouldn't send messages to syslog when invoked interactively — that's probably unexpected behavior in most cases. 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.
Jira (PUP-6214) Confusing error message displayed when using incorrect value with scheduled_task resource
Title: Message Title
Greg Larkin created an issue
Puppet / PUP-6214
Confusing error message displayed when using incorrect value with scheduled_task resource
Issue Type:
Bug
Assignee:
Unassigned
Components:
DSL
Created:
2016/04/21 11:13 AM
Priority:
Normal
Reporter:
Greg Larkin
I recently used a scheduled_task resource and coded the trigger section incorrectly like so:
scheduled_task { 'defrag C':
ensure => present,
enabled => true,
Jira (PUP-6208) Invalid byte sequence in US-ASCII on gem install
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6208 Invalid byte sequence in US-ASCII on gem install Change By: Kylo Ginsberg Labels: gem i18n 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.
Jira (PUP-6213) Puppet Accepts Strings for the "returns" Attribute of the "exec" Type
Title: Message Title Branan Riley updated an issue Puppet / PUP-6213 Puppet Accepts Strings for the "returns" Attribute of the "exec" Type Change By: Branan Riley Environment: Master: 1GB RAM -CentOS 6 x64Agent: 1GB RAM - RHEL 7 x64 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.
Jira (PUP-6212) Puppet Accepts an Empty Array for the "returns" Attribute of the "exec" Type
Title: Message Title Branan Riley updated an issue Puppet / PUP-6212 Puppet Accepts an Empty Array for the "returns" Attribute of the "exec" Type Change By: Branan Riley Environment: Master: 1GB RAM -CentOS 6 x64Agent: 1GB RAM - RHEL 7 x64 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.
Jira (PUP-6213) Puppet Accepts Strings for the "returns" Attribute of the "exec" Type
Title: Message Title Branan Riley moved an issue Puppet / PUP-6213 Puppet Accepts Strings for the "returns" Attribute of the "exec" Type Change By: Branan Riley Affects Version/s: PE 3.3.1 Component/s: Platform Key: PE PUP - 5489 6213 Project: Puppet Enterprise [Internal] 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.
Jira (PUP-3885) Unhelpful error message on type file when ensure => true && content is defined
Title: Message Title Kylo Ginsberg commented on PUP-3885 Re: Unhelpful error message on type file when ensure => true && content is defined This will in effect be addressed by PUP-5265, because we intend to remove this unexpected behavior (on a major release boundary) in favor of explicit management of symlinks. Closing this as Won't Fix because I'd prefer to invest the time in making the behavior sane rather than improving the error handling (which may be tricky). 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.
Jira (PUP-6212) Puppet Accepts an Empty Array for the "returns" Attribute of the "exec" Type
Title: Message Title Branan Riley moved an issue Puppet / PUP-6212 Puppet Accepts an Empty Array for the "returns" Attribute of the "exec" Type Change By: Branan Riley Affects Version/s: PE 3.3.1 Component/s: Platform Key: PE PUP - 5490 6212 Project: Puppet Enterprise [Internal] 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.
Jira (PUP-5284) Investigate which of the 52 skipped tests in puppet/acceptance/* can be re-enabled
Title: Message Title John Duarte updated an issue Puppet / PUP-5284 Investigate which of the 52 skipped tests in puppet/acceptance/* can be re-enabled Change By: John Duarte Sprint: Client 2016-05-18 (Freeze) 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.
Jira (PUP-6211) Bad behavior of getvar() from stdlib when strict_variables is set to true
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6211 Bad behavior of getvar() from stdlib when strict_variables is set to true Change By: Henrik Lindberg Scrum Team: Modules 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.
Jira (PUP-2131) Race Condition between File/recursive directory and Exec script
Title: Message Title
Branan Riley commented on PUP-2131
Re: Race Condition between File/recursive directory and Exec script
As far as I can tell, this is fixed. We contain eval_generated resources, which means that a recursive directory is now treated essentially as a single "unit" in catalog application. Additionally, the following behaves as expected:
exec { 'env':
command => "/var/tmp/scripts/facter",
subscribe => File['/var/tmp/scripts'],
}
file { '/var/tmp/scripts':
ensure => directory,
recurse => true,
source => "/home/branan/prefix/bin",
source_permissions => use,
}
Jira (PUP-6211) Bad behavior of getvar() from stdlib when strict_variables is set to true
Title: Message Title
Francois Lafont created an issue
Puppet / PUP-6211
Bad behavior of getvar() from stdlib when strict_variables is set to true
Issue Type:
Bug
Affects Versions:
PUP 4.4.1
Assignee:
Unassigned
Created:
2016/04/21 10:39 AM
Priority:
Normal
Reporter:
Francois Lafont
I have Puppet version 4.4.1 and Puppetlabs-stdlib version 4.11.0 and, when strict_variables is set to true in puppet.conf, I have this:
~# puppet apply -e '$var = getvar("stuff::which::doesnt::exist"); notice( $var ); notice( $var =~ String[1] )'
Notice: Scope(Class[main]): class stuff::which::doesnt could not be found
Notice: Scope(Class[main]): true
Jira (PUP-4545) Too many restarts on interface changes for Fedora, RHEL, CentOS
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-4545 Too many restarts on interface changes for Fedora, RHEL, CentOS Change By: John Duarte Assignee: qa John Duarte 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.
Jira (PDB-2645) (maint) Update to latest ezbake release
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2645 (maint) Update to latest ezbake release Change By: Kenneth Barber Fix Version/s: PDB 3.2.x Issue Type: Bug Task 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.
Jira (PDB-2645) (maint) Update to latest ezbake release
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2645 (maint) Update to latest ezbake release Issue Type: Bug Assignee: Unassigned Created: 2016/04/21 10:16 AM Priority: Normal Reporter: gepetto-bot 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
Jira (PDB-2644) (maint) Update to latest ezbake release
Title: Message Title Kenneth Barber assigned an issue to Morgan Rhodes PuppetDB / PDB-2644 (maint) Update to latest ezbake release Change By: Kenneth Barber Assignee: Morgan Rhodes 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.
Jira (PDB-2644) (maint) Update to latest ezbake release
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2644 (maint) Update to latest ezbake release Issue Type: Bug Assignee: Unassigned Created: 2016/04/21 9:55 AM Priority: Normal Reporter: gepetto-bot 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
Jira (PDB-2643) improve representativeness of data produced by the benchmark tool
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2643 improve representativeness of data produced by the benchmark tool Issue Type: Improvement Assignee: Unassigned Created: 2016/04/21 9:54 AM Priority: Normal Reporter: Wyatt Alt We should be able to query the summary-stats endpoint on a couple of anonymized user datasets, then use the benchmark tool to synthesize a ~5000 node dataset from each set, query the endpoint again and get outputs that are comparable to the originals. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-2515) Notice: Run of Puppet configuration client already in progress; skipping (/var/lib/puppet/state/agent_catalog_run.lock exists)
Title: Message Title Branan Riley assigned an issue to Unassigned Puppet / PUP-2515 Notice: Run of Puppet configuration client already in progress; skipping (/var/lib/puppet/state/agent_catalog_run.lock exists) Change By: Branan Riley Assignee: Eric Sorenson 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.
Jira (NPUP-41) Implement the `type` function.
Title: Message Title Peter Huene assigned an issue to Peter Huene Native Puppet / NPUP-41 Implement the `type` function. Change By: Peter Huene Assignee: Peter Huene 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.
Jira (PUP-6138) Acceptance: pin to released version of puppet-server
Title: Message Title Branan Riley updated an issue Puppet / PUP-6138 Acceptance: pin to released version of puppet-server Change By: Branan Riley Component/s: QA 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.
Jira (PUP-5201) Enable mount tests on Solaris
Title: Message Title Branan Riley updated an issue Puppet / PUP-5201 Enable mount tests on Solaris Change By: Branan Riley Issue Type: Bug New Feature 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.
Jira (PUP-6210) Report overall status should not be noop because of only one noop resource
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6210 Report overall status should not be noop because of only one noop resource Change By: Kylo Ginsberg Scrum Team: Client Platform 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.
Jira (PUP-4891) Add code_id and related fields to report
Title: Message Title Branan Riley assigned an issue to Kylo Ginsberg We decided not to do the catalog metadata work. Yay closing tickets! Puppet / PUP-4891 Add code_id and related fields to report Change By: Branan Riley Resolution: Won't Fix Status: Open Closed 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.
Jira (PUP-6210) Report overall status should not be noop because of only one noop resource
Title: Message Title Kylo Ginsberg commented on PUP-6210 Re: Report overall status should not be noop because of only one noop resource Ping Branan Riley, Verne Lindner, as I know you've both been looking at statuses from different angles. 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.
Jira (PUP-6210) Report overall status should not be noop because of only one noop resource
Title: Message Title Fabien Malfoy created an issue Puppet / PUP-6210 Report overall status should not be noop because of only one noop resource Issue Type: Improvement Affects Versions: PUP 4.4.1 Assignee: Kylo Ginsberg Components: Catalog Application, PE Created: 2016/04/21 9:02 AM Environment: Behaviour witnessed on PE 2016.1.1 with the Puppet classroom environment VMs (puppet-training-4.1.ova and puppet-student-4.2.ova) Priority: Normal Reporter: Fabien Malfoy The enforcement of a catalog containing at least one noop resource (with the noop metaparameter) that should have been triggered will have an overall status of noop reported (and thus the associated grey icon shown, along with the relevant number of nodes increased in the radiator view of the PE Console), regardless of any other change event during the run. The report should in fact report an overall status of either
Jira (HI-511) ability to work with complex datatypes from facter
Title: Message Title Henrik Lindberg commented on HI-511 Re: ability to work with complex datatypes from facter Hiera simply does not have the required concepts that would make it possible to use all kinds of data types. Interpolation is what it is in and the result is a string by definition. Other compositional mechanisms would be required and they are very hard to express in json/yaml where all data types are already spoken for. I.e this cannot be achieved in a backwards compatible way, but can be implemented as a backend that interprets the json/yaml data differently. 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.
Jira (PDB-2642) PQL: Spike/research deactivated node handling
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-2642 PQL: Spike/research deactivated node handling Issue Type: New Feature Assignee: Unassigned Created: 2016/04/21 8:47 AM Priority: Normal Reporter: Kenneth Barber The new index endpoint introduced the capability to query any entity without requiring a particular endpoint. This decision however meant that we had to make a decision about whether for all entity types, we were going to have to decide whether we show all entities even if they are on deactivated nodes, or not. In the past however, the `resource` endpoint (and others like facts) always hid data for deactivated nodes so this seems surprising to some users. Not only that, hiding deactivated nodes doesn't even work that well in PQL without an implicit subquery across nodes. That is, the ["=", ["node","active"] true] magic doesn't have short-hand in PQL. This ticket is about deciding what to do about that. In one sense, we've discussed removing this strange concept of deactivation, or amending it to something that works for us today. In another sense, query context might decide - and one thing has been discussed is that users wanting to query from puppet itself never want to see facts or resources from deactivated nodes. I think this solution is still to be worked out, and this is what this ticket is about - creating a proposal and then deciding on an implementation to fix.
Jira (PDB-2635) implicit subquery relationship between facts and resources via certname
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2635 implicit subquery relationship between facts and resources via certname Change By: Kenneth Barber Sprint: Hopper 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.
Jira (PDB-2641) PQL: Spike/Research shorthand/sugar for specifying Type[title] syntax in some way for resource matching
Title: Message Title
Kenneth Barber created an issue
PuppetDB / PDB-2641
PQL: Spike/Research shorthand/sugar for specifying Type[title] syntax in some way for resource matching
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2016/04/21 8:41 AM
Priority:
Normal
Reporter:
Kenneth Barber
The ticket is about adding some sort of sugar to allow for Type[title] style querying of resource related data.
In dalen's old query facility, he had Type[title] as a first class way of matching resources. This is one way to fix this problem:
resources { Class[foo] }
Another way is to provide a model change that exposes the combination as a string field for matching, for example:
resources { resource = "Class[foo]" }
Jira (PDB-2636) implicit relationships for self-referencing entities on certname
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2636 implicit relationships for self-referencing entities on certname Change By: Kenneth Barber Sprint: Hopper 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.
Jira (PUP-4889) Direct Puppet Initiative
Title: Message Title Susan McNerney updated an issue Puppet / PUP-4889 Direct Puppet Initiative Change By: Susan McNerney Labels: product-priority 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.
Jira (PDB-2624) query fails when colons exist in title name /resources//
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2624 query fails when colons exist in title name /resources// Change By: Kenneth Barber Fix Version/s: PDB 4.0.2 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.
Jira (PDB-2624) query fails when colons exist in title name /resources//
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2624 query fails when colons exist in title name /resources// Change By: Wyatt Alt Story Points: 1 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.
Jira (PDB-2624) query fails when colons exist in title name /resources//
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2624 query fails when colons exist in title name /resources// Change By: Wyatt Alt Sprint: Hopper 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.
Jira (PDB-2624) query fails when colons exist in title name /resources//
Title: Message Title Dylan Cochran commented on PDB-2624 Re: query fails when colons exist in title name /resources// This also seems to affect resource type names as well: [root@esgpuppetca1 sites-enabled]>curl -G http://localhost:8080/pdb/query/v4/resources/Jhulib::App_serverError 500HTTP ERROR: 500 Problem accessing /pdb/query/v4/resources/Jhulib::App_server. Reason: java.net.URISyntaxException: Expected scheme name at index 0: ::App_server Powered by Jetty:// 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.
Jira (PUP-4545) Too many restarts on interface changes for Fedora, RHEL, CentOS
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4545 Too many restarts on interface changes for Fedora, RHEL, CentOS Change By: Kylo Ginsberg Sprint: RE 2015-07-29, RE 2015-08-26, RE 2015-09-09, RE 2016Q2 Client 2016-05-04 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.
Jira (PDB-2625) Update to raynes.fs 1.4.6
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2625 Update to raynes.fs 1.4.6 Change By: Kenneth Barber Fix Version/s: PDB 4.1.0 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.
Jira (PDB-2585) (maint) improve dotestseq macro
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2585 (maint) improve dotestseq macro Change By: Kenneth Barber Fix Version/s: PDB 4.1.0 Issue Type: Bug Task 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.
Jira (PDB-2571) The puppetdb module does not control permissions on /etc/puppetlabs/puppetdb/conf.d/puppetdb.ini
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2571 The puppetdb module does not control permissions on /etc/puppetlabs/puppetdb/conf.d/puppetdb.ini Change By: Kenneth Barber Fix Version/s: PDB module-5.1.3 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.
Jira (PDB-2625) Update to raynes.fs 1.4.6
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2625 Update to raynes.fs 1.4.6 Change By: Kenneth Barber Story Points: 2 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.
Jira (PDB-2527) support latest_report? as a query field on event-counts/aggregate-event-counts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2527 support latest_report? as a query field on event-counts/aggregate-event-counts Change By: Kenneth Barber Fix Version/s: PDB 4.1.0 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.
Jira (PDB-2626) (maint) Update TK version
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2626 (maint) Update TK version Change By: Kenneth Barber Issue Type: Bug Task 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.
Jira (PDB-2626) (maint) Update TK version
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-2626 (maint) Update TK version Change By: Kenneth Barber Fix Version/s: PDB 4.1.0 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.
Jira (HI-511) ability to work with complex datatypes from facter
Title: Message Title David Schmitt commented on HI-511 Re: ability to work with complex datatypes from facter Pawel Chmielinski when you put it that way, I believe the proper fix would be to enhance hiera so that it can process structured facts properly. I forwarded your feature request to the appropriate team. 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.
Jira (HI-511) ability to work with complex datatypes from facter
Title: Message Title David Schmitt updated an issue Hiera / HI-511 ability to work with complex datatypes from facter Change By: David Schmitt Summary: Allow passing stringified arrays as values ability to parameters that expect arrays work with complex datatypes from facter 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.
Jira (HI-511) Allow passing stringified arrays as values to parameters that expect arrays
Title: Message Title David Schmitt moved an issue Hiera / HI-511 Allow passing stringified arrays as values to parameters that expect arrays Change By: David Schmitt Component/s: haproxy Component/s: UX Issue Type: Improvement New Feature Key: MODULES HI - 3131 511 Project: Forge Modules Hiera 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
Jira (PDB-2628) PuppetDB Cached "trusted" fact causes puppet run's to fail with Error 400 on SERVER: Attempt to assign to a reserved variable name: 'trusted'
Title: Message Title Kenneth Barber commented on PDB-2628 Re: PuppetDB Cached "trusted" fact causes puppet run's to fail with Error 400 on SERVER: Attempt to assign to a reserved variable name: 'trusted' This problem as far as we're aware is only caused by a misconfigured routes.yaml, or misconfigured time between masters & agents which causes the master to ignore the cache and attempt to retrieve it from PuppetDB. Any case where it is trying to retrieve the facts from PDB is incorrect, which is why you are hitting this error as you have presumed. In a properly configured situation this should never happen. The key is to figure out why, and like I said its almost always one of those two reasons. Even if you remove the trusted key like you have, retrieving from PDB is still an error and will cause the master to always ignore your real facts. You state its puppet master --compile that generates the error, but what about puppet agent runs on the clients? Also, what version of Puppet is this? Double check that the routes.yaml is being read also, I often inject mistakes in routes.yaml to prove this, or strace it . The other thing to do is to ensure you have ntp running everywhere and that clock times between hosts are near identical, if there is any mistake there this will cause the master to use puppetdb because it believes the data it has received from the agent is old and fall back to PDB instead. 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.
Jira (PUP-6187) "End of File reached" error
Title: Message Title Gary Richards commented on PUP-6187 Re: "End of File reached" error I forgot to mention. We never saw this prior to switching from apache and passenger to puppet server. I can only assume one of a few things was happening meaning that we didn't see this before: For some reason the VM's time was being updated prior to puppet creating and then caching the connection The http keepalive settings in the apache config we were using allowed the connections to persist for a longer period than they do now with puppet server. 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.
Jira (PUP-6187) "End of File reached" error
Title: Message Title Gary Richards commented on PUP-6187 Re: "End of File reached" error So, since realising 'I do see that the client changes its time at some point after it does an apt-get update and starts installing packages.', I investigated that further. It turns out our KVM backed VMs were being configured with:This meant that on boot our VMs had a hwclock set to the local time of the KVM host (in our instance, BST). One of the first things that happens on our VMs is that ntp (or ntpdate) works out that the machine is almost 3600 seconds out and tries to correct it. From what I can tell, this sometimes didn't seem to change the clock of the VM immediately, instead waiting a number of minutes until right in the middle of the puppet run the time would change. In turn, I believe this confused the pooling code in puppet client. If a connection was added to the pool with an expire time before the time of the machine was updated, the pooling code would think that the connection was valid for a much longer time than originally planned (in our instance 1 hour more) because the check in the puppet code does this: def active_sessions(site) now = Time.now sessions = @pool[site] || [] sessions.select do |session|
Jira (PUP-6209) puppetlabs-release-6-12.noarch.rpm is not signed
Title: Message Title Daniel Townend created an issue Puppet / PUP-6209 puppetlabs-release-6-12.noarch.rpm is not signed Issue Type: Bug Assignee: Unassigned Created: 2016/04/21 1:54 AM Environment: Centos Priority: Normal Reporter: Daniel Townend Hi, We seem to be having problems upgrading puppet on our centos servers. Its saying the update package (6.12) is not signed when I try to update it. "Package puppetlabs-release-6-12.noarch.rpm is not signed" Using the following repo, rpm -ivh https://yum.puppetlabs.com/puppetlabs-release-el-6.noarch.rpm Add Comment
Jira (PUP-6208) Invalid byte sequence in US-ASCII on gem install
Title: Message Title Hugo Freire created an issue Puppet / PUP-6208 Invalid byte sequence in US-ASCII on gem install Issue Type: Bug Assignee: Unassigned Created: 2016/04/21 12:45 AM Labels: gem Priority: Major Reporter: Hugo Freire Using Package provider Gem to install bundler-1.2.5 results on "Invalid byte sequence in US-ASCII". The locale in my machine is correct, en_GB.UTF-8, but when the execute the gem install, puppet changes it to US-ASCII, and fails with the "Invalid byte sequence..." I have found that puppet overrides locales in util execution, but you can skip it by setting "override_locale". I not found any way to pass this. Removing this lines works perfectly. https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/execution.rb#L265 if (options[:override_locale]) then # loop over them and clear them
