Jira (HI-493) Update install.rb to install .bat files on windows
Title: Message Title Melissa Stone updated an issue Hiera / HI-493 Update install.rb to install .bat files on windows Change By: Melissa Stone Story Points: 2 1 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5718) Modify install.rb to install a puppet.bat file on windows
Title: Message Title Melissa Stone updated an issue Puppet / PUP-5718 Modify install.rb to install a puppet.bat file on windows Change By: Melissa Stone Story Points: 2 1 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1321) Install facter.bat et al on windows
Title: Message Title Melissa Stone updated an issue Facter / FACT-1321 Install facter.bat et al on windows Change By: Melissa Stone Story Points: 3 1 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5743) Puppet 3.8.5 breaks compatibility with rspec-puppet
Title: Message Title Krzysztof Suszyński commented on PUP-5743 Re: Puppet 3.8.5 breaks compatibility with rspec-puppet Yea. This should be reverted in Puppet first, I think. Provide a new API, rather then changing the current implementation. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5743) Puppet 3.8.5 breaks compatibility with rspec-puppet
Title: Message Title David Schmitt commented on PUP-5743 Re: Puppet 3.8.5 breaks compatibility with rspec-puppet PR is up at https://github.com/rodjek/rspec-puppet/pull/359 I plan to release that ASAP as 2.3.1 to mitigate the issue in the short term. I'm still running through a few validations with only this patch applied to make sure it doesn't break anything else. After firefighting we can start thinking about a proper solution, the code in the PR doesn't make me happy. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5623) Callable type should be able to describe return type
Title: Message Title
Thomas Hallgren commented on PUP-5623
Re: Callable type should be able to describe return type
In the spirit of minimizing complexity and messyness, couldn't we just refrain from being able to convert functions/methods into lambdas and instead require a wrapper? I.e. use:
$some_callable = |$msg| { Notify.new($msg) }
$some_callable('yo, this is cool')
I think it would resolve the concerns around the initializer method. It also removes the need for the extra operator. Admittedly a bit more verbose but on the other hand, I don't think this will be very common. Adding a keyword could make it more distinct:
$some_callable = lambda |$msg| { Notify.new($msg) }
HashArgsCallable is much better than CallableByName. But perhaps NamedArgsCallable is even better? That way we don't have to lock in on the Hash (the description is much more similar to a Struct).
Add Comment
Jira (PUP-5694) Create static_catalog per-environment setting
Title: Message Title William Hopper commented on PUP-5694 Re: Create static_catalog per-environment setting Functional review: looks good! [root@gqwd6sc8zt78edl puppet]# cat /etc/puppetlabs/code/environments/production/environment.conf static_catalogs=true [root@gqwd6sc8zt78edl puppet]# cat /etc/puppetlabs/code/environments/test/environment.conf [root@gqwd6sc8zt78edl puppet]# puppet config print static_catalogs --environment=production true
Jira (PUP-5617) agent stalls when connection with master is dropped
Title: Message Title Michael Smith updated an issue Puppet / PUP-5617 agent stalls when connection with master is dropped Change By: Michael Smith Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2349) High Availability Phase 3
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-2349 High Availability Phase 3 Issue Type: Epic Assignee: Unassigned Created: 2016/01/25 11:58 AM Priority: Normal Reporter: Ryan Senior Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5690) Test run the windows 10 acceptance tests
Title: Message Title Ethan Brown commented on PUP-5690 Re: Test run the windows 10 acceptance tests Due to RE-6344 (Windows 10 pro template win-10-pro-x86_64 refuses SSH connection), I have retriggered the test run in the puppet-agent ad-hoc pipeline with the template win-10-ent-x86_64 at https://jenkins.puppetlabs.com/view/puppet-agent/view/ad%20hoc/job/platform_puppet-agent_init-van-int_suite-manual-ad-hoc/61/ Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-4760) Service type should not retrieve ensure status when not needed
Title: Message Title Michael Smith commented on PUP-4760 Re: Service type should not retrieve ensure status when not needed One concern I'm still considering is that external consumers of the Puppet API may expect retrieve to give them the correct status for a service. However, I'm not sure that behavior would change. puppet resource uses https://github.com/puppetlabs/puppet/blob/3.x/lib/puppet/indirector/resource/ral.rb#L13-L32 to query resource status. I suspect any user would do something similar. In both find - corresponding to a specific query like puppet resource service com.puppetlabs.puppet - and search - puppet resource service --param enabled - the ensure property is specifically included. For find this happens due to the :audit property, for search because instances queries all properties explicitly (https://github.com/puppetlabs/puppet/blob/3.x/lib/puppet/type.rb#L1159). I'd be more comfortable doing this in a minor release than bug fix, since it's so core and it's marked improvement (not bug). That would mean a 4.4 or 4.5 release (and 3.9?). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-16) Refactor command line options to support commands
Title: Message Title Peter Huene created an issue Native Puppet / NPUP-16 Refactor command line options to support commands Issue Type: Improvement Assignee: Unassigned Created: 2016/01/25 11:19 AM Priority: Normal Reporter: Peter Huene The native compiler needs to support more commands than simply "compiling" a catalog for an environment. The proposed syntax: puppetcpp [command] Where the "command" will default to "compile" with the existing behavior. Initially there will be two commands: "compile" and "parse". The latter will be new functionality that generates parsed and validated AST files (specific format TBD, but YAML output is sufficient for initial work).
Jira (NPUP-15) Refactor operator dispatch to use Puppet type signatures
Title: Message Title Peter Huene updated an issue Native Puppet / NPUP-15 Refactor operator dispatch to use Puppet type signatures Change By: Peter Huene Scope Change Category: Adopted Scope Change Reason: Bandwidth and much needed refactoring of native compiler internals Sprint: Language Triage 2016-01-27 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5356) Nagios extension check_puppet.rb error
Title: Message Title Michael Smith commented on PUP-5356 Re: Nagios extension check_puppet.rb error This looks like it needs a backport of https://github.com/puppetlabs/puppet/commit/8bede02e59cb5f6bf0bad7803bce669018f1b46e to the 3.x branch. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2332) Benchmark does not POST command version
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2332 Benchmark does not POST command version Change By: Wyatt Alt Scope Change Category: Adopted Scope Change Reason: other things are currently blocked and this is really annoying Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2208) simultaneously restarting PDB instances during an initial sync can lead to bad outcomes
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2208 simultaneously restarting PDB instances during an initial sync can lead to bad outcomes Change By: Ryan Senior Sprint: PuppetDB 2016-02-10 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5743) Puppet 3.8.5 breaks compatibility with rspec-puppet
Title: Message Title Krzysztof Suszyński commented on PUP-5743 Re: Puppet 3.8.5 breaks compatibility with rspec-puppet Yup. I can imagine this error was not intentional by Puppetlabs team and that releasing puppet is kind a big deal. I think that we need a better tests compliance suites for Puppet. There were many errors before in depending test harness (rpsec-puppet, beaker). I think this deserves better test suites. And better API for test tools i think. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5726) Non-English values for USERNAME and USERPROFILE causes multiple home directories to be created
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5726 Non-English values for USERNAME and USERPROFILE causes multiple home directories to be created Change By: Ethan Brown Fix Version/s: PUP 4.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5728) Change default parsing of manifest files to UTF-8
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5728 Change default parsing of manifest files to UTF-8 Change By: Ethan Brown Fix Version/s: PUP 4.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1319) ipaddress retruns now 127.0.0.2 since facter 2.4.5
Title: Message Title
Eric Sorenson updated an issue
Facter / FACT-1319
ipaddress retruns now 127.0.0.2 since facter 2.4.5
Change By:
Eric Sorenson
Hello,The new facter is bringing a regression on my VPS (Ubuntu 12.04)Instead of setting ipaddress to the external IP, it set it to 127.0.0.2.{noformat}+Here are the ipaddress related facts with v2.4.5+:ipaddress => 127.0.0.2ipaddress_lo => 127.0.0.1ipaddress_venet0 => 127.0.0.2ipaddress_venet0_0 => ww.xxx.yy.zzz <= this is the real IP address that was returned with facter 2.4.4+here is the content of /proc/net/route file+:Iface Destination Gateway Flags RefCnt Use Metric Mask MTU Window IRTT venet0 0025BB25 0001 0 0 0 00FF 0 0 0 venet0 0001 0 0 0 0 0 0 +The output of ifconfig+:loLink encap:Local Loopbackinet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:638107 errors:0 dropped:0 overruns:0 frame:0 TX packets:638107 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:82856635 (82.8 MB) TX bytes:82856635 (82.8 MB)venet0Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00inet addr:127.0.0.2 P-t-P:127.0.0.2 Bcast:0.0.0.0 Mask:255.255.255.255 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 RX packets:12664381 errors:0 dropped:0 overruns:0 frame:0 TX packets:14917964 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6388359965 (6.3 GB) TX bytes:13581885278 (13.5 GB)venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00inet addr:ww.xxx.yy.zzz P-t-P:ww.xxx.yy.zzz Bcast:ww.xxx.yy.255 Mask:255.255.255.0 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1{noformat}the output of route:{noformat}Kernel IP routing tableDestination Gateway Genmask Flags Metric RefUse Ifaceww.xxx.yy.0 * 255.255.255.0 U 0 00 venet0default * 0.0.0.0 U 0 00 venet0{noformat}
Add Comment
Jira (PUP-5743) Puppet 3.8.5 breaks compatibility with rspec-puppet
Title: Message Title David Schmitt commented on PUP-5743 Re: Puppet 3.8.5 breaks compatibility with rspec-puppet I just released rspec-puppet 2.3.1 with a preliminary fix to work around this. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5743) Puppet 3.8.5 breaks compatibility with rspec-puppet
Title: Message Title David Schmitt commented on PUP-5743 Re: Puppet 3.8.5 breaks compatibility with rspec-puppet Krzysztof Suszyński do you have any other use-cases beside rspec-puppet who are hit by this issue? releasing a new version of puppet is quite expensive, and the hotfix in rspec-puppet basically locks puppet to this behaviour going forward, until we can haz a better API for this. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1319) ipaddress retruns now 127.0.0.2 since facter 2.4.5
Title: Message Title Eric Sorenson updated an issue Facter / FACT-1319 ipaddress retruns now 127.0.0.2 since facter 2.4.5 Change By: Eric Sorenson Environment: Hello,The new facter is bringing a regression on my VPS (Ubuntu 12.04)Instead of setting ipaddress to the external IP, it set it to 127.0.0.2.+Here are the ipaddress related facts with v2.4.5+:ipaddress => 127.0.0.2ipaddress_lo => 127.0.0.1ipaddress_venet0 => 127.0.0.2ipaddress_venet0_0 => ww.xxx.yy.zzz <= this is the real IP address that was returned with facter 2.4.4+here is the content of /proc/net/route file+:Iface Destination Gateway Flags RefCnt Use Metric Mask MTU Window IRTT venet0 0025BB25 0001 0 0 0 00FF 0 0 0 venet0 0001 0 0 0 0 0 0 +The output of ifconfig+:loLink encap:Local Loopbackinet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:638107 errors:0 dropped:0 overruns:0 frame:0 TX packets:638107 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:82856635 (82.8 MB) TX bytes:82856635 (82.8 MB)venet0Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00inet addr:127.0.0.2 P-t-P:127.0.0.2 Bcast:0.0.0.0 Mask:255.255.255.255 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 RX packets:12664381 errors:0 dropped:0 overruns:0 frame:0 TX packets:14917964 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6388359965 (6.3 GB) TX bytes:13581885278 (13.5 GB)venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00inet addr:ww.xxx.yy.zzz P-t-P:ww.xxx.yy.zzz Bcast:ww.xxx.yy.255 Mask:255.255.255.0 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1the output of route:Kernel IP routing tableDestination Gateway Genmask Flags Metric RefUse Ifaceww.xxx.yy.0 * 255.255.255.0 U 0 00 venet0default * 0.0.0.0 U 0 00 venet0 Add Comment
Jira (PUP-5743) Puppet 3.8.5 breaks compatibility with rspec-puppet
Title: Message Title Krzysztof Suszyński commented on PUP-5743 Re: Puppet 3.8.5 breaks compatibility with rspec-puppet I wanted to confirm that by using the latest version of `rspec-puppet` problem does not occur for my code. I've just tested it with our code. Thanks David Schmitt Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5718) Modify install.rb to install a puppet.bat file on windows
Title: Message Title Melissa Stone updated an issue Puppet / PUP-5718 Modify install.rb to install a puppet.bat file on windows Change By: Melissa Stone Sprint: RE 2016-02-03 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5120) Send checksum_type and static_catalog query params in catalog request
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-5120 Send checksum_type and static_catalog query params in catalog request Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-493) Update install.rb to install .bat files on windows
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Hiera / HI-493 Update install.rb to install .bat files on windows Change By: Melissa Stone Assignee: Melissa Stone Scrum Team: Release Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5718) Modify install.rb to install a puppet.bat file on windows
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-5718 Modify install.rb to install a puppet.bat file on windows Change By: Melissa Stone Assignee: Melissa Stone Scrum Team: Release Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5726) Non-English values for USERNAME and USERPROFILE causes multiple home directories to be created
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5726 Non-English values for USERNAME and USERPROFILE causes multiple home directories to be created Change By: Ethan Brown Fix Version/s: PUP 4.x Fix Version/s: PUP 4.3.3 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5736) Remove usage of win32-process gem
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5736 Remove usage of win32-process gem Change By: Ethan Brown Fix Version/s: PUP 4.3.3 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5728) Change default parsing of manifest files to UTF-8
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5728 Change default parsing of manifest files to UTF-8 Change By: Ethan Brown Fix Version/s: PUP 4.3.3 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5743) Puppet 3.8.5 breaks compatibility with rspec-puppet
Title: Message Title David Schmitt commented on PUP-5743 Re: Puppet 3.8.5 breaks compatibility with rspec-puppet Yeah, it's a hairy part of the code. Thanks for validation, Krzysztof Suszyński. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1288) Use leatherman_install to ensure consistent install location
Title: Message Title Michael Smith updated an issue Facter / FACT-1288 Use leatherman_install to ensure consistent install location Change By: Michael Smith Fix Version/s: FACT 3.1.4 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5718) Modify install.rb to install a puppet.bat file on windows
Title: Message Title Melissa Stone updated an issue Puppet / PUP-5718 Modify install.rb to install a puppet.bat file on windows Change By: Melissa Stone Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-493) Update install.rb to install .bat files on windows
Title: Message Title Melissa Stone updated an issue Hiera / HI-493 Update install.rb to install .bat files on windows Change By: Melissa Stone Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-493) Update install.rb to install .bat files on windows
Title: Message Title Melissa Stone updated an issue Hiera / HI-493 Update install.rb to install .bat files on windows Change By: Melissa Stone Sprint: RE 2016-02-03 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5714) Add a 'git' checksum type for file resource sources
Title: Message Title Michael Smith commented on PUP-5714 Re: Add a 'git' checksum type for file resource sources Should this be in the Direct Puppet epic? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5120) Send checksum_type and static_catalog query params in catalog request
Title: Message Title Michael Smith commented on PUP-5120 Re: Send checksum_type and static_catalog query params in catalog request Continuing the discussion here (seems more appropriate than git for design discussions): Josh Cooper: It occurred to me on the way home that we may need the agent to send all supported checksums after all... For example, in the very near future, I want to add support for the git checksum type, as described in PUP-5714. This way the master doesn't compute any checksums at all. It just looks up the object id from git, and inlines that in the catalog. But what happens if the agent only sends one checksum type git? If the master doesn't support it, then what does it fall back to? The master has to guess, and we're essentially back to where we are now, not knowing if the agent supports md5 or not. If the agent sent a list of supported digest algorithms, e.g. git,sha256, then the master could use git if it is capable of using it, otherwise fallback to sha256, but in no circumstance would the master select md5 since the agent said it doesn't support it. So perhaps a new puppet setting supported_digest_algorithms? Some questions that raises: How do filebucket and static catalogs interact? Filebucket only works with things that match the digest_algorithm. It seems like filebucket would be unnecessary, since the master is linking to a specific version of a specific file, so this is probably ok. How should supported_digest_algorithms and digest_algorithm relate? I can't think of a reason they have to be explicitly tied, so it would probably be by convention; if you want digest_algorithm to be the default for static catalogs, then it needs to match the first item in supported_digest_algorithms. What would it mean to specify digest_algorithm=git for puppet apply? That may be the first case where a Puppet setting can only be used with agent runs and not apply runs. That suggests we probably do want to have separate concepts for digest_algorithm and what the static compiler needs. None of those seem blocking. This essentially means `digest_algorithms` will be ignored for static catalogs. Add Comment
Jira (PUP-5703) Handle cached catalog and pluginsync inconsistencies
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-5703 Handle cached catalog and pluginsync inconsistencies Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5743) Puppet 3.8.5 breaks compatibility with rspec-puppet
Title: Message Title Krzysztof Suszyński commented on PUP-5743 Re: Puppet 3.8.5 breaks compatibility with rspec-puppet Couldn't you just add some logic to public environment setter? Public setter can accept values in string, and set it in other parts as it is required. Ideally mostly in the same form ex.: Symbol. In that way you will not change the public interface and in the meanwhile changing internal implementation to your needs or liking. Is something stopping you from doing that? It should be rather straight forward to do this, isn't? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2289) Use historical-catalogs endpoint in sync
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-2289 Use historical-catalogs endpoint in sync Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2214) anonymized logs don't compress
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2214 anonymized logs don't compress Change By: Wyatt Alt Sprint: PuppetDB 2016- 02 01 - 10 27 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5751) Setting enc paramater environment seems to corrupt the internal environment paramater.
Title: Message Title Jason A. Smith created an issue Puppet / PUP-5751 Setting enc paramater environment seems to corrupt the internal environment paramater. Issue Type: Bug Affects Versions: PUP 3.8.5 Assignee: Unassigned Components: Language Created: 2016/01/25 12:45 PM Environment: Testing an upgrade from 3.8.4 to 3.8.5 with a puppet master and custom ENC script. Priority: Normal Reporter: Jason A. Smith We have been using Puppet for several years, back when Puppet was not setting a top-scope environment parameter, so our custom ENC script would to this. When testing the latest 3.8.5 version of Puppet, we discovered that when the ENC was setting this top-scope environment parameter, it would appear to corrupt it somehow. It could still be used in templates and strings, but if it was used in a logical _expression_, like:
Jira (PUP-5743) Puppet 3.8.5 breaks compatibility with rspec-puppet
Title: Message Title Henrik Lindberg commented on PUP-5743 Re: Puppet 3.8.5 breaks compatibility with rspec-puppet Now... changing Puppet back to the way it was before; environment being of String type in a Node will be an interesting excersice as it would again change what needs to be done in rspec-puppet. Our options are: Change puppet back to using strings, and enforce that the attribute is a string. Change rspec-puppet in sync with the puppet release. Keep it as a symbol (it is symbol in parts of the code, and string in other parts), but enforce (and document) that it is a Node.environment (name) is a Symbol. I am leaning towards keeping it as a Symbol. What do you think? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5560) Look at Improving Unicode for all Windows gems
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-5560
Look at Improving Unicode for all Windows gems
Change By:
Ethan Brown
h4. win32-security - PUP-5538 / PUP-5735* {{win32-security}} has problems - https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-security-0.2.5/lib/win32/security/windows/functions.rb - see {{ConvertSidToStringSidA}}, {{ConvertStringSidToSidA}}, {{LookupAccountNameA}}, {{LookupAccountSidA}}* PUP-5538 for the majority of the work + minor cleanup in PUP-5735h4. win32-service* https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-service-0.8.6/lib/win32/windows/functions.rb#L24-L75 - see {{CreateEventA}}, {{FormatMessageA}}, {{ChangeServiceConfigA}}, {{ChangeServiceConfig2A}}, {{CreateServiceA}}, {{EnumServicesStatusExA}}, {{GetServiceDisplayNameA}}, {{GetServiceKeyNameA}}, {{LookupPrivilegeValueA}}, {{OpenSCManagerA}}, {{OpenServiceA}}, {{QueryServiceConfigA}}, {{QueryServiceConfig2A}}, {{RegisterServiceCtrlHandlerExA}}, {{StartServiceA}}, {{StartServiceCtrlDispatcherA}}h4. win32-process - PUP- 5752 / PUP- 5736* https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-process-0.7.4/lib/win32/process/functions.rb - see {{GetModuleHandleA}}, {{GetVersionExA}}, {{GetVolumeInformationA}}, {{CreateJobObjectA}}, {{OpenJobObjectA}}, {{ConvertSidToStringSidA}}h4. win32-eventlog * https://github.com/puppetlabs/puppet-win32-ruby/blob/2.1.x-x64/ruby/lib/ruby/gems/2.1.0/gems/win32-eventlog-0.6.2/lib/win32/windows/functions.rb - see {{ClearEventLogA}}, {{LookupAccountSidA}}, {{OpenEventLogA}}, {{OpenBackupEventLogA}}, {{ReadEventLogA}}, {{RegConnectRegistryA}}, {{RegCreateKeyExA}}, {{RegisterEventSourceA}}, {{RegOpenKeyExA}}, {{RegQueryValueExA}}, {{RegSetValueExA}}, {{ReportEventA}}, {{CreateEventA}}, {{ExpandEnvironmentStringsA}}, {{FormatMessageA}}, {{LoadLibraryExA}}I have filed upstream tickets* https://github.com/djberg96/win32-security/issues/8* https://github.com/djberg96/win32-service/issues/32* https://github.com/djberg96/win32-process/issues/21* https://github.com/djberg96/win32-eventlog/issues/19
Add Comment
Jira (PDB-2214) anonymized logs don't compress
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-2214 anonymized logs don't compress Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2214) anonymized logs don't compress
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2214 anonymized logs don't compress Change By: Wyatt Alt Scope Change Category: Adopted Scope Change Reason: had time to work on it Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2350) Consider more discriminating exception handling in CLI
Title: Message Title Rob Browning created an issue PuppetDB / PDB-2350 Consider more discriminating exception handling in CLI Issue Type: Improvement Assignee: Unassigned Created: 2016/01/25 1:00 PM Priority: Normal Reporter: Rob Browning i.e. perhaps only display the usage message if the exception was a program_options exception. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5752) Replace win32-process calls with internal API implementations that are wide-string compatible
Title: Message Title Ethan Brown created an issue Puppet / PUP-5752 Replace win32-process calls with internal API implementations that are wide-string compatible Issue Type: Bug Assignee: Unassigned Created: 2016/01/25 1:31 PM Fix Versions: PUP 4.4.0, PUP 4.3.3 Priority: Normal Reporter: Ethan Brown win32-process has some ANSI API calls that may cause problems in a non-US language environment - some of this is captured in PUP-5736 This ticket should involve replacing API calls internally where applicable, and PUP-5736 involves the mechanics of removing the gems from puppet-win32-ruby, etc. Add Comment
Jira (PUP-5753) Validate the bugs logged agains the Unicode epic.
Title: Message Title Steve Barlow created an issue Puppet / PUP-5753 Validate the bugs logged agains the Unicode epic. Issue Type: Task Assignee: Unassigned Created: 2016/01/25 1:36 PM Priority: Normal Reporter: Steve Barlow Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-2351) (maint) Remove dependency on leatherman::curl
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2351 (maint) Remove dependency on leatherman::curl Change By: Andrew Roetker Scope Change Category: Found Scope Change Reason: Trying to fix PuppetDB-CLI pipeline Fix Version/s: PDB CLI 0.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-917) Identify why a cached catalog was used
Title: Message Title William Hopper commented on PUP-917 Re: Identify why a cached catalog was used Notes for functional review: There are five scenarios that should be verified here: 1) An agent run where no cached catalog is used. (Don't set --use_cached_catalog and ensure the new catalog successfully compiles). The report should include cached_catalog_status: unused 2) An agent run where the user explicitly sets --use_cached_catalog to use a cached catalog. The report should include cached_catalog_status: use_cached_catalog. 3) An agent run where --use_cached_catalog is not set, but the new catalog fails to compile. usecacheonfailure is true by default, and so the report should include cached_catalog_status: use_cache_on_failure. Note that I'm thinking it might be good to remove the underscores from this status so as to match the setting name. 4) An agent run where the user explicitly sets --use_cached_catalog but there is no cached catalog available. The report should include cached_catalog_status: unused. 5) An agent run where --use_cached_catalog is not set, the new catalog fails to compile, and there is no cached catalog available. The report should include cached_catalog_status: unused.. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2351) (maint) Remove dependency on leatherman::curl
Title: Message Title gepetto-bot updated an issue PuppetDB / PDB-2351 (maint) Remove dependency on leatherman::curl Change By: gepetto-bot Sprint: PuppetDB 2016-01-27 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5694) Create static_catalog per-environment setting
Title: Message Title William Hopper commented on PUP-5694 Re: Create static_catalog per-environment setting Joshua Partlow ah, I hadn't thought of that case. From a few quick tests, it looks like setting static_catalogs in puppet.conf does not have any effect on any environments. In my example, production has static_catalogs=false and test does not specify static_catalogs. In my puppet.conf, I've set static_catalogs=true. [root@gqwd6sc8zt78edl puppet]# puppet config print static_catalogs --environment=production false puppet config print static_catalogs --environment=test false Josh Cooper is this correct, and static_catalogs cannot be set globally in puppet.conf? Add Comment
Jira (PUP-5694) Create static_catalog per-environment setting
Title: Message Title Joshua Partlow commented on PUP-5694 Re: Create static_catalog per-environment setting I'm assuming that if you set static_catalog in puppet.conf, that it applies to any environment that does not have static_catalog set in it's environment.conf. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2351) (maint) Remove dependency on leatherman::curl
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2351 (maint) Remove dependency on leatherman::curl Issue Type: Bug Assignee: Unassigned Created: 2016/01/25 3:22 PM Priority: Normal Reporter: gepetto-bot This commit removes the unused leatherman::curl dependency from the project. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PDB-2332) Benchmark does not POST command version
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-2332 Benchmark does not POST command version Change By: Wyatt Alt Assignee: Wyatt Alt Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-2332) Benchmark does not POST command version
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2332 Benchmark does not POST command version Change By: Wyatt Alt Sprint: PuppetDB 2016- 02 01 - 10 27 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5617) agent stalls when connection with master is dropped
Title: Message Title Michael Smith updated an issue Puppet / PUP-5617 agent stalls when connection with master is dropped Change By: Michael Smith Sprint: Client Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-16) Refactor command line options to support commands
Title: Message Title Peter Huene assigned an issue to Peter Huene Native Puppet / NPUP-16 Refactor command line options to support commands Change By: Peter Huene Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5735) Remove usage of win32-security gem
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5735 Remove usage of win32-security gem Change By: Ethan Brown Fix Version/s: PUP 4.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5736) Remove usage of win32-process gem
Title: Message Title Ethan Brown updated an issue Puppet / PUP-5736 Remove usage of win32-process gem Change By: Ethan Brown Fix Version/s: PUP 4.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1330) Smoke test packages (FACT 2.4.6)
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1330 Smoke test packages (FACT 2.4.6) Change By: Kylo Ginsberg (Initial planned release date: 2016-01-26)Procedure may vary by project and point in the release cycle. Ask around.In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc).For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master. Manual smoke testing can therefore be limited to other package formats than deb and rpm.For the Puppet gem, we don't yet have automated acceptance testing, so some quick manual smoke testing should always be performed. Platform packages express their dependencies differently than gems, so it's possible to encounter a situation where the build pipeline produced packages out of sync with the gems.Lighter testing of Z releases is acceptable. * Add a link to the Packages repository that you receive from the "Tag and create packages" subtask * Ping folks on your team for help with different platforms. * When you pick up a platform, please leave a comment below that you are testing it. When it looks good, leave another comment, preferably with a code snippet showing the commands executed and their output. * When all platforms picked have been smoke tested, move this ticket to done.IMPORTANT: Please edit the description of this ticket and remove "Example:" below. Edit the platforms to smoke test on, and the smoke test procedure. Example: Smoke test platforms: * pick some platforms such as * gem - select one Linux for the universal gem, Windows with x64 platform-specific gem, and Windows with x86 platform-specific gem * Windows 2003/2008/2012 (msi) * Solaris 10/11 (tarball or gem?) * OSX (dmg) * (Note if you are smoke testing Puppet and pick an rpm or deb based platform, concentrate on testing a gem or tarball, since acceptance should have adequately smoke tested those packages.)* RHEL / 7 or CentOS 5/6/ 7* Fedora 19/20* Debian 6/ 7 * Ubuntu 10.04/12.04/14.04 Smoke test procedure: * Start/stop/restart a master (if the platform supports that) does facter produce output * Start/stop/restart an agent * Help/ does ' man facter' look correct * Write and run some manifests is facter version correct? Dependencies: * Tag and create packages * For Windows MSIs - Push tag Add Comment
Jira (PUP-5741) Confusing error message for invalid types for comparison operations
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5741 Confusing error message for invalid types for comparison operations Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5695) Add checksum_value parameter to file type
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-5695 Add checksum_value parameter to file type Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5529) (Catalog Metadata) As a puppet administrator, I want to reduce the load on my compile masters when nothing has changed on my intended system state. (CPU load reduction of 60%)
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5529 (Catalog Metadata) As a puppet administrator, I want to reduce the load on my compile masters when nothing has changed on my intended system state. (CPU load reduction of 60%) Change By: Erik Dasher QA Contact: Erik Dasher Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5535) (Static Catalog) As a puppet administrator I want to reduce the load on my compiler masters when reapplying a cached catalog
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5535 (Static Catalog) As a puppet administrator I want to reduce the load on my compiler masters when reapplying a cached catalog Change By: Erik Dasher QA Contact: Erik Dasher Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5706) As a puppet administrator, I want to know if and why a cached catalog was applied
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5706 As a puppet administrator, I want to know if and why a cached catalog was applied Change By: Erik Dasher QA Contact: Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5532) As a puppet administrator, when I enable direct puppet on my master, agents that do not support it should function as they did before.
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5532 As a puppet administrator, when I enable direct puppet on my master, agents that do not support it should function as they did before. Change By: Erik Dasher QA Contact: Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5530) (Catalog Metadata) As a puppet administrator, I do not want the compile master to compile a catalog unless I have specified that the compilation should occur.
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5530 (Catalog Metadata) As a puppet administrator, I do not want the compile master to compile a catalog unless I have specified that the compilation should occur. Change By: Erik Dasher QA Contact: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5528) As a puppet administrator, I can enable direct puppet on a per environment basis as an onramp to adoption.
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5528 As a puppet administrator, I can enable direct puppet on a per environment basis as an onramp to adoption. Change By: Erik Dasher QA Contact: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5526) (Static Catalog) As a puppet administrator, I want the catalog that I apply to produce the same results regardless of the updates that happen to out-of-band file content.
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5526 (Static Catalog) As a puppet administrator, I want the catalog that I apply to produce the same results regardless of the updates that happen to out-of-band file content. Change By: Erik Dasher QA Contact: Erik Dasher Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5694) Create static_catalog per-environment setting
Title: Message Title
William Hopper updated an issue
Puppet / PUP-5694
Create static_catalog per-environment setting
Change By:
William Hopper
Comment:
[~joshua.partlow] ah, I hadn't thought of that case. From a few quick tests, it looks like setting {{static_catalogs}} in {{puppet.conf}} does *not* have any effect on any environments. In my example, {{production}} has {{static_catalogs=false}} and {{test}} does not specify {{static_catalogs}}. In my {{puppet.conf}}, I've set {{static_catalogs=true}}.{noformat}[root@gqwd6sc8zt78edl puppet]# puppet config print static_catalogs --environment=productionfalsepuppet config print static_catalogs --environment=testfalse{noformat}[~josh] is this correct, and {{static_catalogs}} cannot be set globally in {{puppet.conf}}?
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-5533) (Static Catalog) As a puppet administrator, I should be able to correlate all agent run reports to a catalog.
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5533 (Static Catalog) As a puppet administrator, I should be able to correlate all agent run reports to a catalog. Change By: Erik Dasher QA Contact: Erik Dasher Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5695) Add checksum_value parameter to file type
Title: Message Title Michael Smith commented on PUP-5695 Re: Add checksum_value parameter to file type I'm working out what the semantics of this parameter should be: Should it ever be set automatically? Should it be enforced to match the checksum calculated for content? (if both are set) If it's purpose is to circumvent the flaws in putting the checksum type in content, then it doesn't seem like it needs to be set except when using the static compiler, and doesn't need to be enforced to match the checksum put into the content parameter. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5534) (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /environments/*/modules/*/files/*
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5534 (Static Catalog) As a puppet node, I should only be able to retrieve historical file content for files in /environments/*/modules/*/files/* Change By: Erik Dasher QA Contact: Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5694) Create static_catalog per-environment setting
Title: Message Title William Hopper commented on PUP-5694 Re: Create static_catalog per-environment setting Joshua Partlow Josh Cooper doh! I had static_catalogs under the master section rather than main, and it wasn't being picked up. It definitely does work as Josh descried above if it's in the correct section . Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5743) Puppet 3.8.5 breaks compatibility with rspec-puppet
Title: Message Title Henrik Lindberg commented on PUP-5743 Re: Puppet 3.8.5 breaks compatibility with rspec-puppet Go look at what is there? The environment is set in phases, and there is lots of old code that makes assumptions about in which order things occur. When we changed the behavior we added such a synchronization of two of the ways a node gets the "environment", via the name of an environment, or the actual environment (an instance that knows stuff about the environment, among other things the name of the environment (a Symbol)). At the end it boils down to, what is the return type of the method that returns the name of the environment for the node. It cannot both return String and Symbol at the same time. That is the problem, not protecting a ruby instance variable with setter/getter (and in this case multiple values, that in different times of the Node's lifecycle is a name or a real environment). Now, parts of the code uses symbol, others use string. There are modules and tools and what not in the eco system around Puppet. So, one type, what should it be? What it was earlier (String), what it became (Symbol)? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-16) Refactor command line options to support commands
Title: Message Title
Peter Huene updated an issue
Native Puppet / NPUP-16
Refactor command line options to support commands
Change By:
Peter Huene
The native compiler needs to support more commands than simply "compiling" a catalog for an environment.The proposed syntax:{code}puppetcpp [command] < command options>{code}Where the "command" will default to "compile" with the existing behavior.Initially there will be two commands: "compile" and "parse". The latter will be new functionality that generates parsed and validated AST files (specific format TBD, but YAML output is sufficient for initial work).
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
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-5694) Create static_catalog per-environment setting
Title: Message Title Joshua Partlow commented on PUP-5694 Re: Create static_catalog per-environment setting That's odd; I wouldn't have expected that. The settings allowed in environment.conf are still just settings. Unless they're explicitly blocked from being valid in puppet.conf (like manifest/modulepath). If that is the case, it causes a problem in PE as well, because we can't touch customer's environment.conf files since they are checked into the code manager. It's code, not configuration at that point. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5705) As a puppet admin, I want to enable static catalogs on a per-env basis so I can test the behavior without affecting production nodes
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5705 As a puppet admin, I want to enable static catalogs on a per-env basis so I can test the behavior without affecting production nodes Change By: Erik Dasher QA Contact: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5536) (Static Catalog) As a puppet administrator, when I enable direct puppet on my master, agents that do not support it should continue to update file content as they did previously
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5536 (Static Catalog) As a puppet administrator, when I enable direct puppet on my master, agents that do not support it should continue to update file content as they did previously Change By: Erik Dasher QA Contact: Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5531) (Static Catalog) As a puppet administrator, I want the agents to only attempt to fetch out-of-band file content when they know that the local content does not match desired state.
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5531 (Static Catalog) As a puppet administrator, I want the agents to only attempt to fetch out-of-band file content when they know that the local content does not match desired state. Change By: Erik Dasher QA Contact: Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-5527) (Control Catalog Compilation) As a puppet administrator, I can update the manifests on my master without causing agents to get those updates.
Title: Message Title Erik Dasher updated an issue Puppet / PUP-5527 (Control Catalog Compilation) As a puppet administrator, I can update the manifests on my master without causing agents to get those updates. Change By: Erik Dasher QA Contact: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1327) Is the Jira tidy-up done for this release and prepared for the next one? (FACT 2.4.6)
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-1327 Is the Jira tidy-up done for this release and prepared for the next one? (FACT 2.4.6) Issue Type: Sub-task Assignee: Branan Riley Created: 2016/01/25 4:53 PM Priority: Normal Reporter: Kylo Ginsberg (Initial planned release date: 2016-01-26) This happens on Jira - we need to clean up the current release and prepare for the next release. Mark the version that's going out as "Released" in the Project Admin -> Versions panel. Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future) Create a public pair of queries for inclusion in the release notes/announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes slated for the next release (Paste their URLs into the "Release story" ticket): 'project = XX AND affectedVersion = 'X.Y.Z', Save as "Introduced in X.Y.Z", click Details, add permission for Everyone 'project = XX AND
Jira (FACT-1332) Push tag (FACT 2.4.6)
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-1332 Push tag (FACT 2.4.6) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/01/25 4:53 PM Priority: Normal Reporter: Kylo Ginsberg (Initial planned release date: 2016-01-26) The development team is responsible for updating the stable/master branches as necessary. This will be done after the version bump in version.rb. Dependencies: Go / No Go meeting (except where it's required to push the tag to build packages - MSIs) Add Comment
Jira (FACT-1321) Install facter.bat et al on windows
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Facter / FACT-1321 Install facter.bat et al on windows Change By: Melissa Stone Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1324) Reconcile git commits and JIRA tickets (FACT 2.4.6)
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-1324 Reconcile git commits and JIRA tickets (FACT 2.4.6) Issue Type: Sub-task Assignee: Branan Riley Created: 2016/01/25 4:53 PM Priority: Normal Reporter: Kylo Ginsberg (Initial planned release date: 2016-01-26) Use the ticketmatch script to ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. cd ~/work git clone https://github.com/puppetlabs/ticketmatch cd ~/work/puppet # or whatever the repo is you're releasing from ruby ../ticketmatch/ticketmatch.rb Enter Git From Rev: 4.1.0 Enter Git To Rev: |master| stable Enter JIRA project: |PUP| Enter JIRA fix version: PUP 4.2.0 The output may contain the following headers: COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF ...) Lists git commits that don't have a corresponding ticket, at least not for the specified fix version. If the commit has a ticket, but the ticket is not targeted correctly, then the ticket's fixVersion should be updated. This can frequently happen if a ticket is initially targeted for a future release (master), but is pulled into
Jira (FACT-1334) Docs pushed (FACT 2.4.6)
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-1334 Docs pushed (FACT 2.4.6) Issue Type: Sub-task Assignee: Jorie Tappa Created: 2016/01/25 4:54 PM Priority: Normal Reporter: Kylo Ginsberg (Initial planned release date: 2016-01-26) Push the documentation updates to docs.puppetlabs.com. Dependencies: Go / No Go meeting (Status - Ship it!) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (FACT-1323) Is the code ready for release? (FACT 2.4.6)
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-1323 Is the code ready for release? (FACT 2.4.6) Issue Type: Sub-task Assignee: Branan Riley Created: 2016/01/25 4:53 PM Priority: Normal Reporter: Kylo Ginsberg (Initial planned release date: 2016-01-26) If there are any version dependencies expressed in the code base, make sure these are up to date. For Puppet, make sure the shas used to build the MSI are correct. For Puppet-Server, make sure all references to the puppet version are correct. All tests (spec, acceptance) should be passing on all platforms for both stable & master. If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through spec/acceptance/etc. tests Move all items that should be moved from Ready for CI to Ready for Review Have all tickets been resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20FACT%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%222.4.6%22
Jira (FACT-1329) Tag the release and create packages (FACT 2.4.6)
Title: Message Title
Kylo Ginsberg created an issue
Facter / FACT-1329
Tag the release and create packages (FACT 2.4.6)
Issue Type:
Sub-task
Assignee:
Morgan Rhodes
Created:
2016/01/25 4:53 PM
Priority:
Normal
Reporter:
Kylo Ginsberg
(Initial planned release date: 2016-01-26)
Tag and create packages
Developer provides the SHA - Branan Riley - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb)
checkout the sha
Make sure you are about to tag the correct thing
Create the tag e.g.) git tag -s -u {GPG key}
-m "1.7.3" 1.7.3
You need to know the pass phrase for this to complete successfully. It's important that we make sure all releases are signed to verify authenticity.
DO NOT push the tag to the repo, keep it local only
`git describe` will show you the tag. Make sure you're building what you think you're building.
Jira (FACT-1325) Update version number in source (FACT 2.4.6)
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-1325 Update version number in source (FACT 2.4.6) Issue Type: Sub-task Assignee: Branan Riley Created: 2016/01/25 4:53 PM Priority: Normal Reporter: Kylo Ginsberg (Initial planned release date: 2016-01-26) Bump VERSION in lib/FACT/version.rb or project.clj to correct version. Commit the updated version file. e.g) commit -m "(packaging) Update FACTERVERSION to 1.7.3". If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask). Once this is done, hand the SHA to be built to RelEng to be tagged. Dependencies: Is the code ready for release? Reconcile git commits and JIRA tickets
Jira (FACT-1330) Smoke test packages (FACT 2.4.6)
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-1330 Smoke test packages (FACT 2.4.6) Issue Type: Sub-task Assignee: Branan Riley Created: 2016/01/25 4:53 PM Priority: Normal Reporter: Kylo Ginsberg (Initial planned release date: 2016-01-26) Procedure may vary by project and point in the release cycle. Ask around. In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master. Manual smoke testing can therefore be limited to other package formats than deb and rpm. For the Puppet gem, we don't yet have automated acceptance testing, so some quick manual smoke testing should always be performed. Platform packages express their dependencies differently than gems, so it's possible to encounter a situation where the build pipeline produced packages out of sync with the gems. Lighter testing of Z releases is acceptable. Add a link to the Packages repository that you receive from the "Tag and create packages" subtask Ping folks on your team for help with different platforms. When you pick up a platform, please leave a comment below that you are testing it. When it looks good, leave another comment, preferably with a code snippet showing the commands executed and their output.
Jira (FACT-1322) facter 2.4.6 2016-01-26 Release
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-1322 facter 2.4.6 2016-01-26 Release Issue Type: Task Assignee: Branan Riley Created: 2016/01/25 4:53 PM Priority: Normal Reporter: Kylo Ginsberg facter 2.4.6 2016-01-26 Release When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward. When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready.
Jira (FACT-1331) Go/no-go meeting (before 4pm) (FACT 2.4.6)
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-1331 Go/no-go meeting (before 4pm) (FACT 2.4.6) Issue Type: Sub-task Assignee: Branan Riley Created: 2016/01/25 4:53 PM Priority: Normal Reporter: Kylo Ginsberg (Initial planned release date: 2016-01-26) This should happen Monday-Thursday, before 4pm. We should not be shipping anything after 4:00 PM or on a Friday both for our users, and because shipping takes time. Get a yes/no for the release from dev, docs, product, qa, releng. This meeting is informal, over chat, and usually happens right before packages are pushed. Keep in mind we typically do not ship releases in the evening and we don't ship on Friday if the release is a final release. Dependencies: Smoke testing Participants: Branan Riley Jorie Tappa Eric Sorenson John Duarte Morgan Rhodes
Jira (FACT-1326) Merge master into stable (FACT 2.4.6)
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-1326 Merge master into stable (FACT 2.4.6) Issue Type: Sub-task Assignee: Branan Riley Created: 2016/01/25 4:53 PM Priority: Normal Reporter: Kylo Ginsberg (Initial planned release date: 2016-01-26) For some releases, the code base will need to be merged down to stable. NOTE: This is usually only during a x.y.0 release, but even then it may have already been done. If it doesn't apply, close this ticket. Assuming you have origin (your remote) and upstream (puppetlabs remote), the commands will look something like this: git fetch upstream git rebase upstream/master
Jira (FACT-1333) Packages pushed (FACT 2.4.6)
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-1333 Packages pushed (FACT 2.4.6) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/01/25 4:54 PM Priority: Normal Reporter: Kylo Ginsberg (Initial planned release date: 2016-01-26) Push packages run `rake pl:jenkins:uber_ship` You will need the keys to the castle (aka the passphrase) for this to work. Don't forget to make sure everything looks like it's in the correct folder, the pkgs dir has been cleared out, and that you are shipping for all expected platforms. Get a second set of RelEng eyes on the packages that are about to be shipped to make sure everything looks a-okay. If you're shipping a gem you need to make sure you have a rubygems account, are an owner of that project, and have a gem config file. If you're shipping puppet you need to sign the MSI file for Windows. This is a manual process and the ship task doesn't ship or build the msi so talk to Moses or Haus for more details. This file also needs to be manually signed.
Jira (FACT-1328) Prepare long form release notes and short form release story (FACT 2.4.6)
Title: Message Title Kylo Ginsberg created an issue Facter / FACT-1328 Prepare long form release notes and short form release story (FACT 2.4.6) Issue Type: Sub-task Assignee: Jorie Tappa Created: 2016/01/25 4:53 PM Priority: Normal Reporter: Kylo Ginsberg (Initial planned release date: 2016-01-26) Collaborating with product for release story Dependencies: Reconcile git commits and JIRA tickets Add Comment This message was sent by Atlassian
Jira (FACT-1321) Install facter.bat et al on windows
Title: Message Title Melissa Stone updated an issue Facter / FACT-1321 Install facter.bat et al on windows Change By: Melissa Stone Story Points: 3 Component/s: Windows Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1321) Install facter.bat et al on windows
Title: Message Title Melissa Stone created an issue Facter / FACT-1321 Install facter.bat et al on windows Issue Type: Bug Assignee: Unassigned Created: 2016/01/25 4:53 PM Priority: Normal Reporter: Melissa Stone Ideally, the cmake stuff would just do this, but in the meantime, I have some work arounds Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
