Jira (PUP-3200) Is rrdgraph still supported?
Title: Message Title Josh Cooper commented on an issue Re: Is rrdgraph still supported? That last real change to the rrdgraph report processor was e9f9d26 in Sep 23, 2010. I have no idea if it still works, e.g. does it handle the transaction_uuid we added? There have been some inquiries as to whether rrdgraph works on the puppet-users list: https://groups.google.com/d/topic/puppet-users/Z_Z9OTX1GGQ/discussion. I'm sure there are some people using it, but I think the number is very small. Add Comment Puppet / PUP-3200 Is rrdgraph still supported? We're writing tests for puppet's reporting abilities and wondering if rrdgraph is something that's critical to test or if it's really supported anymore The docs link to a dead RubyRRDtool rubyforge page and the RubyRRDtool gem won't install, at least without some hassle. I haven't been able to get it to work and there don't seem to be many people onlin... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails fr
Jira (PUP-3222) Windows service provider references a non-existent class
Title: Message Title Josh Cooper commented on an issue Re: Windows service provider references a non-existent class Merged in 8d0f08c2d to be released in 3.7.1 Add Comment Puppet / PUP-3222 Windows service provider references a non-existent class MCollective has a dependency on a windows gem that we had to change as part of the FFI work. The issue was posted here: http://ask.puppetlabs.com/question/13630/mcollective-windows-service-no-longer-working/?answer=13637 Our docs describe the change in question: https://docs.puppetlabs.com/puppet/latest/reference/deprecated_windows_api.html#updated-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3222) Windows service provider references a non-existent class
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-3222 Windows service provider references a non-existent class Change By: Josh Cooper Assignee: Ethan Brown Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3162) Block $environment in directory based environment configuration settings
Title: Message Title Joshua Partlow commented on an issue Re: Block $environment in directory based environment configuration settings New PR 3065 takes the whitelist approach and removes the early validation of default_manifest that would halt puppet startup in 3.7.0. Sorry for the churn on that later piece Nicholas Fagerlund; predocs have been updated. Add Comment Puppet / PUP-3162 Block $environment in directory based environment configuration settings Using interpolation of $environment can cause problems when it is used in a fashion that makes a directory based environment behave as dynamic environments. We should help users by making it an error to use this. It plays a role in dynamic environments in 3.x, so this can not be fixed until 4.0 because it is a breaking change otherwise. When startin... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visi
Jira (PUP-3226) Non-existent directory environments should raise a helpful error
Title: Message Title
Joshua Partlow commented on an issue
Re: Non-existent directory environments should raise a helpful error
I think this is a combination of special setup for PE and the default production environment having a blessed status required for bootstrapping, but will need to investigate.
Add Comment
Puppet / PUP-3226
Non-existent directory environments should raise a helpful error
If in puppet.conf I have: {noformat} [main] basemodulepath = /etc/puppetlabs/puppet/modules environmentpath = /etc/puppetlabs/puppet/envs {noformat} and if /etc/puppetlabs/puppet/modules/test/manifests/init.pp exists with `class test { }` in it, and if /etc/puppetlabs/puppet/envs/production does not exist, when I run {{puppet agent -t}} I get {{Erro...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
F
Jira (PUP-3222) Windows service provider references a non-existent class
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-3222 Windows service provider references a non-existent class Change By: Ethan Brown Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3226) Non-existent directory environments should raise a helpful error
Title: Message Title
Hunter Haugen updated an issue
Puppet / PUP-3226
Non-existent directory environments should raise a helpful error
Change By:
Hunter Haugen
If in puppet.conf I have:{noformat}[main]basemodulepath = /etc/puppetlabs/puppet/modulesenvironmentpath = /etc/puppetlabs/puppet/envs{noformat}and if /etc/puppetlabs/puppet/modules/test/manifests/init.pp exists with {{ ` class \ test \ { \ } }} ` in it, and if /etc/puppetlabs/puppet/envs/production does not exist, when I run {{puppet agent -t}} I get {{Error 400 on SERVER: Could not find class test for ...}}This is because if {{$environmentpath/$environment}} does not exist then the environment is considered to be non-existent. If I create /etc/puppet/envs/production (even leaving it empty) then it will work as desired.To avoid red-herring hunts, it would probably be better UX to have the puppetmaster raise an error describing that the environment (in this case "production") cannot be found in the environmentpath.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3226) Non-existent directory environments should raise a helpful error
Title: Message Title
Hunter Haugen updated an issue
Puppet / PUP-3226
Non-existent directory environments should raise a helpful error
Change By:
Hunter Haugen
If in puppet.conf I have:{noformat}[main]basemodulepath = /etc/ puppetlabs/ puppet/modulesenvironmentpath = /etc/ puppetlabs/ puppet/envs{noformat}and if /etc/ puppetlabs/ puppet/modules/test/manifests/init.pp exists with {{class\ test \{ \}}} in it, and if /etc/ puppetlabs/ puppet/envs/production does not exist, when I run {{puppet agent -t}} I get {{Error 400 on SERVER: Could not find class test for ...}}This is because if {{$environmentpath/$environment}} does not exist then the environment is considered to be non-existent. If I create /etc/puppet/envs/production (even leaving it empty) then it will work as desired.To avoid red-herring hunts, it would probably be better UX to have the puppetmaster raise an error describing that the environment (in this case "production") cannot be found in the environmentpath.
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3226) Non-existent directory environments should raise a helpful error
Title: Message Title Hunter Haugen updated an issue Puppet / PUP-3226 Non-existent directory environments should raise a helpful error Change By: Hunter Haugen Environment: PE 3.3.1 ( puppet 3.6.2 ) Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3226) Non-existent directory environments should raise a helpful error
Title: Message Title
Hunter Haugen created an issue
Puppet / PUP-3226
Non-existent directory environments should raise a helpful error
Issue Type:
Improvement
Assignee:
Unassigned
Created:
09/Sep/14 5:11 PM
Environment:
puppet 3.6.2
Priority:
Normal
Reporter:
Hunter Haugen
If in puppet.conf I have:
[main]
basemodulepath = /etc/puppet/modules
environmentpath = /etc/puppet/envs
and if /etc/puppet/modules/test/manifests/init.pp exists with class\ test { }}} in it, and if /etc/puppet/envs/production does not exist, when I run {{puppet agent -t I get Error 400 on SERVER: Could not find class test for ...
This is because if $environmentpath/$environment does not exist then the environment is considered to be non-existent. If I create /etc/puppet/envs/production (even leaving it empty) then it will work as desired.
To avoid red-herring hunts, it would probably be better UX to have the puppetmaster raise an error describing that the environment (in this case "production") cannot be found in the environmentpath.
Jira (PUP-3225) Remove legacy and dynamic environment support.
Title: Message Title Joshua Partlow created an issue Puppet / PUP-3225 Remove legacy and dynamic environment support. Issue Type: Improvement Assignee: Andy Parker Components: DOCS, Modules Created: 09/Sep/14 4:59 PM Fix Versions: 4.0.0 Priority: Normal Reporter: Joshua Partlow Legacy and dynamic environments are deprecated, but support has not yet been removed. We can't remove manifest/modulepath/config_version settings, because they are still parsed in environment.conf, but we should raise an error? if they are found in puppet.conf. Legacy loaders should be removed. Puppet::Node::Environment should get cleanup for code paths related to legacy environment creation. Undoubtedly other things I'm forgetting about. Andy Parker I didn't see a ticket for this when I browsed the 4.0 stack; might have missed it though. Add Comment
Jira (PUP-3003) Windows MSI contains unneeded files
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3003 Windows MSI contains unneeded files Change By: Josh Cooper Fix Version/s: 3.7.1 Fix Version/s: 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3224) Literal Hash as Hash key does not parse
Title: Message Title
Henrik Lindberg created an issue
Puppet / PUP-3224
Literal Hash as Hash key does not parse
Issue Type:
Bug
Assignee:
Andy Parker
Components:
DSL
Created:
09/Sep/14 4:15 PM
Fix Versions:
3.7.1
Priority:
Normal
Reporter:
Henrik Lindberg
As discovered in GEP-109, the parser parses a literal hash key in a hash the wrong way and ends up hitting EOF.
{ {10=>20} => 10 }
Add Comment
Jira (PUP-3188) Puppet module tool no longer processes files starting with a period as erb
Title: Message Title Anderson Mills updated an issue Puppet / PUP-3188 Puppet module tool no longer processes files starting with a period as erb Change By: Anderson Mills Fix Version/s: 3.x Fix Version/s: 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3011) Add acceptance test for PMT install command changes for 3.7
Title: Message Title Anderson Mills updated an issue Puppet / PUP-3011 Add acceptance test for PMT install command changes for 3.7 Change By: Anderson Mills Fix Version/s: 3.7.1 Fix Version/s: 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2701) Add acceptance tests for PMT build metadata.json support
Title: Message Title Anderson Mills updated an issue Puppet / PUP-2701 Add acceptance tests for PMT build metadata.json support Change By: Anderson Mills Fix Version/s: 3.7.1 Fix Version/s: 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3188) Puppet module tool no longer processes files starting with a period as erb
Title: Message Title Anderson Mills updated an issue Puppet / PUP-3188 Puppet module tool no longer processes files starting with a period as erb Change By: Anderson Mills Fix Version/s: 4.0.0 Fix Version/s: 3.x Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3012) Add acceptance test for PMT upgrade command changes for 3.7
Title: Message Title Anderson Mills updated an issue Puppet / PUP-3012 Add acceptance test for PMT upgrade command changes for 3.7 Change By: Anderson Mills Fix Version/s: 3.7.1 Fix Version/s: 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3015) Add acceptance test for PMT search command changes for 3.7
Title: Message Title Anderson Mills updated an issue Puppet / PUP-3015 Add acceptance test for PMT search command changes for 3.7 Change By: Anderson Mills Fix Version/s: 3.7.1 Fix Version/s: 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3188) Puppet module tool no longer processes files starting with a period as erb
Title: Message Title Anderson Mills updated an issue Puppet / PUP-3188 Puppet module tool no longer processes files starting with a period as erb Change By: Anderson Mills Fix Version/s: 3.7.1 Fix Version/s: 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3014) Add acceptance test for PMT generate command changes for 3.7
Title: Message Title Anderson Mills updated an issue Puppet / PUP-3014 Add acceptance test for PMT generate command changes for 3.7 Change By: Anderson Mills Fix Version/s: 3.7.1 Fix Version/s: 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3013) Add acceptance test for PMT build command changes for 3.7
Title: Message Title Anderson Mills updated an issue Puppet / PUP-3013 Add acceptance test for PMT build command changes for 3.7 Change By: Anderson Mills Fix Version/s: 3.7.1 Fix Version/s: 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3222) Windows service provider references a non-existent class
Title: Message Title Jeff Sparrow commented on an issue Re: Windows service provider references a non-existent class Found out we arent going live until later tomorrow afternoon. So I can test that in the morning. I will report back. Add Comment Puppet / PUP-3222 Windows service provider references a non-existent class MCollective has a dependency on a windows gem that we had to change as part of the FFI work. The issue was posted here: http://ask.puppetlabs.com/question/13630/mcollective-windows-service-no-longer-working/?answer=13637 Our docs describe the change in question: https://docs.puppetlabs.com/puppet/latest/reference/deprecated_windows_api.html#updated-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3222) Windows service provider references a non-existent class
Title: Message Title Jeff Sparrow commented on an issue Re: Windows service provider references a non-existent class You are completely right. I am not sure how I missed this: Originally I thought it was because I had removed ruby from path, thus it didnt know what to do, but even when running it from ruby, it is not installed: `C:\Program Files\Puppet Labs\Puppet\sys\ruby\bin>c:\marionette-collective\bin\register_service.bat Service mcollectived installed` Add Comment Puppet / PUP-3222 Windows service provider references a non-existent class MCollective has a dependency on a windows gem that we had to change as part of the FFI work. The issue was posted here: http://ask.puppetlabs.com/question/13630/mcollective-windows-service-no-longer-working/?answer=13637 Our docs describe the change in question: https://docs.puppetlabs.com/puppet/latest/reference/deprecated_windows_api.html#updated-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from
Jira (PUP-3222) Windows service provider references a non-existent class
Title: Message Title Josh Cooper commented on an issue Re: Windows service provider references a non-existent class Jeff Sparrow can you apply the commit in the linked PR to your puppet install, or edit lib/puppet/provider/service/windows.rb, and change lines like: - rescue Win32::Service::Error => detail + rescue => detail That should resolve the uninitialized constant Win32::Service::Error errors, but let me know if it doesn't Add Comment Puppet / PUP-3222 Windows service provider references a non-existent class MCollective has a dependency on a windows gem that we had to change as part of the FFI work. The issue was posted here: http://ask.puppetlabs.com/question/13630/mcollective-windows-service-no-longer-working/?answer=13637 Our docs describe the change in question: https://docs.puppetlabs.com/puppet/latest/reference/deprecated_windows_api.html#updated-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3222) Windows service provider references a non-existent class
Title: Message Title Jeff Sparrow commented on an issue Re: Windows service provider references a non-existent class I should note the mcollective service was installed. Add Comment Puppet / PUP-3222 Windows service provider references a non-existent class MCollective has a dependency on a windows gem that we had to change as part of the FFI work. The issue was posted here: http://ask.puppetlabs.com/question/13630/mcollective-windows-service-no-longer-working/?answer=13637 Our docs describe the change in question: https://docs.puppetlabs.com/puppet/latest/reference/deprecated_windows_api.html#updated-... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3222) Windows service provider references a non-existent class
Title: Message Title Josh Cooper commented on an issue Re: Windows service provider references a non-existent class The root cause here is that win32-service 0.7.x used to raise Win32::Service::Error when errors occurred. As part of the FFI migration, we moved win32-service to 0.8.4 (see PUP-1283 ), which no longer defines that class. We failed to update the windows service provider during that process. The bug was triggered, because the OP failed to install the mcollective service: C:\marionette-collective\bin>register_service.bat '"ruby"' is not recognized as an internal or external command, operable program or batch file So puppet would get an exception when trying to manage the non-existent mcollective serivce. And puppet was trying to rescue a non-existent exception class. I am guessing mcollective failed to register because of the way rubygems writes the ruby.bat file. Puppet vendors ruby in the MSI we produce, and we apply the following patch to work around the rubygems issue: https://gist.github.com/joshcooper/bf4613c1d4e886dad08c Add Comment Puppet / PUP-3222 Windows service provider references a non-existent class MCollective has a dependency on a windows gem that we had to change as part of the FFI work. The issue was posted here: http://ask.puppetlabs.com/question/13630/mcollective-windows-service-no-longer-working/?answer=13637 Our docs describe the change in question: https://docs.puppetlabs.com/puppet/latest/reference/deprecated_windows_api.html#updated-...
Jira (PUP-3186) Puppetmaster removes /etc/puppet/environments/production if it's a link rather than a directory
Title: Message Title Britt Gresham commented on an issue Re: Puppetmaster removes /etc/puppet/environments/production if it's a link rather than a directory Added PR-3062 This commit will test if the production directory environment exists and if it does puppet will test if it is a symlink or not. In the event that it is a symlink puppet will ensure that the followed path is a directory instead of ensuring the symlink itself is a directory. Add Comment Puppet / PUP-3186 Puppetmaster removes /etc/puppet/environments/production if it's a link rather than a directory We use puppet environments, and symlink the puppet folder of one of our git repos to /etc/puppet/environment. This is how it looks like: #:/etc/puppet/environments$ ls -l total 4 lrwxrwxrwx 1 root root 47 Jul 4 10:05 user1 -> /var/lib/ops-automation.user1/puppet lrwxrwxrwx 1 root root 49 Jul 4 10:05 user2 -> /var/lib/ops-automation.user2/pupp... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiv
Jira (PUP-3223) Support for rrdgraph should be deprecated
Title: Message Title Joe Pinsonault created an issue Puppet / PUP-3223 Support for rrdgraph should be deprecated Issue Type: Bug Affects Versions: 3.7.0 Assignee: Unassigned Created: 09/Sep/14 2:13 PM Priority: Minor Reporter: Joe Pinsonault In reference to PUP-3200 and nigel's comment, it looks like support for rrdgraph should be deprecated. The docs make it seem like it's still fully supported Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaed
Jira (PUP-3162) Block $environment in directory based environment configuration settings
Title: Message Title Henrik Lindberg commented on an issue Re: Block $environment in directory based environment configuration settings The "proceed after a warning" makes me nervous. People only find those when the ### has already hit the fan. Otherwise I agree. Add Comment Puppet / PUP-3162 Block $environment in directory based environment configuration settings Using interpolation of $environment can cause problems when it is used in a fashion that makes a directory based environment behave as dynamic environments. We should help users by making it an error to use this. It plays a role in dynamic environments in 3.x, so this can not be fixed until 4.0 because it is a breaking change otherwise. When startin... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://g
Jira (PUP-3162) Block $environment in directory based environment configuration settings
Title: Message Title Joshua Partlow commented on an issue Re: Block $environment in directory based environment configuration settings Henrik Lindberg I agree that those would be invalid environments, but I think those cases are separate from this ticket. Other than flipping to a whitelist of config_version and removing the halt on default_manifest being set with $environment in it, is there anything you think needs adding. If I made those changes, Puppet would log a warning, not interpolate but otherwise proceed for any setting that has an $environment set in it (other than config_version). Add Comment Puppet / PUP-3162 Block $environment in directory based environment configuration settings Using interpolation of $environment can cause problems when it is used in a fashion that makes a directory based environment behave as dynamic environments. We should help users by making it an error to use this. It plays a role in dynamic environments in 3.x, so this can not be fixed until 4.0 because it is a breaking change otherwise. When startin... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscri
Jira (PUP-3222) Windows service provider references a non-existent class
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3222 Windows service provider references a non-existent class Change By: Josh Cooper Sprint: 2014-09-17 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3162) Block $environment in directory based environment configuration settings
Title: Message Title Henrik Lindberg commented on an issue Re: Block $environment in directory based environment configuration settings Do you mean besides the name of the environment? (i.e. no /, spaces, should not start with . and other special characters that will create surprises). Other causes of invalid environment...: permissions, cannot read the content, or only some of the content the environment changed while loading it (very hard to detect, but still a problem) circularities via symlinks (perhaps not a valid problem for the environment per se) i.e. anything that makes environment loading produce something malodorous. After that, there can be many other problems in the environment; modules with broken meta data, module paths containing entries that cannot be read, does not exist etc. But that is really up to the evaluation / catalog compilation to detect and report. Add Comment Puppet / PUP-3162 Block $environment in directory based environment configuration settings Using interpolation of $environment can cause problems when it is used in a fashion that makes a directory based environment behave as dynamic environments. We should help users by making it an error to use this. It plays a role in dynamic environments in 3.x, so this can not be fixed until 4.0 because it is a breaking change otherwise. When startin...
Jira (PUP-3222) Windows service provider references a non-existent class
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3222 Windows service provider references a non-existent class Change By: Josh Cooper Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3175) Intermittent failure for node/check_woy_cache_works testcase
Title: Message Title Wayne Warren updated an issue Puppet / PUP-3175 Intermittent failure for node/check_woy_cache_works testcase Change By: Wayne Warren Fix Version/s: 3.7.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3174) After enabling directory environments the manifestdir setting is still required to be valid
Title: Message Title Andy Parker commented on an issue Re: After enabling directory environments the manifestdir setting is still required to be valid Merged into stable in 8ffaa4 Add Comment Puppet / PUP-3174 After enabling directory environments the manifestdir setting is still required to be valid PE gives a stack trace if the manifestdir does not exist. When setting up directory environments we recommend moving the $confdir/manifest folder into your environment which is guaranteed to break your install. https://docs.puppetlabs.com/puppet/latest/reference/environments.html Steps to reproduce: 1. Install PE3.3 on your platform of choice ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3177) Resource titles ending with square brackets fail
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3177 Resource titles ending with square brackets fail Change By: Eric Thompson QA Contact: Kurt Wall Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3177) Resource titles ending with square brackets fail
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-3177 Resource titles ending with square brackets fail Change By: Eric Thompson Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3097) Puppet 3.7.0 2014-09-02 Release
Title: Message Title Andy Parker updated an issue Puppet / PUP-3097 Puppet 3.7.0 2014-09-02 Release Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Andy Parker updated an issue Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-894) Too easy to hit "CRL not yet valid for " (and not very informative)
Title: Message Title Andy Parker updated an issue Puppet / PUP-894 Too easy to hit "CRL not yet valid for " (and not very informative) Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3186) Puppetmaster removes /etc/puppet/environments/production if it's a link rather than a directory
Title: Message Title Andy Parker updated an issue Puppet / PUP-3186 Puppetmaster removes /etc/puppet/environments/production if it's a link rather than a directory Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3190) "each" no longer supported in Puppet 3.7.0
Title: Message Title Andy Parker updated an issue Puppet / PUP-3190 "each" no longer supported in Puppet 3.7.0 Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3162) Block $environment in directory based environment configuration settings
Title: Message Title Andy Parker updated an issue Puppet / PUP-3162 Block $environment in directory based environment configuration settings Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1680) "incorrect header check" using Ruby 2
Title: Message Title Andy Parker updated an issue Puppet / PUP-1680 "incorrect header check" using Ruby 2 Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3174) After enabling directory environments the manifestdir setting is still required to be valid
Title: Message Title Andy Parker updated an issue Puppet / PUP-3174 After enabling directory environments the manifestdir setting is still required to be valid Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3177) Resource titles ending with square brackets fail
Title: Message Title Andy Parker updated an issue Puppet / PUP-3177 Resource titles ending with square brackets fail Change By: Andy Parker Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1680) "incorrect header check" using Ruby 2
Title: Message Title Andy Parker updated an issue Puppet / PUP-1680 "incorrect header check" using Ruby 2 Change By: Andy Parker Affects Version/s: 3.7.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1680) "incorrect header check" using Ruby 2
Title: Message Title Andy Parker updated an issue Puppet / PUP-1680 "incorrect header check" using Ruby 2 Change By: Andy Parker Affects Version/s: 3.4.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3174) After enabling directory environments the manifestdir setting is still required to be valid
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3174 After enabling directory environments the manifestdir setting is still required to be valid Change By: Andy Parker Assignee: Andy Parker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Andy Parker commented on an issue Re: Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Joshua Partlow had some comments on the PR about using --detailed-exitcodes to make it error out better. Add Comment Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Just recently there have been a few intermittent failures in resource/service/ticket_14297_handle_upstart.rb. (Btw note that this test is confined to Ubuntu.) Three examples: https://jenkins.puppetlabs.com/job/Puppet-Package-Acceptance-4.0/label=acc-coord,platform=precise/212/consoleFull https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Master/... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.g
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Andy Parker assigned an issue to Britt Gresham Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Change By: Andy Parker Assignee: Andy Parker Britt Gresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3222) Windows service provider references a non-existent class
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3222 Windows service provider references a non-existent class Change By: Josh Cooper Summary: Does not work with puppet 3.7 x86 or x64 Windows service provider references a non-existent class Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3222) Does not work with puppet 3.7 x86 or x64
Title: Message Title Josh Cooper moved an issue Puppet / PUP-3222 Does not work with puppet 3.7 x86 or x64 Change By: Josh Cooper Fix Version/s: 2.6.1 Fix Version/s: 3.7.1 Key: MCO PUP - 462 3222 Project: MCollective Puppet Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2650) 3.6.1 issues "warning" message for deprecation
Title: Message Title Ben Ford commented on an issue Re: 3.6.1 issues "warning" message for deprecation This also raises its nasty little head when running puppet resource. Add Comment Puppet / PUP-2650 3.6.1 issues "warning" message for deprecation Message is issued from agent runs at the warning level for a deprecation message. Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false. (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2396) Support ruby 2.0 x64 on windows
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2396 Support ruby 2.0 x64 on windows Change By: Josh Cooper Epic Status: Done Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3162) Block $environment in directory based environment configuration settings
Title: Message Title Joshua Partlow commented on an issue Re: Block $environment in directory based environment configuration settings Henrik Lindberg an environment name like 'what$environment' is invalid; it will be rejected both by the network routing, and will be ignored (if you had a directory 'what$environment' in your $environmentpath) by the Directories environment loader. Are there other criteria that you would consider to make an environment 'invalid' as we were discussing at standup? Add Comment Puppet / PUP-3162 Block $environment in directory based environment configuration settings Using interpolation of $environment can cause problems when it is used in a fashion that makes a directory based environment behave as dynamic environments. We should help users by making it an error to use this. It plays a role in dynamic environments in 3.x, so this can not be fixed until 4.0 because it is a breaking change otherwise. When startin... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubs
Jira (PUP-3162) Block $environment in directory based environment configuration settings
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3162 Block $environment in directory based environment configuration settings Change By: Joshua Partlow Assignee: Joshua Partlow Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3188) Puppet module tool no longer processes files starting with a period as erb
Title: Message Title
Brandon High commented on an issue
Re: Puppet module tool no longer processes files starting with a period as erb
Downloaded https://github.com/garethr/puppet-module-skeleton/blob/master/skeleton/.fixtures.yml.erb , replaced my ~/.puppet/var/puppet-module/skeleton, ran puppet module generate on master @ HEAD, found .fixtures.yml file in generated module: https://gist.github.com/highb/2c8ce45fb0b1087f3c89 . It appears the metadata.name was properly substituted by ERB. I notice there is an inline # {source_dir}
, which was not substituted, but as far as I know, ERB requires everything that will be evaluated to be contained within ERB brackets. Gareth Rushgrove, could you provide more details about what this file is supposed to look like after it has been correctly processed?
Add Comment
Puppet / PUP-3188
Puppet module tool no longer processes files starting with a period as erb
The following commit changed the behaviour of the Puppet module tool generator: https://github.com/puppetlabs/puppet/commit/9202651f547c96e1a766d04c00a7691a3d383754 Prior to that commit any file that ended in .erb was processed as a template. After that commit any file that started with a period was no longer processed. The reason why this is rel...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3126) Update win32-service gem to 0.8.6+
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3126 Update win32-service gem to 0.8.6+ Change By: Josh Cooper Fix Version/s: 3.7.1 Fix Version/s: 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3126) Update win32-service gem to 0.8.6+
Title: Message Title Josh Cooper commented on an issue Re: Update win32-service gem to 0.8.6+ Bumping to 4.0 Add Comment Puppet / PUP-3126 Update win32-service gem to 0.8.6+ A new version of the win32-service gem has come out that incorporates the changes for https://github.com/djberg96/win32-service/pull/18, https://github.com/djberg96/win32-service/pull/19, and https://github.com/djberg96/win32-service/issues/22. We are vendoring patches now in the puppet-win32-ruby repository, so those will need to be cleaned up as part of... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3162) Block $environment in directory based environment configuration settings
Title: Message Title Joshua Partlow commented on an issue Re: Block $environment in directory based environment configuration settings Nicholas Fagerlund If we go with a whitelist, then based on our current list of settings, only config_version would allow interpolation of $environment. Add Comment Puppet / PUP-3162 Block $environment in directory based environment configuration settings Using interpolation of $environment can cause problems when it is used in a fashion that makes a directory based environment behave as dynamic environments. We should help users by making it an error to use this. It plays a role in dynamic environments in 3.x, so this can not be fixed until 4.0 because it is a breaking change otherwise. When startin... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more
Jira (FACT-692) Facter reports operatingsystemmajrelease incorrectly in Solaris 10
Title: Message Title
William Hopper updated an issue
Facter / FACT-692
Facter reports operatingsystemmajrelease incorrectly in Solaris 10
Change By:
William Hopper
Prior to Facter 2.2.0, the operatingsystemrelease facts in Solaris 10 resolved as follows:{noformat}operatingsystemmajrelease => 10operatingsystemrelease => 10_u11{noformat}After the release, the major release resolution changed to:{noformat}operatingsystemmajrelease => 10_u11operatingsystemrelease => 10_u11{noformat} (Added for clarity):The output of Facter in Solaris 10 for these facts should be:{noformat}operatingsystemmajrelease => 10operatingsystemrelease => 10_u11 (where uX depends on the minor release. Our testing environments happen to be 10_u11){noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-683) facter id broken on solaris10 as root
Title: Message Title
William Hopper commented on an issue
Re: facter id broken on solaris10 as root
From Rahul Gopinath: the package name is SUNWxcu4 (that provides the xpg4 utilities)
Add Comment
Facter / FACT-683
facter id broken on solaris10 as root
installed from source at SHA 5994c22 {code} -bash-3.2# which facter /opt/csw/bin/facter -bash-3.2# facter /usr/bin/id: illegal option -- n Usage: id [-ap] [user] architecture => i86pc {code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-683) facter id broken on solaris10 as root
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Facter / FACT-683 facter id broken on solaris10 as root Change By: Eric Thompson Assignee: Rahul Gopinath Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-683) facter id broken on solaris10 as root
Title: Message Title Eric Thompson updated an issue Facter / FACT-683 facter id broken on solaris10 as root Change By: Eric Thompson QA Contact: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-692) Facter reports operatingsystemmajrelease incorrectly in Solaris 10
Title: Message Title Eric Thompson updated an issue Facter / FACT-692 Facter reports operatingsystemmajrelease incorrectly in Solaris 10 Change By: Eric Thompson QA Contact: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3136) Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-3136 Intermittent acceptance failure in resource/service/ticket_14297_handle_upstart.rb Change By: Andy Parker Assignee: Andy Parker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3205) Puppet 3.7.1 2014-09-11 Release
Title: Message Title Andy Parker updated an issue Puppet / PUP-3205 Puppet 3.7.1 2014-09-11 Release Change By: Andy Parker Sprint: 2014-09-17 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3205) Puppet 3.7.1 2014-09-11 Release
Title: Message Title Andy Parker updated an issue Puppet / PUP-3205 Puppet 3.7.1 2014-09-11 Release Change By: Andy Parker Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3219) Docs pushed
Title: Message Title Andy Parker created an issue Puppet / PUP-3219 Docs pushed Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 09/Sep/14 10:43 AM Priority: Normal Reporter: Andy Parker 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.1.4#6159-sha1:44eaede)
Jira (PUP-3188) Puppet module tool no longer processes files starting with a period as erb
Title: Message Title Brandon High commented on an issue Re: Puppet module tool no longer processes files starting with a period as erb I'm going to take a look at fixing this today. Add Comment Puppet / PUP-3188 Puppet module tool no longer processes files starting with a period as erb The following commit changed the behaviour of the Puppet module tool generator: https://github.com/puppetlabs/puppet/commit/9202651f547c96e1a766d04c00a7691a3d383754 Prior to that commit any file that ended in .erb was processed as a template. After that commit any file that started with a period was no longer processed. The reason why this is rel... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3216) Push tag
Title: Message Title Andy Parker created an issue Puppet / PUP-3216 Push tag Issue Type: Sub-task Assignee: Melissa Stone Created: 09/Sep/14 10:43 AM Priority: Normal Reporter: Andy Parker 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 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3217) Packages pushed
Title: Message Title Andy Parker created an issue Puppet / PUP-3217 Packages pushed Issue Type: Sub-task Assignee: Melissa Stone Created: 09/Sep/14 10:43 AM Priority: Normal Reporter: Andy Parker 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. Dependencies:
Jira (PUP-3220) Send out announcements
Title: Message Title Andy Parker created an issue Puppet / PUP-3220 Send out announcements Issue Type: Sub-task Assignee: Eric Sorenson Created: 09/Sep/14 10:43 AM Priority: Normal Reporter: Andy Parker Melissa Stone: update the release google spreadsheet. Update the MSI build targets in the Puppet repo in ext/build_defaults.yaml. This needs to be done for any projects that are to get into the MSI (facter and hiera as of 8/2014) Send the drafted release notes email. If final send to puppet-announce and specific distribution lists (e.g. puppet to puppet-users & puppet-dev). Make a PSA on IRC letting those kiddos know about the new release. Something along the lines of "PSA: facter 1.7.3 now available" Dependencies: Prepare long form release notes and short form release story Packages pushed
Jira (PUP-3218) Update the downloads page
Title: Message Title Andy Parker created an issue Puppet / PUP-3218 Update the downloads page Issue Type: Sub-task Assignee: Melissa Stone Created: 09/Sep/14 10:43 AM Priority: Normal Reporter: Andy Parker Update downloads page Update misc/download-options to reflect the new builds you just pushed and also make sure they're displayed. It's a good idea to make sure this looks like it's supposed to NOTE: this page will hopefully be deprecated soon. The idea is that docs with update their documentation to include "latest release version" and where to download files. This page will then be changed to redirect to docs.puppetlabs.com and will no longer need updating. Dependencies: Go / No Go meeting (Status - Ship it!) Add Comment
Jira (PUP-3221) Close all resolved tickets in Jira
Title: Message Title Andy Parker created an issue Puppet / PUP-3221 Close all resolved tickets in Jira Issue Type: Sub-task Assignee: Andy Parker Created: 09/Sep/14 10:43 AM Priority: Normal Reporter: Andy Parker Close any tickets that have been resolved for the release. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%223.7.1%22%20AND%20status%20%3D%20Resolved There is a bulk edit at the top (a gear with the word "Tools"). Should you decide to take this route: Select Bulk Change - All # issues Step 1 - choose all relevant issues (likely all of them) Step 2 - Select "Transition Issues" Step 3 - Select "Closed" Step 4 - Select "Fixed" in Change Resolution. View what is about to change and confirm it. Then commit the change. Dependencies: Packages pushed
Jira (FACT-683) facter id broken on solaris10 as root
Title: Message Title
Eric Thompson commented on an issue
Re: facter id broken on solaris10 as root
re: William Hopper: fact in question [...] is actually the gid fact, and it doesn't resolve on our vcloud vms because they don't have the XPG4 utilities present
The xpg4 stuff is not part of slim-install.
Add Comment
Facter / FACT-683
facter id broken on solaris10 as root
installed from source at SHA 5994c22 {code} -bash-3.2# which facter /opt/csw/bin/facter -bash-3.2# facter /usr/bin/id: illegal option -- n Usage: id [-ap] [user] architecture => i86pc {code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3215) Go/no-go meeting
Title: Message Title Andy Parker created an issue Puppet / PUP-3215 Go/no-go meeting Issue Type: Sub-task Assignee: Andy Parker Created: 09/Sep/14 10:43 AM Priority: Normal Reporter: Andy Parker 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 Add Comment This message was sent by Atlassian JIRA (v6.1.
Jira (PUP-3214) Smoke test packages
Title: Message Title Andy Parker created an issue Puppet / PUP-3214 Smoke test packages Issue Type: Sub-task Assignee: Andy Parker Created: 09/Sep/14 10:43 AM Priority: Normal Reporter: Andy Parker 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). 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. If your smoke testing includes MSIs, you will generally test on other platforms first and when that is looking good, ping the Release Engineer that built the other packages to move forward with MSIs (they require tags to be pushed). This ticket doesn't close until all chosen platforms (including MSIs) have been tested. When all platforms picked have been smoke tested, move this ticket to done.
Jira (PUP-3188) Puppet module tool no longer processes files starting with a period as erb
Title: Message Title Brandon High assigned an issue to Brandon High Puppet / PUP-3188 Puppet module tool no longer processes files starting with a period as erb Change By: Brandon High Assignee: Gareth Rushgrove Brandon High Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3209) Update version number in source
Title: Message Title
Andy Parker created an issue
Puppet / PUP-3209
Update version number in source
Issue Type:
Sub-task
Assignee:
Andy Parker
Created:
09/Sep/14 10:43 AM
Priority:
Normal
Reporter:
Andy Parker
Bump VERSION in lib/ {#project}
/version.rb 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?
Is there a commit for every JIRA ticket targeted at the release?
Jira (PUP-3205) Puppet 3.7.1 2014-09-11 Release
Title: Message Title Andy Parker created an issue Puppet / PUP-3205 Puppet 3.7.1 2014-09-11 Release Issue Type: Task Assignee: Release Engineering Created: 09/Sep/14 10:43 AM Priority: Normal Reporter: Andy Parker Puppet 3.7.1 2014-09-11 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 (PUP-3207) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Andy Parker created an issue Puppet / PUP-3207 Is there a JIRA ticket targeted at the release for every commit? Issue Type: Sub-task Assignee: Andy Parker Created: 09/Sep/14 10:43 AM Priority: Normal Reporter: Andy Parker Ensure all tickets referenced in the commit log have a bug targeted at the release git log .. look through, and make sure that if there is a JIRA ticket number referenced in any of the commits, that ticket is targeted at the release Also, make sure the code itself is sane, that you understand why the change was made, etc. etc. ticketmatch.rb script is a ruby script that helps with "Is there a JIRA ticket targeted at the release for every commit?" and "Is there a commit for every JIRA ticket targeted at the release?" (it beats doing it manually, but requires manual steps and hacking the script for the specific release)
Jira (PUP-3212) Prepare long form release notes and short form release story
Title: Message Title Andy Parker created an issue Puppet / PUP-3212 Prepare long form release notes and short form release story Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 09/Sep/14 10:43 AM Priority: Normal Reporter: Andy Parker Collaborating with product for release story Dependencies: Is there a JIRA ticket targeted at the release for every commit? Is there a commit for every JIRA ticket targeted at the release? Add Comment This messa
Jira (PUP-3206) Is the code ready for release?
Title: Message Title Andy Parker created an issue Puppet / PUP-3206 Is the code ready for release? Issue Type: Sub-task Assignee: Andy Parker Created: 09/Sep/14 10:43 AM Priority: Normal Reporter: Andy Parker 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%20PUP%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%223.7.1%22 Add Com
Jira (FACT-683) facter id broken on solaris10 as root
Title: Message Title Eric Thompson updated an issue Facter / FACT-683 facter id broken on solaris10 as root Change By: Eric Thompson Assignee: Eric Thompson Rahul Gopinath Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3213) Tag the release and create packages
Title: Message Title
Andy Parker created an issue
Puppet / PUP-3213
Tag the release and create packages
Issue Type:
Sub-task
Assignee:
Melissa Stone
Created:
09/Sep/14 10:43 AM
Priority:
Normal
Reporter:
Andy Parker
Tag and create packages
Developer provides the SHA - Andy Parker - 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.
Make sure you look over the code that has changed since the previous release so we k
Jira (PUP-3210) Merge master into stable
Title: Message Title Andy Parker created an issue Puppet / PUP-3210 Merge master into stable Issue Type: Sub-task Assignee: Andy Parker Created: 09/Sep/14 10:43 AM Priority: Normal Reporter: Andy Parker 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 git checkout stable git rebase upstream/stable git merge master --no-ff --log Once that looks good: git push origin git push upstream After merging to stable, the jobs on jenkins may require updates (spec, acceptance, etc) when you merge master into stable. Please ensure that the jenkins jobs are updated if necessary. Dependencies: Is the code ready for release? Is there a commit for every JIRA ticket targeted at the release?
Jira (PUP-3208) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Andy Parker created an issue Puppet / PUP-3208 Is there a commit for every JIRA ticket targeted at the release? Issue Type: Sub-task Assignee: Andy Parker Created: 09/Sep/14 10:43 AM Priority: Normal Reporter: Andy Parker Ensure all tickets targeted at the release have a corresponding commit git log .. This time, look through tickets targeted at this release in JIRA, and compare it to the commit log, looking for the corresponding numbers ticketmatch.rb script is a ruby script that helps with "Is there a JIRA ticket targeted at the release for every commit?" and "Is there a commit for every JIRA ticket targeted at the release?" (it beats doing it manually, but requires manual steps and hacking the script for the specific release) Add Comment
Jira (PUP-3211) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Andy Parker created an issue Puppet / PUP-3211 Is the Jira tidy-up done for this release and prepared for the next one? Issue Type: Sub-task Assignee: Andy Parker Created: 09/Sep/14 10:43 AM Priority: Normal Reporter: Andy Parker 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.Y', Save as "Introduced in X.Y.Y", click Details, add permission for Everyone 'project = XX AND fixVersion = 'X.Y.Z', Save as "Fixes for X.Y.Z", click Details, add permission for Everyone
Jira (PUP-3202) Release 2.7.X series still adds "--include-dependencies" to gem provider.
Title: Message Title Kylo Ginsberg commented on an issue Re: Release 2.7.X series still adds "--include-dependencies" to gem provider. Sam Kottler are you still taking PRs for 2.7? Add Comment Puppet / PUP-3202 Release 2.7.X series still adds "--include-dependencies" to gem provider. PUP-544 mentions this, and this is actually breaking things for us. This have been deprecated since 2007! http://blog.rubygems.org/2007/11/19/0.9.5-released.html This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3162) Block $environment in directory based environment configuration settings
Title: Message Title Nicholas Fagerlund commented on an issue Re: Block $environment in directory based environment configuration settings And we're gonna disallow $environment in the manifest and modulepath settings in environment.conf, right? That seems sensible, since the whole point of DIRECTORY environments is that having everything more or less in one place removes a layer of hard-to-reason-about indirection. I could see people doing something wild like two directories per environment, which seems like a bad idea. Add Comment Puppet / PUP-3162 Block $environment in directory based environment configuration settings Using interpolation of $environment can cause problems when it is used in a fashion that makes a directory based environment behave as dynamic environments. We should help users by making it an error to use this. It plays a role in dynamic environments in 3.x, so this can not be fixed until 4.0 because it is a breaking change otherwise. When startin... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this g
Jira (PUP-3162) Block $environment in directory based environment configuration settings
Title: Message Title Nicholas Fagerlund commented on an issue Re: Block $environment in directory based environment configuration settings config_version is the only legit one I can think of. I read back through the list of important settings and nothing else seemed relevant. Add Comment Puppet / PUP-3162 Block $environment in directory based environment configuration settings Using interpolation of $environment can cause problems when it is used in a fashion that makes a directory based environment behave as dynamic environments. We should help users by making it an error to use this. It plays a role in dynamic environments in 3.x, so this can not be fixed until 4.0 because it is a breaking change otherwise. When startin... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, vi
Jira (PUP-3061) Upgrade win32-eventlog to 0.6.2+ once it is released
Title: Message Title Josh Cooper commented on an issue Re: Upgrade win32-eventlog to 0.6.2+ once it is released We're still waiting on the gem to be published, bumping to 4.0, if/when it's released, we can pull into a future 3.7.x release Add Comment Puppet / PUP-3061 Upgrade win32-eventlog to 0.6.2+ once it is released This will incorporate https://github.com/djberg96/win32-eventlog/pull/10 fix that we need to upgrade the gems locally in puppet. Following that up we'll need to remove the patches from the puppet-win32-ruby repository.Remove the guards put in with https://github.com/puppetlabs/puppet/pull/2991 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-683) facter id broken on solaris10 as root
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Facter / FACT-683 facter id broken on solaris10 as root Change By: Eric Thompson Assignee: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3061) Upgrade win32-eventlog to 0.6.2+ once it is released
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3061 Upgrade win32-eventlog to 0.6.2+ once it is released Change By: Josh Cooper Fix Version/s: 3.7.1 Fix Version/s: 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3061) Upgrade win32-eventlog to 0.6.2+ once it is released
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-3061 Upgrade win32-eventlog to 0.6.2+ once it is released Change By: Josh Cooper Assignee: Kylo Ginsberg Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3186) Puppetmaster removes /etc/puppet/environments/production if it's a link rather than a directory
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3186 Puppetmaster removes /etc/puppet/environments/production if it's a link rather than a directory Change By: Britt Gresham Assignee: Britt Gresham Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3162) Block $environment in directory based environment configuration settings
Title: Message Title Joshua Partlow commented on an issue Re: Block $environment in directory based environment configuration settings Talking with Andy and Henrik this morning, we're considering changing to a whitelist of settings we allow $environment to be interpolated in, rather than proscribing a few specific settings. At the moment, the only setting we can think of that you ought to be able to interpolate $environment in when using directory environments is: config_version Can anyone think of any others? Eric Sorenson Nicholas Fagerlund Any thoughts on this? We also agreed that we don't want to halt the puppetmaster on startup, because of how difficult it is to trace the error in a passenger setup (due to the html rack error response). Henrik brought up the idea of returning an invalid environment (perhaps with a single manifest that fails compilation) if the environment settings are misconfigured? Still need to think that idea through. Add Comment Puppet / PUP-3162 Block $environment in directory based environment configuration settings Using interpolation of $environment can cause problems when it is used in a fashion that makes a directory based environment behave as dynamic environments. We should help users by making it an error to use this. It plays a role in dynamic environments in 3.x, so this can not be fixed until 4.0 because it is a breaking change otherwise. When startin...
