Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Wyatt Alt, thanks for your response. We already ran these requests and have responce only from the first one. puppetdb=# select count(*) from fact_values where id not in (select distinct fact_value_id from facts); count --- 42765 (1 row) puppetdb=# select count(*) from fact_paths where id not in (select path_id from fact_values); count --- 0
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage When we tried to solve this issue last time we fully removed KahaDB and scheduler directories (i think it was 19.01) and now we have no discarded directories at all (there was no of them as well). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1120) PR (163): Allow puppetdb to be configure for masterless conf - Spredzy
Title: Message Title gepetto-bot commented on PDB-1120 Re: PR (163): Allow puppetdb to be configure for masterless conf - Spredzy kbarber commented: @ajroetker we can't change the API on a non-major boundary. We'd need to create new classes or something and find some way to proxy from the old ones to the new ones to keep backwards compatibility. Having said that, we could almost start considering a 5.0 release at this point ... since we probably will need this for PDB 3.0.0 later on, however there is some complexity in just doing that right now - my concern is about the package naming really for the terminus, since that might introduce some lack of backwards compatibility with PDB 2.2.x. Maybe if this all gets too nasty we should cut a stable & master branch. This needs some more thought, and to be truly honest with you - introducing complexity like this right now is somewhat bad timing, due to the pressures we are under . But I get what you are trying to say about naming, it does make some sense to create some differently named classes. Not sure if I like the term 'consumer' however, seems very generic, I'd just say 'puppet' or something like that, since thats what its trying to manage really. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1120) PR (163): Allow puppetdb to be configure for masterless conf - Spredzy
Title: Message Title gepetto-bot commented on PDB-1120 Re: PR (163): Allow puppetdb to be configure for masterless conf - Spredzy kbarber commented: @ajroetker so ... I'd shelve your idea in a ticket. I like it, its nice, but lets try and do it for a major release and when we have the time. Mark it as a 'fix for 5.0.0' or something like that, so we know exactly when it can be worked on. I think the naming problem here isn't terrible, and most people would be forgiving if they saw it. At least we know about it . Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1130) mechanism to apply non-migration database operations across subsequent upgrades
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1130 mechanism to apply non-migration database operations across subsequent upgrades Change By: Kenneth Barber Affects Version/s: PDB 2.2.2 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1132) the events endpoint should not require a query
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1132 the events endpoint should not require a query Change By: Kenneth Barber Affects Version/s: PDB 2.2.2 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-328) Hiera does not detect interpolation recursion
Title: Message Title Thomas Hallgren created an issue Hiera / HI-328 Hiera does not detect interpolation recursion Issue Type: Bug Assignee: Unassigned Created: 2015/01/26 3:31 AM Priority: Normal Reporter: Thomas Hallgren Hiera data that contains this: foo: '%{hiera("bar")}' bar: '%{hiera("foo")}' will result in:
Jira (PUP-3910) puppet agent: RUNTIME_ERROR during certificate creation
Title: Message Title Wolfgang Hotwagner created an issue Puppet / PUP-3910 puppet agent: RUNTIME_ERROR during certificate creation Issue Type: Bug Affects Versions: PUP 3.7.3 Assignee: Kylo Ginsberg Components: Client Created: 2015/01/26 3:53 AM Environment: Linux: Debian Stable(Wheezy) amd64 Used Repository: Puppetlabs products deb http://apt.puppetlabs.com wheezy main deb-src http://apt.puppetlabs.com wheezy main Puppetlabs dependencies deb http://apt.puppetlabs.com wheezy dependencies deb-src http://apt.puppetlabs.com wheezy dependencies Priority: Normal Reporter: Wolfgang Hotwagner
Jira (PUP-3911) Ignored included dependencies due to interpretation order
Title: Message Title David Barbion created an issue Puppet / PUP-3911 Ignored included dependencies due to interpretation order Issue Type: Bug Affects Versions: PUP 3.6.2 Assignee: Unassigned Components: Language Created: 2015/01/26 5:41 AM Environment: RHEL6, 7 MacOs X Priority: Normal Reporter: David Barbion Hello, We are massively using tags to provision servers (production and development) to restrict catalog to a sub-part. We found a strange behaviour when mixing the use of tags, include directive and definitions: class do_not_ignore_me {
Jira (PUP-3911) Ignored included dependencies due to interpretation order
Title: Message Title Mathieu BONIFACE updated an issue Puppet / PUP-3911 Ignored included dependencies due to interpretation order Change By: Mathieu BONIFACE Hello,We are massively using tags to provision servers (production and development) to restrict catalog to a sub-part.We found a strange behaviour when mixing the use of tags, include directive and definitions:{code :puppet } class do_not_ignore_me {notify { 'This message should always be displayed' :} } define foobar($message = '') {notify { $message :}include do_not_ignore_me } class foo {foobar { 'from_foo' : message => $name} } class bar {foobar { 'from_bar' : message => $name} } include foo include bar{code}When we try to apply this catalog, using the following command:{code}puppet apply foobar.pp --tags foo{code}we get this output:{code}Notice: Compiled catalog for my-wks in environment production in 0.03 secondsNotice: fooNotice: /Stage[main]/Foo/Foobar[from_foo]/Notify[foo]/message: defined 'message' as 'foo'Notice: This message should always be displayedNotice: /Stage[main]/Do_not_ignore_me/Notify[This message should always be displayed]/message: defined 'message' as 'This message should always be displayed'Notice: Finished catalog run in 0.05 seconds{code}And when we switch the last 2 lines, we get a different result, still with the same command:{code}Notice: Compiled catalog for my-wks in environment production in 0.03 secondsNotice: fooNotice: /Stage[main]/Foo/Foobar[from_foo]/Notify[foo]/message: defined 'message' as 'foo'Notice: Finished catalog run in 0.05 seconds{code}This bug is embarassing as only a little part of the large catalog is applied.Regards. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3911) Ignored included dependencies due to interpretation order
Title: Message Title Mathieu BONIFACE updated an issue Puppet / PUP-3911 Ignored included dependencies due to interpretation order Change By: Mathieu BONIFACE Hello,We are massively using tags to provision servers (production and development) to restrict catalog to a sub-part.We found a strange behaviour when mixing the use of tags, include directive and definitions:{code:puppet} class do_not_ignore_me {notify { 'This message should always be displayed' :} } define foobar($message = '') {notify { $message :}include do_not_ignore_me } class foo {foobar { 'from_foo' : message => $name} } class bar {foobar { 'from_bar' : message => $name} } include foo include bar{code}When we try to apply this catalog, using the following command:{code :shell }puppet apply foobar.pp --tags foo{code}we get this output:{code}Notice: Compiled catalog for my-wks in environment production in 0.03 secondsNotice: fooNotice: /Stage[main]/Foo/Foobar[from_foo]/Notify[foo]/message: defined 'message' as 'foo'Notice: This message should always be displayedNotice: /Stage[main]/Do_not_ignore_me/Notify[This message should always be displayed]/message: defined 'message' as 'This message should always be displayed'Notice: Finished catalog run in 0.05 seconds{code}And when we switch the last 2 lines, we get a different result, still with the same command:{code}Notice: Compiled catalog for my-wks in environment production in 0.03 secondsNotice: fooNotice: /Stage[main]/Foo/Foobar[from_foo]/Notify[foo]/message: defined 'message' as 'foo'Notice: Finished catalog run in 0.05 seconds{code}This bug is embarassing as only a little part of the large catalog is applied.Regards. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-2689) A node can't always collect its own exported resources
Title: Message Title Iain Buclaw commented on PUP-2689 Re: A node can't always collect its own exported resources This seems to have caused a regression in my environment when upgrading from 3.5.1 to 3.6.2. node arthur { @notify { "I feel very depressed": tag => 'marvin' } Notify <| tag == 'arthur' |> } Before upgrade, Arthur never saw the notification, now Arthur does. Add Comment
Jira (HI-328) Hiera does not detect interpolation recursion
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Hiera / HI-328 Hiera does not detect interpolation recursion Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-328) Hiera does not detect interpolation recursion
Title: Message Title Thomas Hallgren updated an issue Hiera / HI-328 Hiera does not detect interpolation recursion Change By: Thomas Hallgren Sprint: Language 2015-02-04 Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-14) Allow access to structured data
Title: Message Title Thomas Hallgren updated an issue Hiera / HI-14 Allow access to structured data Change By: Thomas Hallgren Sprint: Language 2015-02-04 Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2689) A node can't always collect its own exported resources
Title: Message Title Henrik Lindberg commented on PUP-2689 Re: A node can't always collect its own exported resources Iain Buclaw Since we do not have a complete specification of how tags should work in all cases I am not sure if this is a regression, or if you are seeing the effect of a corrected bug. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2689) A node can't always collect its own exported resources
Title: Message Title Iain Buclaw commented on PUP-2689 Re: A node can't always collect its own exported resources Henrik Lindberg So not having a specification has justified a means for changing how collecting virtual resources work with tags? Given that the ramifications are pretty hefty here, I'm surprised this didn't get deterred to the next major version. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-294) Traverse hiera with a fact that returns an array
Title: Message Title Jon Shanks commented on HI-294 Re: Traverse hiera with a fact that returns an array Also, it would allow you to potentially utilise the list of classes assigned to a machine hence traversing data relevant to what is applied to a box i.e. if classes contained an array list of classes assigned to a machine, then modules could find other data for other modules within it: — :backends: yaml :hierarchy: defaults "modules/% {module_name} /%{::classes}" global So if you had a box which had jenkins + sudo modules assigned, you could drop have modules/sudo/jenkins.yaml on the machine with specific jenkins sudo rules and sudo, when it went to compile data for the module, would read the jenkins.yaml and apply the sudo rules for jenkins on the box. If you removed jenkins module, it wouldn't find it anymore. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-294) Traverse hiera with a fact that returns an array
Title: Message Title Jon Shanks commented on HI-294 Re: Traverse hiera with a fact that returns an array This woudl mean i wouldn't have to use my custom wrapper function around hiera to achieve this: https://github.com/jon-shanks/customlib Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-949) Retrieving facts that have had 'trusted' facts injected into them causes a 400 "Attempt to assign to a reserved variable name: 'trusted' on node" failure during Puppet catalog compilati
Title: Message Title Ben Ford commented on PDB-949 Re: Retrieving facts that have had 'trusted' facts injected into them causes a 400 "Attempt to assign to a reserved variable name: 'trusted' on node" failure during Puppet catalog compilation. Joshua Partlow is there any chance that the time value you mention that the master uses to set fact expiration does not include the time zone? IE, just the raw time of day? We are running into this problem in the classroom with completely synced clocks, but with the possibility that some agents are on different time zones. Ping Gabe Schuyler & Peter Souter. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2689) A node can't always collect its own exported resources
Title: Message Title Henrik Lindberg commented on PUP-2689 Re: A node can't always collect its own exported resources Iain Buclaw I was trying to say that I am sorry this bit you. The consequences of fixing what seemed like a bug to us were not understood. That was in turned caused by lack of specification. Had we understood that fixing the problem would mean that collection in general would find additional objects and that it could lead to bad results we should have deferred the fix to the next major release (4.0.0). Again, I am sorry about that. Now, what should we do about this? The fix (this ticket) was released in 3.6.2 (june 10, 2014), and we are about to release 3.7.4 (any day now) and there has been a number of releases in between. I am afraid that reverting the change will cause more pain (albeit other people's pain) than keeping it since there has been more complaints about tagging not doing what was expected (and that this ticket fixed) than there has been complaints about the consequences of fixing this problem. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3910) puppet agent: RUNTIME_ERROR during certificate creation
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3910 puppet agent: RUNTIME_ERROR during certificate creation Change By: Kylo Ginsberg If i try to create a certificate using puppet agent --server --waitforcert 60 -t, then the following error occurs: {code} Warning: Setting templatedir is deprecated. See http://links.puppetlabs.com/env-settings-deprecations (at /usr/lib/ruby/vendor_ruby/puppet/settings.rb:1139:in `issue_deprecation_warning')Error: Could not request certificate: Error 500 on SERVER: {"message":"Server Error: No such file or directory - /tmp/RackRewindableInput20150126-14275-kc4s7z.lock","issue_kind":"RUNTIME_ERROR","stacktrace":["/usr/lib/ruby/1.9.1/tempfile.rb:346:in `rmdir'","/usr/lib/ruby/1.9.1/tempfile.rb:346:in `rmdir'","/usr/lib/ruby/1.9.1/tempfile.rb:338:in `ensure in locking'","/usr/lib/ruby/1.9.1/tempfile.rb:338:in `locking'","/usr/lib/ruby/1.9.1/tempfile.rb:144:in `block in initialize'","/usr/lib/ruby/1.9.1/tmpdir.rb:133:in `create'","/usr/lib/ruby/1.9.1/tempfile.rb:134:in `initialize'","/usr/lib/ruby/vendor_ruby/phusion_passenger/utils/rewindable_input.rb:86:in `new'","/usr/lib/ruby/vendor_ruby/phusion_passenger/utils/rewindable_input.rb:86:in `make_rewindable'","/usr/lib/ruby/vendor_ruby/phusion_passenger/utils/rewindable_input.rb:30:in `read'","/usr/lib/ruby/vendor_ruby/puppet/network/http/rack/rest.rb:85:in `body'","/usr/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:55:in `process'","/usr/lib/ruby/vendor_ruby/puppet/network/http/rack.rb:21:in `call'","/usr/lib/ruby/vendor_ruby/phusion_passenger/rack/request_handler.rb:96:in `process_request'","/usr/lib/ruby/vendor_ruby/phusion_passenger/abstract_request_handler.rb:516:in `accept_and_process_next_request'","/usr/lib/ruby/vendor_ruby/phusion_passenger/abstract_request_handler.rb:274:in `main_loop'","/usr/lib/ruby/vendor_ruby/phusion_passenger/rack/application_spawner.rb:206:in `start_request_handler'","/usr/lib/ruby/vendor_ruby/phusion_passenger/rack/application_spawner.rb:171:in `block in handle_spawn_application'","/usr/lib/ruby/vendor_ruby/phusion_passenger/utils.rb:479:in `safe_fork'","/usr/lib/ruby/vendor_ruby/phusion_passenger/rack/application_spawner.rb:166:in `handle_spawn_application'","/usr/lib/ruby/vendor_ruby/phusion_passenger/abstract_server.rb:357:in `server_main_loop'","/usr/lib/ruby/vendor_ruby/phusion_passenger/abstract_server.rb:206:in `start_synchronously'","/usr/lib/ruby/vendor_ruby/phusion_passenger/abstract_server.rb:180:in `start'","/usr/lib/ruby/vendor_ruby/phusion_passenger/rack/application_spawner.rb:129:in `start'","/usr/lib/ruby/vendor_ruby/phusion_passenger/spawn_manager.rb:253:in `block (2 levels) in spawn_rack_application'","/usr/lib/ruby/vendor_ruby/phusion_passenger/abstract_server_collection.rb:132:in `lookup_or_add'","/usr/lib/ruby/vendor_ruby/phusion_passenger/spawn_manager.rb:246:in `block in spawn_rack_application'","/usr/lib/ruby/vendor_ruby/phusion_passenger/abstract_server_collection.rb:82:in `block in synchronize'",":10:in `synchronize'","/usr/lib/ruby/vendor_ruby/phusion_passenger/abstract_server_collection.rb:79:in `synchronize'","/usr/lib/ruby/vendor_ruby/phusion_passenger/spawn_manager.rb:244:in `spawn_rack_application'","/usr/lib/ruby/vendor_ruby/phusion_passenger/spawn_manager.rb:137:in `spawn_applicat
Jira (PUP-3910) puppet agent: RUNTIME_ERROR during certificate creation
Title: Message Title Kylo Ginsberg commented on PUP-3910 Re: puppet agent: RUNTIME_ERROR during certificate creation Wolfgang Hotwagner it looks like this is some kind of Rack permissions or config issue based on Server Error: No such file or directory - /tmp/RackRewindableInput20150126-14275-kc4s7z.lock. Can you narrow this down to a configuration that can be reproduced independently? Btw, you might ask on the #puppet channel or the puppet-users group as well to see if anyone else has run into this one before. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3910) puppet agent: RUNTIME_ERROR during certificate creation
Title: Message Title Kylo Ginsberg assigned an issue to Wolfgang Hotwagner Puppet / PUP-3910 puppet agent: RUNTIME_ERROR during certificate creation Change By: Kylo Ginsberg Assignee: Kylo Ginsberg Wolfgang Hotwagner Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3909) Error: /Service[servicename]: Provider upstart is not functional on this host
Title: Message Title Kylo Ginsberg assigned an issue to Maksym Polshcha Puppet / PUP-3909 Error: /Service[servicename]: Provider upstart is not functional on this host Change By: Kylo Ginsberg Assignee: Kylo Ginsberg Maksym Polshcha Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3909) Error: /Service[servicename]: Provider upstart is not functional on this host
Title: Message Title Kylo Ginsberg commented on PUP-3909 Re: Error: /Service[servicename]: Provider upstart is not functional on this host Maksym Polshcha there have been some changes in puppet/master for the upstart provider. If you're able to test from source, can you try to repro this with puppet/master? (If not, we should be releasing puppet 4.0 off of puppet/master in the next week or so, so you could try then.) Also where do you see initctl --test being invoked? /cc Scott Garman Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1135) PR (1227): (maint) eastwood linting - wkalt
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1135 PR (1227): (maint) eastwood linting - wkalt Issue Type: Task Assignee: Unassigned Created: 2015/01/26 7:28 AM Labels: github Priority: Normal Reporter: gepetto-bot (maint) eastwood linting Author: Wyatt Alt <> Company: Github ID: wkalt Pull Request 1227 Discussion Pull Request 1227 File Diff Pull Request Description I ran lein eastwood on the repo and these are the things that jumped out at me. A few docstrings after function arguments, a few places where tests weren't running as expected. (webhooks-id: 275fed14c6a462224f854587bdfc0e6e)
Jira (HI-294) Traverse hiera with a fact that returns an array
Title: Message Title Henrik Lindberg commented on HI-294 Re: Traverse hiera with a fact that returns an array In PUP-1640 we have defined a new mechanism that allows a provider of data to be specified per module and per environment in a way that does not force a user to use one particular technology for supplying the data. That mechanism will cater to the need of being able to associate the data for a module with a module and not having to update the global hierarchy. I believe that R.I.Pienaar is working on an implementation for PUP-1640 for hiera. As for "expanding the hierarchy" based on the contents of an array I see no harm in adding such a feature even if it may be a bit difficult since it means that different requests will end up with a different hierarchy (i.e. different number of levels) - something I am not sure the current implementation can deal with in a straight forward way. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-294) Traverse hiera with a fact that returns an array
Title: Message Title R.I.Pienaar commented on HI-294 Re: Traverse hiera with a fact that returns an array This feature has been requested many times: https://github.com/puppetlabs/hiera/pull/193 https://github.com/puppetlabs/hiera/pull/48 I'd like to see it implemented, but lots of to and fro in those 2 PRs Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3910) puppet agent: RUNTIME_ERROR during certificate creation
Title: Message Title Wolfgang Hotwagner commented on PUP-3910 Re: puppet agent: RUNTIME_ERROR during certificate creation My fault, I thought it is a bug of the puppet version with the actual debian package, since i have a lot of puppet-agents working. But it was actually a full disk on my puppet-server. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3911) Ignored included dependencies due to interpretation order
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3911 Ignored included dependencies due to interpretation order Change By: Henrik Lindberg Affects Version/s: PUP 3.7.3 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3911) Ignored included dependencies due to interpretation order
Title: Message Title Henrik Lindberg commented on PUP-3911 Re: Ignored included dependencies due to interpretation order Verified that problem is still present in 3.7.3 and in 4.0.0 (in the making). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3911) Ignored included dependencies due to interpretation order
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3911 Ignored included dependencies due to interpretation order Change By: Henrik Lindberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3911) Ignored included dependencies due to interpretation order
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3911 Ignored included dependencies due to interpretation order Change By: Henrik Lindberg Fix Version/s: PUP 3.7.5 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1136) communicate v4 API changes to stakeholders ahead of release
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1136 communicate v4 API changes to stakeholders ahead of release Issue Type: Task Affects Versions: PDB 2.2.2 Assignee: Unassigned Created: 2015/01/26 7:54 AM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: Wyatt Alt Since we're dropping v2 and v3 for the next release, and v4 is undergoing some changes, there is no API version in PDB 2.2.2 that matches reality in 3.0. We need to make sure other teams using PDB are aware of the changes occurring to v4 in the next release, before the release occurs. We should send out an email once we have a complete list of changes. An incomplete list is: dashes in command and API endpoint fieldnames converted to underscores reports endpoint now supplies resource events top level extract
Jira (PUP-3484) Cron hour/minute format "0-6,13-23" is not allowed
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3484 Cron hour/minute format "0-6,13-23" is not allowed Change By: Henrik Lindberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3484) Cron hour/minute format "0-6,13-23" is not allowed
Title: Message Title Henrik Lindberg assigned an issue to Kylo Ginsberg Puppet / PUP-3484 Cron hour/minute format "0-6,13-23" is not allowed Change By: Henrik Lindberg Assignee: Maksym Polshcha Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1135) PR (1227): (maint) eastwood linting - wkalt
Title: Message Title gepetto-bot commented on PDB-1135 Re: PR (1227): (maint) eastwood linting - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/462/ Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3484) Cron hour/minute format "0-6,13-23" is not allowed
Title: Message Title Kylo Ginsberg commented on PUP-3484 Re: Cron hour/minute format "0-6,13-23" is not allowed This is what the docs indicate as well: https://docs.puppetlabs.com/references/latest/type.html#cron "Note that all periodic attributes can be specified as an array of values." I think we can close this unless there's a remaining issue. Maksym Polshcha thoughts? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3894) Default license for module metadata does not match an identifier provided by SPDX
Title: Message Title Anderson Mills commented on PUP-3894 Re: Default license for module metadata does not match an identifier provided by SPDX This looks good. I also need to add a small PR to change the example in face/module/generate.rb, too. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2689) A node can't always collect its own exported resources
Title: Message Title Iain Buclaw commented on PUP-2689 Re: A node can't always collect its own exported resources I'm not sure - I've been trying to understand the nature of the change through printing debug messages from util/tagging.rb I can see that it now recursively goes through every parent resource for a match. self.tags = ['marvin', 'notify'] tags = ['arthur'] caller = /usr/lib/ruby/vendor_ruby/puppet/parser/resource.rb:200:in `tagged?', ... return = false self.tags = ['node', 'arthur', 'class'] tags = ['arthur'] caller = /usr/lib/ruby/vendor_ruby/puppet/parser/resource.rb:200:in `tagged?', /usr/lib/ruby/vendor_ruby/puppet/parser/resource.rb:200:in `tagged?', ... return = true
Jira (PUP-3082) Error in puppet module skeleton
Title: Message Title Ryan Gard commented on PUP-3082 Re: Error in puppet module skeleton Verified as fixed against Puppet at SHA 0bf24a7d58f08e8b9b67665af5c21d6f015bfa3d on master branch. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3082) Error in puppet module skeleton
Title: Message Title Ryan Gard updated an issue Puppet / PUP-3082 Error in puppet module skeleton Change By: Ryan Gard QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3894) Default license for module metadata does not match an identifier provided by SPDX
Title: Message Title Anderson Mills updated an issue Puppet / PUP-3894 Default license for module metadata does not match an identifier provided by SPDX Change By: Anderson Mills Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3894) Default license for module metadata does not match an identifier provided by SPDX
Title: Message Title Anderson Mills commented on PUP-3894 Re: Default license for module metadata does not match an identifier provided by SPDX Another PR is currently on the way, and both PRs should be included to close this ticket. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3894) Default license for module metadata does not match an identifier provided by SPDX
Title: Message Title Heidi Pio updated an issue Puppet / PUP-3894 Default license for module metadata does not match an identifier provided by SPDX Change By: Heidi Pio Sprint: CODEMGMT 2015-01-28 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3894) Default license for module metadata does not match an identifier provided by SPDX
Title: Message Title Anderson Mills updated an issue Puppet / PUP-3894 Default license for module metadata does not match an identifier provided by SPDX Change By: Anderson Mills Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3082) Error in puppet module skeleton
Title: Message Title Eric Thompson commented on PUP-3082 Re: Error in puppet module skeleton Ryan Gard sorry to be pedantic here, but how was this verified? we typically put terminal output of our manual FR in here, to enable future automation, and for general posterity. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3082) Error in puppet module skeleton
Title: Message Title Ryan Gard commented on PUP-3082 Re: Error in puppet module skeleton The issue was verified by visual inspection of the "Gemfile". Console output of commands below: [root@centos7 ~]# cd /tmp/ [root@centos7 tmp]# puppet module generate ryan-test We need to create a metadata.json file for this module. Please answer the following questions; if the question is not applicable to this module, feel free to leave it blank. Puppet uses Semantic Versioning (semver.org) to version modules. What version is this module? [0.1.0] -->
Jira (PUP-3867) puppet 3.7.4 2014-01-27 Release
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3867 puppet 3.7.4 2014-01-27 Release Change By: Kylo Ginsberg Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3168) Fix all file permissions on puppet module install
Title: Message Title Anderson Mills commented on PUP-3168 Re: Fix all file permissions on puppet module install Currently creating a new PR to address problem with user's PR, which failed review as-is and has not been changed in months. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3867) puppet 3.7.4 2014-01-27 Release
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-3867 puppet 3.7.4 2014-01-27 Release Change By: Hailee Kenney Assignee: Release Engineering Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3868) Is the code ready for release?
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-3868 Is the code ready for release? Change By: Hailee Kenney Assignee: Henrik Lindberg Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3901) Host type has unexpected behavior and is not idempotent
Title: Message Title Eli Young commented on PUP-3901 Re: Host type has unexpected behavior and is not idempotent Further complications: on Windows, you can only put 9 domains per line: C:\> type \windows\system32\drivers\etc\hosts 1.1.1.1 host alias1 alias2 alias3 alias4 alias5 alias6 alias7 alias8 alias9 C:\>ping host Pinging host [1.1.1.1] with 32 bytes of data: Control-C ^C C:\>ping alias8 Pinging host [1.1.1.1] with 32 bytes of data: Control
Jira (PUP-3867) puppet 3.7.4 2014-01-27 Release
Title: Message Title Hailee Kenney updated an issue Puppet / PUP-3867 puppet 3.7.4 2014-01-27 Release Change By: Hailee Kenney Sprint: Language 2015-02-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3168) Fix all file permissions on puppet module install
Title: Message Title Anderson Mills updated an issue Puppet / PUP-3168 Fix all file permissions on puppet module install Change By: Anderson Mills Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3168) Fix all file permissions on puppet module install
Title: Message Title Anderson Mills commented on PUP-3168 Re: Fix all file permissions on puppet module install A new PR is up for this problem (PR 3520). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3894) Default license for module metadata does not match an identifier provided by SPDX
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Puppet / PUP-3894 Default license for module metadata does not match an identifier provided by SPDX Change By: Adrien Thebo Assignee: Adrien Thebo Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3168) Fix all file permissions on puppet module install
Title: Message Title Anderson Mills assigned an issue to Adrien Thebo Puppet / PUP-3168 Fix all file permissions on puppet module install Change By: Anderson Mills Assignee: Adrien Thebo Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3897) add acceptance to ensure newly assigned node environments are picked up by agents on first run
Title: Message Title Josh Cooper commented on PUP-3897 Re: add acceptance to ensure newly assigned node environments are picked up by agents on first run Merged to master in c4343d4 Henrik Lindberg do you want to backport this change to stable for 3.7.5? or change the fix version for this ticket to 4.0? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3901) Host type has unexpected behavior and is not idempotent
Title: Message Title Eli Young commented on PUP-3901 Re: Host type has unexpected behavior and is not idempotent After doing some research, I have determined that the format of lines in a hostfile is as follows: IPcanonical-hostname[alias-hostnames] This is evidenced by the fact that, when a hostname is resolved by either gethostbyname() or getaddrinfo(), the canonical name returned by those functions is canonical-hostname. See also the Windows documentation for gethostbyname() and getaddrinfo(). Incidentally, Augeas has the same assessment. Given a hostfile of: 1.1.1.1 host alias1 alias2 Augeas parses it into this: augtool> print /files/etc/hosts /files/etc/hosts /files/etc/hosts/1 /files/etc/hosts/1/ipaddr = "1.1.1.1" /files/etc/hos
Jira (PUP-3868) Is the code ready for release?
Title: Message Title Hailee Kenney commented on PUP-3868 Re: Is the code ready for release? I confirmed that the commit we're tagging for the release (3e8e84200) has been through CI and everything is green. All the tickets that have their fix version tagged as PUP 3.7.4 have been resolved. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3869) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-3869 Is there a JIRA ticket targeted at the release for every commit? Change By: Hailee Kenney Assignee: Henrik Lindberg Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3912) Update specs to rspec 3
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Puppet / PUP-3912 Update specs to rspec 3 Change By: Kylo Ginsberg Assignee: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-298) Update FS layout for hiera
Title: Message Title Eric Sorenson commented on HI-298 Re: Update FS layout for hiera We bashed this out in a room and I have run it by a few people for validation; consensus is the hiera config file (hiera.yaml) should live alongside puppet's config, and the data directory should default to the root of the 'code' directory described in PUP-3809 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3912) Update specs to rspec 3
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3912 Update specs to rspec 3 Change By: Kylo Ginsberg Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3912) Update specs to rspec 3
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-3912 Update specs to rspec 3 Issue Type: Improvement Assignee: Unassigned Created: 2015/01/26 11:39 AM Priority: Normal Reporter: Kylo Ginsberg Rspec 3 has been out for 6 months and includes some nice new features that would be useful to leverage in puppet specs. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3912) Update specs to rspec 3
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3912 Update specs to rspec 3 Change By: Kylo Ginsberg Scrum Team: Client Platform Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-298) Update FS layout for hiera
Title: Message Title Eric Sorenson commented on HI-298 Re: Update FS layout for hiera does that Unblock it? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title Eric Sorenson commented on PUP-3809 Re: Separate code (content?) and configuration directories for AIO packaging i commented on HI-289 , but for completeness sake the hiera.yaml should live alongside puppet's config files, and its datadir should default to the root of the 'code' directory. Typical deployments have it either in the control repo root (which would man /etc/puppet/code/hieradata) or use a per-environment datadir. The latter relies on variable interpolation on the master, and would land it in /etc/puppet/code/environments/$environment/hieradata, but that is not usable for a default. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3446) CertificateError when running tests with OpenSSL >= 1.0.1i
Title: Message Title Hailee Kenney updated an issue Puppet / PUP-3446 CertificateError when running tests with OpenSSL >= 1.0.1i Change By: Hailee Kenney Fix Version/s: PUP 4.0.0 Fix Version/s: PUP 3.7.4 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-298) Update FS layout for hiera
Title: Message Title Henrik Lindberg commented on HI-298 Re: Update FS layout for hiera Eric Sorenson yes, if we do this for puppet's use of hiera only; all change is on the puppet side, and the free-standing hiera is unchanged as the AIO is all about changing settings in Puppet. Is this correct? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3912) Update specs to rspec 3
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3912 Update specs to rspec 3 Change By: Josh Cooper Sprint: Platform Client 2015-02-04 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-298) Update FS layout for hiera
Title: Message Title Henrik Lindberg commented on HI-298 Re: Update FS layout for hiera What is then really missing is the ability to override the default datadir from puppet (and that we add a setting for that in puppet). With those changes the hiera release can remain at 1.4 if I understand things correctly. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3897) add acceptance to ensure newly assigned node environments are picked up by agents on first run
Title: Message Title Henrik Lindberg commented on PUP-3897 Re: add acceptance to ensure newly assigned node environments are picked up by agents on first run Backport to 3.7.5 please (but wait for stable to be tagged first). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1137) Dujour - Simplify deployment/packaging of dujour
Title: Message Title AJ Roetker created an issue PuppetDB / PDB-1137 Dujour - Simplify deployment/packaging of dujour Issue Type: Bug Assignee: Unassigned Created: 2015/01/26 12:06 PM Labels: dujour Priority: Normal Reporter: AJ Roetker Currently Dujour packaging has fallen out of sync with the rest of the packaging for our other Clojure projects. Also OPs interaction with Dujour has traditionally been confusing. It may just be easier to deploy a jar with an init script from the github repo and have some simple monitoring cron job, but it would probably be worthwhile to simplify the deploy process to minimize upkeep. Add Comment
Jira (PUP-3912) Update specs to rspec 3
Title: Message Title Josh Cooper commented on PUP-3912 Re: Update specs to rspec 3 Merged in 75561067. When this passes, it can be moved directly to resolved. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1515 Invalid parameter provider for custom types/providers Change By: Henrik Lindberg Fix Version/s: PUP 3.7.5 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Henrik Lindberg commented on PUP-1515 Re: Invalid parameter provider for custom types/providers Reopened as a backport is wanted to 3.7.5 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-328) Hiera does not detect interpolation recursion
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-328 Hiera does not detect interpolation recursion Change By: Henrik Lindberg Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3863) hiera('some::key', undef) returns empty string
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3863 hiera('some::key', undef) returns empty string Change By: Henrik Lindberg Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3526) re-structure CA REST API
Title: Message Title Ruth Linehan commented on PUP-3526 Re: re-structure CA REST API This was merged in as 6438c7215c73e6eaffe34828fb764d672b517c32 and seems to have passed CI: https://jenkins.puppetlabs.com/job/Puppet-Packaging-Callback-master/364/. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3911) Ignored included dependencies due to interpretation order
Title: Message Title Henrik Lindberg assigned an issue to David Barbion Puppet / PUP-3911 Ignored included dependencies due to interpretation order Change By: Henrik Lindberg Assignee: Henrik Lindberg David Barbion Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3872) Merge master into stable
Title: Message Title Melissa Stone commented on PUP-3872 Re: Merge master into stable This shouldn't need to happen, since this release is a patch/bugfix of the current stable release (3.7.x). Hailee Kenney feel free to correct me, but I think this should be closed. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3911) Ignored included dependencies due to interpretation order
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3911 Ignored included dependencies due to interpretation order Change By: Henrik Lindberg Fix Version/s: PUP 3.7.5 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3911) Ignored included dependencies due to interpretation order
Title: Message Title Henrik Lindberg commented on PUP-3911 Re: Ignored included dependencies due to interpretation order Actually, this is not so strange... When foo and bar change places, the include of do_not_ignore_me happens within the context of bar. When it is again being included this is simply ignored. This may be an effect of dynamic scoping going away (which caused a lot of other mysterious side effects). Do you see this as a regression in 3.6, from some earlier release? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3911) Ignored included dependencies due to interpretation order
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-3911 Ignored included dependencies due to interpretation order Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-298) Update FS layout for hiera
Title: Message Title Justin Stoller commented on HI-298 Re: Update FS layout for hiera yes, if we do this for puppet's use of hiera only Can we please get rid of the distinction between hiera-as-used-by-puppet and hiera-used-from-the-command-line. A major bump would be a great time to merge those configs. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3911) Ignored included dependencies due to interpretation order
Title: Message Title David Barbion updated an issue Puppet / PUP-3911 Ignored included dependencies due to interpretation order Change By: David Barbion Affects Version/s: PUP 3.6.1 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3911) Ignored included dependencies due to interpretation order
Title: Message Title David Barbion commented on PUP-3911 Re: Ignored included dependencies due to interpretation order AFAIK, the older release which produces such result is 3.6.1. I will test with older release tomorrow. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3479) Windows ffi dependency fails for Ruby 2.1.3
Title: Message Title Hailee Kenney updated an issue Puppet / PUP-3479 Windows ffi dependency fails for Ruby 2.1.3 Change By: Hailee Kenney Fix Version/s: PUP 4.0.0 Fix Version/s: PUP 3.7.4 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3894) Default license for module metadata does not match an identifier provided by SPDX
Title: Message Title Anderson Mills commented on PUP-3894 Re: Default license for module metadata does not match an identifier provided by SPDX Second PR is waiting for merge. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3479) Windows ffi dependency fails for Ruby 2.1.3
Title: Message Title Hailee Kenney updated an issue Puppet / PUP-3479 Windows ffi dependency fails for Ruby 2.1.3 Change By: Hailee Kenney Fix Version/s: PUP 3.7.4 Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-799) operatingsystemmajrelease has excessive detail on AIX
Title: Message Title Chris Roddy created an issue Facter / FACT-799 operatingsystemmajrelease has excessive detail on AIX Issue Type: Bug Affects Versions: FACT 2.2.0 Assignee: Eric Sorenson Created: 2015/01/26 1:40 PM Priority: Normal Reporter: Chris Roddy On AIX, 'operatingsystemmajrelease' shows full release information down to the patchlevel. It appears to contain just the same information as 'operatingsystemrelease'. Josh Preston at DSW says this was returning the correct (shorter) info in his proof-of-concept installations on earlier versions of PE 3.x. On PE 3.7 (Facter 2.2.0) we get these results: facter operatingsystemmajrelease operatingsystemrelease operatingsystemmajrelease => 6100-07-06-1241 operatingsystemrelease => 6100-07-06-1241 facter operatingsystemmajrelease operatingsystemrelease operatingsystemmajrelease => 5300-12-04-1119 operatingsystemrelease => 5300-12-04-1119
Jira (PUP-3869) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Hailee Kenney commented on PUP-3869 Re: Is there a JIRA ticket targeted at the release for every commit? Upon running the release-inquistion script and updating the fix version for some tickets there are still a few that appear to be inconsistent (the commit does not have a matching JIRA ticket with a PUP 3.7.4 fix version): ++ Issues in Git that are not in Jira PUP-3391 1eb4d77: Plugin synced for incorrect environment while agent is resolving environment PUP-3548 5fc04ec: Fix issues from review d97d44c: Allow 4x functions to call 3x functions f158248: Extract Runtime3Converter class from Runtime3Support module The commit for PUP-3391 contains a typo and is actually a part of a fix for PUP-3591 . I will go ahead and make a note on both relevant tickets in case there is confusion in the future. The commits for PUP-3548 have actually be reverted, but since they still appear in the history they came up in the script. The ticket has a correct fix version of PUP 3.7.5. Beyond that, all the other commits have an appropriate corre
Jira (PUP-3872) Merge master into stable
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-3872 Merge master into stable Change By: Hailee Kenney Assignee: Henrik Lindberg Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3872) Merge master into stable
Title: Message Title Hailee Kenney commented on PUP-3872 Re: Merge master into stable Melissa Stone, I think you're right! I will go ahead and close this, thanks for pointing that out. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3591) Puppet does not plugin sync with the proper environment after agent attempts to resolve environment
Title: Message Title Hailee Kenney commented on PUP-3591 Re: Puppet does not plugin sync with the proper environment after agent attempts to resolve environment It's worth noting for those who may find themselves here in the future that one of the commits for this ticket contained a small typo in the ticket number. Commit 7958aa034 lists the ticket as PUP-3391 rather that PUP-3591 , but is part of a fix for this ticket. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3391) Delay puppet agent startup until after network is configured
Title: Message Title Hailee Kenney commented on PUP-3391 Re: Delay puppet agent startup until after network is configured It's worth noting for the future that there is a commit in puppet that references this ticket accidentally due to small typo. Commit 7958aa034 lists the ticket as PUP-3391, but it is really part of a fix for PUP-3591 . Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3870) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Hailee Kenney commented on PUP-3870 Re: Is there a commit for every JIRA ticket targeted at the release? Upon running the release-inquisition script, it appears that there is a JIRA ticket with a PUP 3.7.4 fix version that not have a corresponding commit: ++ Issues in Jira not found in Git PUP-3737: (Fixed) Can't Install Puppet Gem on Windows64 Bit Ruby 1.9.3 and 2.0 This issue was actually fixed in commit b9a50e5c, but since that commit covered two tickets ( PUP-3479 and PUP-3737 ), the script did not pick it up as a fix for PUP-3737 . Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Gr