Jira (PUP-6336) Quoted string "undef" treated as value undef
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6336
Quoted string "undef" treated as value undef
Change By:
Henrik Lindberg
Scope Change Category:
Found
Scope Change Reason:
Blocker for 4.5.0 - causes commonly used module(s) to fail
Acceptance Criteria:
That {{notice 'undef'}} in puppet is noticed as a string when running on puppetserver (as well as on MRI)
Story Points:
1
Release Notes Summary:
A regression was found that caused 'undef' to be equal to a literal undef when running on JRuby. This in turn is caused in what appears to be a discrepancy in the implementations of String and Symbol in MRI vs. JRuby.Users writing Ruby code should be aware that String == Symbol is different than Symbol == String and that the safe way to make such comparisons until discrepancies are solved (or before Puppet 5.0.0) should compare symbols using {{:undef.equal?(x)}} rather than {{:undef == x}} (which will fail), and {{x == :undef}} (since that triggers a slower code path on JRuby).
Sprint:
Language 2016-06-01
Scrum Team:
Language
Jira (PUP-6336) Quoted string "undef" treated as value undef
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6336 Quoted string "undef" treated as value undef Change By: Henrik Lindberg Environment: Debian 8 (jessie) 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-6336) Quoted string "undef" treated as value undef
Title: Message Title Henrik Lindberg commented on PUP-6336 Re: Quoted string "undef" treated as value undef Merged to stable: e5b9131 (after thumbs up from Matthaus Owens and Kylo Ginsberg - and then merged to master. 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-6336) Quoted string "undef" treated as value undef
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6336 Quoted string "undef" treated as value undef Change By: Henrik Lindberg Fix Version/s: PUP 4.5.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 (PUP-6336) Quoted string "undef" treated as value undef
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6336 Quoted string "undef" treated as value undef Change By: Henrik Lindberg Priority: Critical Blocker 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-6336) Quoted string "undef" treated as value undef
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6336 Quoted string "undef" treated as value undef Change By: Henrik Lindberg Priority: Normal Critical 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-6336) Quoted string "undef" treated as value undef
Title: Message Title Henrik Lindberg commented on PUP-6336 Re: Quoted string "undef" treated as value undef A PR is up https://github.com/puppetlabs/puppet/pull/4981 This PR also includes a unit test of the consequences of the monkey patch. Apparently the == operator on String is the only affected operation. The String#.eql?, String#.equal? methods are unaffected. The test for == is therefore made pending subject to running on JRuby. 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-6336) Quoted string "undef" treated as value undef
Title: Message Title Henrik Lindberg commented on PUP-6336 Re: Quoted string "undef" treated as value undef We concluded that the JRuby implementation is different from MRI in that the == operator uses <=> which makes every == against a String on JRuby run into the monkey patch. It would be interesting to know if this is changed behaviour in JRuby (it should not have implemented == that way since MRI does not do it that way). We are between a rock and a hard place here. We can fix the regression that was caused by the found commit by using :under.equal? as that works on both JRuby and MRI. JRuby's behaviour is however alarming as it could potentially be the source of "lots of trouble". We should never have done the insane thing of monkeypatching String <=> so it equates to Symbol (it will be removed in Puppet 5.0.0). But if we remove that in 4.x then we break API without warning, We can also report the incompatibility to JRuby. 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-6336) Quoted string "undef" treated as value undef
Title: Message Title Matthaus Owens commented on PUP-6336 Re: Quoted string "undef" treated as value undef Here is a simple test. puts "undef" == :undef puts :undef == "undef" puts "requiring puppet now" require 'puppet' puts "undef" == :undef puts :undef == "undef" On jruby 1.7.20, it returns... false false requiring
Jira (PUP-6257) Add --allow-authorization-extensions to puppet cert sign
Title: Message Title Nathaniel Smith updated an issue Puppet / PUP-6257 Add --allow-authorization-extensions to puppet cert sign Change By: Nathaniel Smith In Scope* Support a new flag in the "puppet cert sign" tool, "--allow-authorization-extensions"* Determine if a cert given to "puppet cert sign" has any extensions under the puppet.1.3 OID arc* Fail the signing unless the --allow-authorization-extensions flag is present* Audit the cert-related tools in puppet to see if any need to be updated with respect to this work; ca, certificate, certificate-request, certificate-revocation-list. Hopefully they don't need to be updated.* Update the internal signing policy in the ruby CA code to allow the new puppet.3 arc (in certificate_authority.rb:323 in puppet) * Update clojure CA code to respect new arc Out of Scope* Worrying about any extensions other than those under puppet.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 (PUP-6257) Add --allow-authorization-extensions to puppet cert sign
Title: Message Title Nathaniel Smith updated an issue Puppet / PUP-6257 Add --allow-authorization-extensions to puppet cert sign Change By: Nathaniel Smith In Scope* Support a new flag in the "puppet cert sign" tool, "--allow-authorization-extensions"* Determine if a cert given to "puppet cert sign" has any extensions under the puppet.1.3 OID arc* Fail the signing unless the --allow-authorization-extensions flag is present* Audit the cert-related tools in puppet to see if any need to be updated with respect to this work; ca, certificate, certificate-request, certificate-revocation-list. Hopefully they don't need to be updated. * Update the internal signing policy in the ruby CA code to allow the new puppet.3 arc (in certificate_authority.rb:323 in puppet) Out of Scope* Worrying about any extensions other than those under puppet.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 (PUP-6258) Update Puppet OID lists to add new authorized extensions
Title: Message Title Nathaniel Smith updated an issue Puppet / PUP-6258 Update Puppet OID lists to add new authorized extensions Change By: Nathaniel Smith The point of this ticket is to define a new OID arc that can be used to guard cert signing in such a way that makes using x509 extensions safe for use in PE tk-auth rules (see SERVER-1305 for a more in-depth motivation).The new arc is puppet.3, short-named ppAuthExt. Two new OIDs will be added: pp_authorization and pp_auth_role.The former is essentially intended for use as a flag that extensions from other arcs can be trusted on a given certificate. The latter is a convenience extension that duplicates the pp_role extension but with implied authorization.In Scope* Add new extensions to puppet's oids.rb* Add new extensions to Clojure CAOut of Scope* Functional changes anywhere * Allowing the ruby CA or the clojure CA to actually respect these certs (that's in PUP-6257) New extensions1.3.6.1.4.1.34380.1.3.1 pp_authorization1.3.6.1.4.1.34380.1.3.13 pp_auth_role 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-2729) REST API ignores data after AST query
Title: Message Title Daniel Parks commented on PDB-2729 Re: REST API ignores data after AST query Yeah, something like 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-6336) Quoted string "undef" treated as value undef
Title: Message Title Henrik Lindberg commented on PUP-6336 Re: Quoted string "undef" treated as value undef User reported this in bug report against logrotate: sorry, had to downgrade puppet agent as well to fix it it works with 4.4.2 (agent 1.4.2 and server 2.3.2) it breaks with 4.5 (agent 1.5.0 and server 2.4.0) So - somewhat inconclusive where the problem is. The odd thing is that a notice (running server side) shows the faulty behavior under puppetserver. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6336) Quoted string "undef" treated as value undef
Title: Message Title Matthaus Owens commented on PUP-6336 Re: Quoted string "undef" treated as value undef A git bisect shows that https://github.com/puppetlabs/puppet/commit/1547756ad7caa5cb1f0add8161e51ac07f61bd67 is the commit that caused this. 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-6336) Quoted string "undef" treated as value undef
Title: Message Title Chris Price commented on PUP-6336 Re: Quoted string "undef" treated as value undef Matthaus Owens you already bisected this under Puppet Server and determined that the behavior was different between Puppet 4.4.x and Puppet 4.5, correct? If so, then, Henrik Lindberg, it seems like you guys may need to spin it up under Puppet Server to debug? 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-6336) Quoted string "undef" treated as value undef
Title: Message Title Henrik Lindberg commented on PUP-6336 Re: Quoted string "undef" treated as value undef My output is on webrick - "simplest" (old-school) test to see if it is parser/evaluator/compiler vs. something else. Ping Chris Price - looks like something puppetserver related, or something that puppetlabs-logrotate does when running 4.5.0 with puppetserver. 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-6336) Quoted string "undef" treated as value undef
Title: Message Title Matthaus Owens commented on PUP-6336 Re: Quoted string "undef" treated as value undef This is still broken on stable with the fix for PUP-6321. Henrik Lindberg was your above output using apply or a master/agent? 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-6336) Quoted string "undef" treated as value undef
Title: Message Title Henrik Lindberg commented on PUP-6336 Re: Quoted string "undef" treated as value undef The problem could be related to PUP-6321 if the resource in question is using autorequire. The fix for PUP-6321 is in on both master (for 4.6.0) and stable (for 4.5.1) branches. If possible, test running from source. I ran the test in the previous example from source using commands as shown here: https://gist.github.com/hlindberg/6d956df8ab2e08f24b07d94c0b337a3a 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-6258) Update Puppet OID lists to add new authorized extensions
Title: Message Title
Nathaniel Smith commented on PUP-6258
Re: Update Puppet OID lists to add new authorized extensions
Chris Barker, Reid Vandewiele, I wanted to let you know what I was going with for the first pass on the puppet.3 OID arc – just two extensions for now, with the understanding that the presence of one of them essentially "blesses" use of extensions from ppRegExt and ppPrivExt. I'm still adding pp_auth_role as a convenience, though (so rules can just look for {extensions: {pp_auth_role: "mom"}} instead of {extensions: {pp_authorization: true, pp_role: "mom"}}).
If either of you have reservations about this, let me know.
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-6258) Update Puppet OID lists to add new authorized extensions
Title: Message Title Nathaniel Smith updated an issue Puppet / PUP-6258 Update Puppet OID lists to add new authorized extensions Change By: Nathaniel Smith The point of this ticket is to define a new OID arc that can be used to guard cert signing in such a way that makes using x509 extensions safe for use in PE tk-auth rules (see SERVER-1305 for a more in-depth motivation).The new arc is puppet.3, short-named ppAuthExt. Two new OIDs will be added: pp_authorization and pp_auth_role.The former is essentially intended for use as a flag that extensions from other arcs can be trusted on a given certificate. The latter is a convenience extension that duplicates the pp_role extension but with implied authorization. In Scope* Add new extensions to puppet's oids.rb* Add new extensions to Clojure CAOut of Scope* Functional changes anywhereNew extensions1.3.6.1.4.1.34380.1.3. 13 pp_auth_role 1 .3.6.1.4.1.34380.1.3.25 pp_auth_hostname pp_authorization 1.3.6.1.4.1.34380.1.3. 9 pp_auth_service 13 pp_auth_role 1.3.6.1.4.1.34380.1.3.12 pp_auth_environment1.3.6.1.4.1.34380.1.3.21 pp_auth_network1.3.6.1.4.1.34380.1.3.19 pp_auth_datacenter1.3.6.1.4.1.34380.1.3.23 pp_auth_cloudplatform 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-6336) Quoted string "undef" treated as value undef
Title: Message Title
Henrik Lindberg commented on PUP-6336
Re: Quoted string "undef" treated as value undef
On the tag 4.5.0 I can not recreate this error with an agent -t using the reproducer.
# cat site.pp
henrik$ cat site.pp
node default {
$var1 = undef
$var2 = "undef"
$var3 = 'undef'
$var4 = "'undef'"
$var5 = '"undef"'
notify { "VAR1: ${var1} VAR2: ${var2} VAR3: ${var3} VAR4: ${var4} VAR5: ${var5}": }
notice("VAR1: ${var1} VAR2: ${var2} VAR3: ${var3} VAR4: ${var4} VAR5: ${var5}")
Jira (PUP-6334) ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x)
Title: Message Title
William Hopper commented on PUP-6334
Re: ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x)
Brian Conner this is the result of a change we made to fix issues between the systemd / sysvinit providers on newer EL systems.
Is there a reason you explicitly want to use the init provider here? On CentOS, the RedHat provider is the default, and correct, provider to manage sysvinit services:
[root@c9fqwnzfo8xif3a ~]# puppet resource service iptables --param provider
service { 'iptables':
ensure => 'running',
enable => 'false',
provider => 'redhat',
}
In Puppet 4.4.1, if you specifically ask for the init provider, you lose the ability to manage the enable state of the service, but using the redhat provider as intended, this works correctly:
[root@gpnyys3cfeaiogh ~]# puppet resource service iptables provider=init --param provider
Jira (PUP-6336) Quoted string "undef" treated as value undef
Title: Message Title Henrik Lindberg commented on PUP-6336 Re: Quoted string "undef" treated as value undef Matthaus Owens The apply run is different in that is re-using what was created during compilation in terms of loaded types. I can confirm that the same does not trigger the problem on a puppet apply on 4.5.0 - and there no difference after PUP-6321 is applied when running apply. 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-6334) ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x)
Title: Message Title Michael Smith commented on PUP-6334 Re: ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x) This was caused by https://github.com/puppetlabs/puppet/commit/d7470152d0b1c71f393e36475d5982078cc12a24. The Init provider didn't behave correctly, it's recommended to use the RedHat provider instead. This does seem like it became a breaking change... I'm not sure if that could've been avoided. 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-6334) ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x)
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6334 ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x) Ping Kylo Ginsberg Change By: Henrik Lindberg 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 (PDB-2703) (maint) Make PE_VER configurable
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2703 (maint) Make PE_VER configurable Change By: Ryan Senior 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-2702) (maint) Add example config file for running PDB and RBAC together
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2702 (maint) Add example config file for running PDB and RBAC together Change By: Ryan Senior 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-2686) (maint) bump kitchensink to 1.3.1
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2686 (maint) bump kitchensink to 1.3.1 Change By: Ryan Senior 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-2725) (MAINT) Bump testing timeouts to deal with slow infra
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2725 (MAINT) Bump testing timeouts to deal with slow infra Change By: Ryan Senior 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-6088) Make TypeParser#interpret public API for Puppet Strings use
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-6088 Make TypeParser#interpret public API for Puppet Strings use Change By: Sean Griffin Status: Ready for CI Test Assignee: 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-6321) undef in custom type autorequire value causes error in Puppet 4.5.0
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-6321 undef in custom type autorequire value causes error in Puppet 4.5.0 Change By: Sean Griffin Status: Ready for CI Test Assignee: 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 (PDB-2729) REST API ignores data after AST query
Title: Message Title Andrew Roetker commented on PDB-2729 Re: REST API ignores data after AST query So the specific case we're worried about is something like `[extract [certname]] [= certame foo]]` or some such 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-2729) REST API ignores data after AST query
Title: Message Title Daniel Parks created an issue PuppetDB / PDB-2729 REST API ignores data after AST query Issue Type: Bug Affects Versions: PDB 4.0.1 Assignee: Unassigned Created: 2016/05/20 1:47 PM Environment: CentOS Linux release 7.2.1511 (Core) PE 2016.1 with separate compile nodes Priority: Normal Reporter: Daniel Parks Query Result Expected ["=", "title", "dp"] found
Jira (PUP-6334) ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x)
Title: Message Title
Brian Conner updated an issue
Puppet / PUP-6334
ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x)
Change By:
Brian Conner
"Provider init is not functional on this host" is returned when executing {code}puppet resource service iptables provider=init --debug{code} in 4.5.0. Note that the Service resource is using: {code}provider => 'init',{code}.On a 4.4.2 machine, the same command returns ok. This is on CentOS 6.x , masterless puppet .
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-6178) Look for hiera.yaml in codedir first, then confdir
Title: Message Title Jean Bond updated an issue Puppet / PUP-6178 Look for hiera.yaml in codedir first, then confdir Change By: Jean Bond Labels: docs-reviewed 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-6336) Quoted string "undef" treated as value undef
Title: Message Title Daniel Urist commented on PUP-6336 Re: Quoted string "undef" treated as value undef root@dev-puppet:~# puppetserver --version puppetserver version: 2.4.0 root@dev-puppet:~# puppet --version 4.5.0 On Fri, May 20, 2016 at 1:59 PM, Matthaus Owens (JIRA) < 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-6336) Quoted string "undef" treated as value undef
Title: Message Title Matthaus Owens commented on PUP-6336 Re: Quoted string "undef" treated as value undef Daniel Urist What version of puppet-agent is installed alongside your puppetserver? I presume from what I've seen that it is 1.5.0, but I'd love confirmation on 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-6316) Write up notes on Puppet Settings spike w/Kylo
Title: Message Title Chris Price assigned an issue to Chris Price Puppet / PUP-6316 Write up notes on Puppet Settings spike w/Kylo Change By: Chris Price Assignee: Chris Price 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-6337) Transient OSX test failure in should_allow_password_salt_iterations_osx.rb
Title: Message Title William Hopper created an issue Puppet / PUP-6337 Transient OSX test failure in should_allow_password_salt_iterations_osx.rb Issue Type: Bug Assignee: Unassigned Created: 2016/05/20 1:01 PM Priority: Normal Reporter: William Hopper user.should_allow_password_salt_iterations_osx.rb was added as part of PUP-6159. It has passed through CI successfully several times, but it failed this morning with: * verify the password was set correctly dtnlabypt55qkbn.delivery.puppetlabs.net (osx1010-64-1) 19:15:26$ dscl /Local/Default -authonly testuser helloworld DS Error: -14090 (eDSAuthFailed)
Jira (PUP-6336) Quoted string "undef" treated as value undef
Title: Message Title Matthaus Owens commented on PUP-6336 Re: Quoted string "undef" treated as value undef Interesting that the behavior is different here between puppet apply and an agent run. 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-1423) Ubuntu tests not run on Ubuntu
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1423 Ubuntu tests not run on Ubuntu Change By: Kylo Ginsberg Release Notes: Not Needed 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-6336) Quoted string "undef" treated as value undef
Title: Message Title Matthaus Owens commented on PUP-6336 Re: Quoted string "undef" treated as value undef Eric0 Sorenson Kylo Ginsberg This looks related to PUP-6321 as it also affects undef. 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-6336) Quoted string "undef" treated as value undef
Title: Message Title Matthaus Owens moved an issue Puppet / PUP-6336 Quoted string "undef" treated as value undef Change By: Matthaus Owens Affects Version/s: SERVER 2.4.0 Affects Version/s: PUP 4.5.0 Component/s: Puppet Server Key: SERVER PUP - 1356 6336 Project: 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
Jira (PUP-6335) Puppet OID listing should be shareable between Clojure and Ruby code
Title: Message Title Nathaniel Smith updated an issue Puppet / PUP-6335 Puppet OID listing should be shareable between Clojure and Ruby code Change By: Nathaniel Smith Sub-team: jade 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-6335) Puppet OID listing should be shareable between Clojure and Ruby code
Title: Message Title Nathaniel Smith created an issue Puppet / PUP-6335 Puppet OID listing should be shareable between Clojure and Ruby code Issue Type: Improvement Assignee: Unassigned Created: 2016/05/20 12:39 PM Priority: Normal Reporter: Nathaniel Smith We currently share a copypasta list of OID -> shortname translations for puppet's OID arcs between ruby code (oids.rb in puppet) and clojure (certificate_authority.clj in puppet server). We should be storing that static mapping in a file on disk that can be read by either codebase. We already do this with the csr_attributes.yml file, but only for user-defined extensions above what we hardcode. This will require changes in both puppet and puppetserver. Add Comment
Jira (PUP-6332) Ability to mount as specific user
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-6332 Ability to mount as specific user Change By: Kylo Ginsberg Assignee: Kylo Ginsberg 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-3314) Assign new OID in registeredExtensions space for 'pp_role'
Title: Message Title Nathaniel Smith commented on PUP-3314 Re: Assign new OID in registeredExtensions space for 'pp_role' Eric0 Sorenson I'm reviewing tickets that mention OIDs and noticed this one. We have pp_role (and I'm about to add it to the new OID arc as well). Can I close this as fixed? 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-1428) FreeBSD facts are missing from Facter 3.X onwards
Title: Message Title Peter Souter commented on FACT-1428 Re: FreeBSD facts are missing from Facter 3.X onwards So thanks to the work by Jasper Lievisse Adriaanse for OpenBSD, there's already a lot of prior knowledge on BSD internals. Not 1:1 obviously, but a lot can be used in FreeBSD Right now I'm playing with importing all the OpenBSD in the FreeBSD builds, and seeing what breaks. Long term, it would be nice to refactor the OpenBSD work into common classes and import into FreeBSD 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-1428) FreeBSD facts are missing from Facter 3.X onwards
Title: Message Title Dylan Cochran commented on FACT-1428 Re: FreeBSD facts are missing from Facter 3.X onwards Just to keep my sanity, I'm going to list where the information lives; so if I get time to work on it I just have to transcribe: bios_release_date = kenv -q smbios.bios.reldate bios_vendor = kenv -q smbios.bios.vendor bios_version = kenv -q smbios.bios.version boardmanufacturer = kenv -q smbios.planar.maker boardproductname = kenv -q smbios.planar.product boardserialnumber = kenv -q smbios.planar.serial serialnumber = kenv -q smbios.system.serial productname = kenv -q smbios.system.product manufacturer = kenv -q smbios.system.maker 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-1428) FreeBSD facts are missing from Facter 3.X onwards
Title: Message Title Peter Souter updated an issue Facter / FACT-1428 FreeBSD facts are missing from Facter 3.X onwards Change By: Peter Souter Affects Version/s: FACT 3.0.0 Affects Version/s: FACT 3.1.0 Affects Version/s: FACT 3.1.7 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-1428) FreeBSD facts are missing from Facter 3.X onwards
Title: Message Title
Peter Souter commented on FACT-1428
Re: FreeBSD facts are missing from Facter 3.X onwards
Output from Debug attached, but there's nothing there?
#!/bin/bash
array=( architecture augeasversion augeasversion bios_release_date bios_vendor bios_version boardmanufacturer boardproductname boardserialnumber domain fqdn gid gid hardwareisa hardwaremodel hostname id interfaces ipaddress ipaddress_em0 ipaddress_lo0 ipaddress_re0 is_virtual macaddress macaddress_em0 macaddress_re0 macaddress_xl0 manufacturer memoryfree memoryfree_mb memorysize memorysize_mb mtu_em0 mtu_lo0 mtu_re0 mtu_xl0 netmask netmask_em0 netmask_lo0 netmask_re0 network_em0 network_lo0 network_re0 osfamily processor processorcount processors productname ps puppetversion rubyplatform rubysitedir rubyversion serialnumber sshdsakey sshecdsakey sshed25519key sshfp_dsa sshfp_ecdsa sshfp_ed25519 sshfp_rsa sshrsakey swapfree swapsize type uptime uptime_days uptime_hours uptime_seconds uuid virtual zfs_version zpool_version )
for i in "${array[@]}"
do
facter -p $i --debug
done
Jira (FACT-1428) FreeBSD facts are missing from Facter 3.X onwards
Title: Message Title Peter Souter updated an issue Facter / FACT-1428 FreeBSD facts are missing from Facter 3.X onwards Change By: Peter Souter Some are kinda expected, some are pretty worrying (no FQDN? :[ ) architectureaugeasversion augeasversion bios_release_datebios_vendorbios_versionboardmanufacturerboardproductnameboardserialnumberdomainfqdngid gid hardwareisahardwaremodelhostnameidinterfacesipaddressipaddress_em0ipaddress_lo0ipaddress_re0is_virtualmacaddressmacaddress_em0macaddress_re0macaddress_xl0manufacturermemoryfreememoryfree_mbmemorysizememorysize_mbmtu_em0mtu_lo0mtu_re0mtu_xl0netmasknetmask_em0netmask_lo0netmask_re0network_em0network_lo0network_re0 operatingsystemoperatingsystemmajreleaseoperatingsystemrelease osfamilyprocessorprocessorcountprocessorsproductnamepspuppetversionrubyplatformrubysitedirrubyversionserialnumbersshdsakeysshecdsakeysshed25519keysshfp_dsasshfp_ecdsasshfp_ed25519sshfp_rsasshrsakeyswapfree swapfree_mb swapsize swapsize_mb typeuptimeuptime_daysuptime_hoursuptime_secondsuuidvirtualzfs_versionzpool_version 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-1428) FreeBSD facts are missing from Facter 3.X onwards
Title: Message Title Peter Souter created an issue Facter / FACT-1428 FreeBSD facts are missing from Facter 3.X onwards Issue Type: Bug Assignee: Unassigned Created: 2016/05/20 11:24 AM Labels: freebsd Priority: Normal Reporter: Peter Souter Some are kinda expected, some are pretty worrying (no FQDN? :[ ) architecture augeasversion bios_release_date bios_vendor bios_version boardmanufacturer boardproductname boardserialnumber domain fqdn gid hardwareisa hardwaremodel hostname id interfaces ipaddress ipaddress_em0 ipaddress_lo0 ipaddress_re0 is_virtual macaddress macaddress_em0 macaddress_re0 macaddress_xl0 manufacturer memoryfree memoryfree_mb memorysize memorysize_mb mtu_em0 mtu_lo0 mtu_re0 mtu_xl0 netmask netmask_em0 netmask_lo0 netmask_re0 network_em0 network_lo0 network_re0 operatingsystem operatingsystemmajrelease operatingsystemrelease osfamily processor processorcount processors productname ps puppetversion rubyplatform rubysitedir rubyversion serialnumber sshdsakey sshecdsakey sshed25519key sshfp_dsa sshfp_ecdsa sshfp_ed25519 sshfp_rsa sshrsakey swapfree swapfree_mb swapsize swapsize_mb type uptime uptime_days uptime_hours uptime_seconds uuid virtual zfs_version zpool_version
Jira (PUP-6334) ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x)
Title: Message Title
Roan O'Sullivan updated an issue
Puppet / PUP-6334
ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x)
Change By:
Roan O'Sullivan
"Provider init is not functional on this host" is returned when executing {code}puppet resource service iptables provider=init --debug{code} in 4.5.0. This class Note that the Service resource is using: {code} provider => 'init', {code}. On a 4.4.2 machine, the same command returns ok. This is on CentOS 6.x.
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-6334) ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x)
Title: Message Title
Roan O'Sullivan updated an issue
Puppet / PUP-6334
ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x)
Change By:
Roan O'Sullivan
"Provider init is not functional on this host" is returned when executing {code} puppet resource service iptables provider=init --debug {code} in 4.5.0. This class is using:provider => 'init', On a 4.4.2 machine, the same command returns ok. This is on CentOS 6.x.
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-6334) ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x)
Title: Message Title Brian Conner updated an issue Puppet / PUP-6334 ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x) Change By: Brian Conner "Provider init is not functional on this host" is returned when executing puppet resource service cphalod iptables provider=init --debug in 4.5.0. This class is using:provider => 'init', On a 4.4.2 machine, the same command returns ok. This is on CentOS 6.x. 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-6334) ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x)
Title: Message Title Brian Conner created an issue Puppet / PUP-6334 ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x) Issue Type: Bug Affects Versions: PUP 4.5.0 Assignee: Unassigned Components: Breaking Change Created: 2016/05/20 11:06 AM Fix Versions: PUP 4.4.2 Priority: Critical Reporter: Brian Conner "Provider init is not functional on this host" is returned when executing puppet resource service cphalod provider=init --debug in 4.5.0. This class is using: provider => 'init', On a 4.4.2 machine, the same command returns ok. This is on CentOS 6.x.
Jira (PUP-6333) Mount creates 0600 /etc/fstab
Title: Message Title Ken Stanley created an issue Puppet / PUP-6333 Mount creates 0600 /etc/fstab Issue Type: Bug Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/05/20 10:44 AM Environment: Puppet 3.8 Mac OS X Yosemite Priority: Normal Reporter: Ken Stanley When puppet creates the /etc/fstab for the mount resource, it creates it with 0600 permissions. This means only the root user can access the fstab, when it may be beneficial for other users to mount filesystems. Add Comment
Jira (PUP-6332) Ability to mount as specific user
Title: Message Title Ken Stanley created an issue Puppet / PUP-6332 Ability to mount as specific user Issue Type: New Feature Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/05/20 10:42 AM Environment: Puppet 3.8 Mac OS X Yosemite Priority: Normal Reporter: Ken Stanley Similar to the exec resource, it would be useful to run a mount operation as a specific user. In Mac OS X, for example, there is no option to pass to mount for which user owns a mount. It is based on the user running the mount command. If puppet is run as root, this means the mount is owned by root. Add Comment
Jira (PUP-6321) undef in custom type autorequire value causes error in Puppet 4.5.0
Title: Message Title Sean Griffin commented on PUP-6321 Re: undef in custom type autorequire value causes error in Puppet 4.5.0 Yes I think there was a gap. Thomas added a unit test. I'm seeing if I can figure out that the unit test would have caught it (I think yes), and therefore whether we're covered now. Ryan Gard 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-6321) undef in custom type autorequire value causes error in Puppet 4.5.0
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6321 undef in custom type autorequire value causes error in Puppet 4.5.0 Change By: Henrik Lindberg Priority: Normal Major 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 Karen Van der Veer updated an issue PuppetDB / PDB-773 Add primary keys to 'edges' and 'resource_events' Change By: Karen Van der Veer 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-6321) undef in custom type autorequire value causes error in Puppet 4.5.0
Title: Message Title Ryan Gard commented on PUP-6321 Re: undef in custom type autorequire value causes error in Puppet 4.5.0 John Duarte Sean Griffin Is this a test gap in our test automation? 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-6321) undef in custom type autorequire value causes error in Puppet 4.5.0
Title: Message Title Rajasree Talla commented on PUP-6321 Re: undef in custom type autorequire value causes error in Puppet 4.5.0 Kylo Ginsberg This bug is in normal priority now. Is that correct? Do we need a agent release before Couch goes out for this? 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-1409) Facter should continue without locales instead of aborting if they are unavailable
Title: Message Title William Hopper assigned an issue to William Hopper Facter / FACT-1409 Facter should continue without locales instead of aborting if they are unavailable Change By: William Hopper Assignee: William 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-2228) Create "examples repo" and tie that into PDB CLI manpage creation
Title: Message Title J.D. Welch assigned an issue to Unassigned PuppetDB / PDB-2228 Create "examples repo" and tie that into PDB CLI manpage creation Change By: J.D. Welch Assignee: J.D. Welch 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-2728) PostgreSQL in public schema by default - security issue
Title: Message Title Susan McNerney created an issue PuppetDB / PDB-2728 PostgreSQL in public schema by default - security issue Issue Type: Bug Assignee: Unassigned Created: 2016/05/20 9:45 AM Priority: Normal Reporter: Susan McNerney This ticket will track the PDB work to resolve this issue. Summary: By default, PostgreSQL includes a 'public' schema and a 'public' role. By default, all database users have access to the public schema. In addition to this, the public schema is included by default on all user's search paths. The result is unless the database user's search path is changed (or the user/app qualifies all operations with a schema) all tables/indexes etc get created in this public schema. Add Comment
Jira (PUP-6331) Hiera interpolations are interpreted in the data() function
Title: Message Title
Francois Lafont created an issue
Puppet / PUP-6331
Hiera interpolations are interpreted in the data() function
Issue Type:
Bug
Affects Versions:
PUP 4.5.0
Assignee:
Unassigned
Components:
Language
Created:
2016/05/20 9:11 AM
Priority:
Normal
Reporter:
Francois Lafont
Now (since 4.5.0), hiera interpolations are interpreted in the value of the data() function of a module. It wasn't the case before Puppet 4.5.0.
Is it an expected behavior?
Personally, it seems to me curious. Imho, hiera interpolations should be reserved to hiera data (in yaml files). In puppet code, I can use variables.
Here is an example. I have a module test with function as data provider. Here is my test/functions/data.pp:
function test::data {
Jira (PUP-4742) Bring semantic_puppet library into Puppet
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-4742 Bring semantic_puppet library into Puppet Change By: Henrik Lindberg Assignee: Thomas Hallgren 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-4742) Bring semantic_puppet library into Puppet
Title: Message Title Henrik Lindberg commented on PUP-4742 Re: Bring semantic_puppet library into Puppet Travis fails this on Ruby 2.3.1 with the following result: 1) Puppet::ModuleTool::Applications::Upgrader#run for an installed module that is depended upon and out of date properly upgrades to the greatest version matching the dependency Failure/Error: expect(release).not_to be_nil expected: not nil got: nil # ./spec/lib/puppet_spec/module_tool/shared_functions.rb:42:in `graph_should_include' # ./spec/unit/module_tool/applications/upgrader_spec.rb:134:in `block (6 levels) in ' # util/rspec_runner:39:in `run' # util/rspec_runner:53:in `' 2) Puppet::ModuleTool::Applications::Upgrader#run for an installed module with dependencies that are unsatisfied upgrades the module and installs the missing dependencies
Jira (PUP-6321) undef in custom type autorequire value causes error in Puppet 4.5.0
Title: Message Title Henrik Lindberg commented on PUP-6321 Re: undef in custom type autorequire value causes error in Puppet 4.5.0 Merged to stable: 2005779 and on to master 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-6088) Make TypeParser#interpret public API for Puppet Strings use
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-6088 Make TypeParser#interpret public API for Puppet Strings use Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-6088) Make TypeParser#interpret public API for Puppet Strings use
Title: Message Title Thomas Hallgren commented on PUP-6088 Re: Make TypeParser#interpret public API for Puppet Strings use Merged to master at 2bebbf2. 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-4742) Bring semantic_puppet library into Puppet
Title: Message Title Thomas Hallgren commented on PUP-4742 Re: Bring semantic_puppet library into Puppet Oh man. I'm more confused than usual today. 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-4742) Bring semantic_puppet library into Puppet
Title: Message Title Kylo Ginsberg commented on PUP-4742 Re: Bring semantic_puppet library into Puppet Thomas Hallgren your fix was for semantic-puppet at https://github.com/puppetlabs/semantic_puppet/pull/12, which was released in semantic-puppet 0.1.2, which was included as a component in the puppet-agent packages at https://github.com/puppetlabs/puppet-agent/pull/652/files, which was released in puppet-agent 1.5.0. The upshot of all that is that you should be able rely on the fix being there in semantic-puppet 0.1.2. So a variation of the current PR that references 0.1.2 (along with the other changes you mentioned above) should do the trick. 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-4742) Bring semantic_puppet library into Puppet
Title: Message Title Kylo Ginsberg assigned an issue to Thomas Hallgren Puppet / PUP-4742 Bring semantic_puppet library into Puppet Change By: Kylo Ginsberg Assignee: Jesse Scott Thomas Hallgren 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-4742) Bring semantic_puppet library into Puppet
Title: Message Title Henrik Lindberg commented on PUP-4742 Re: Bring semantic_puppet library into Puppet Thomas Hallgren The fix you submitted was to a gem (that gem is included in the Agent, the same gem IIRC, was vendored in Puppet). Naturally important to do surgery on the right limb (eh. or was it the other right). 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-4742) Bring semantic_puppet library into Puppet
Title: Message Title Thomas Hallgren commented on PUP-4742 Re: Bring semantic_puppet library into Puppet I'm not sure of which gem that should be used either (IIRC, my fix was for Semantic, not SemanticPuppet, although I think Jesse Scott copied it over). Jesse Scott, Kylo Ginsberg, can you shed some light on this? 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-4742) Bring semantic_puppet library into Puppet
Title: Message Title Thomas Hallgren assigned an issue to Jesse Scott Puppet / PUP-4742 Bring semantic_puppet library into Puppet Change By: Thomas Hallgren Assignee: Thomas Hallgren Jesse Scott 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-4742) Bring semantic_puppet library into Puppet
Title: Message Title Henrik Lindberg commented on PUP-4742 Re: Bring semantic_puppet library into Puppet You can take over the PR and do the required changes - that is, if what the PR does is the right thing to do (I lost track of which semver support is named what - we want the free standing gem version, and the vendored and old impl should be deprecated / removed. The unvendoring and replacement with gem should be fine to do. The old implementation may require deprecation instead of removal. 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-6330) puppet uninstall exe resource fails on windows due to missing quotes
Title: Message Title Max Greifenstein created an issue Puppet / PUP-6330 puppet uninstall exe resource fails on windows due to missing quotes Issue Type: Bug Affects Versions: PUP 3.8.7 Assignee: Unassigned Components: Windows Created: 2016/05/20 12:23 AM Environment: Windows 8.1 client, server running on CentOS Labels: windows Priority: Normal Reporter: Max Greifenstein Uninstalling exe-packages on windows fails under the following circumstances: a) Path for uninstall .exe-file contains spaces AND b) uninstall.exe needs an argument passed to it Reason seems to be the following section of
Jira (PUP-4742) Bring semantic_puppet library into Puppet
Title: Message Title Thomas Hallgren commented on PUP-4742 Re: Bring semantic_puppet library into Puppet The PR of this ticket must be updated to also cover the addition of PSemVerType and PSemVerRangeType (PR changes ruby module Semantic to SemanticPuppet). 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-6321) undef in custom type autorequire value causes error in Puppet 4.5.0
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-6321 undef in custom type autorequire value causes error in Puppet 4.5.0 Change By: Thomas Hallgren Scope Change Category: Found Affects Version/s: PUP 4.5.0 Scope Change Reason: Regression, needs to be dealt with a.s.a.p. Fix Version/s: PUP 4.5.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
Jira (PUP-6321) undef in custom type autorequire value causes error in Puppet 4.5.0
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-6321 undef in custom type autorequire value causes error in Puppet 4.5.0 Change By: Thomas Hallgren Story Points: 1 Sprint: Language 2016-06-01 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.
