Jira (PUP-1965) Clients are hung when server has intermittent service
Title: Message Title Sam McLeod updated an issue Puppet / PUP-1965 Clients are hung when server has intermittent service Change By: Sam McLeod Comment: We have this issue as well.We can reproduce it on Puppet Enterprise 2018.1 and CentOS 7.5 clients. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1965) Clients are hung when server has intermittent service
Title: Message Title Sam McLeod commented on PUP-1965 Re: Clients are hung when server has intermittent service We have this issue as well. We can reproduce it on Puppet Enterprise 2018.1 and CentOS 7.5 clients. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6510) selmodule provider should only list modules once
Title: Message Title Sam McLeod updated an issue Puppet / PUP-6510 selmodule provider should only list modules once Change By: Sam McLeod Affects Version/s: PUP 4.10.8 Affects Version/s: PUP 5.3.2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6510) selmodule provider should only list modules once
Title: Message Title Sam McLeod updated an issue Puppet / PUP-6510 selmodule provider should only list modules once Change By: Sam McLeod Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6510) selmodule provider should only list modules once
Title: Message Title Sam McLeod commented on PUP-6510 Re: selmodule provider should only list modules once This has been unresolved for a long time now - can we please get a fix for this Puppet? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6739) Error running puppet with non-existent and non-default environment
Title: Message Title Sam McLeod commented on PUP-6739 Re: Error running puppet with non-existent and non-default environment Good to know Martijn Pepping thanks for the update! Perhaps then - the Puppetlabs documentation needs to be updated to reflect this? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6739) Error running puppet with non-existent and non-default environment
Title: Message Title Sam McLeod commented on PUP-6739 Re: Error running puppet with non-existent and non-default environment I've just found a repeatable workaround for this bug. Simply creating the environment directory does not work (`/etc/puppetlabs/code/environment/`) however if you copy the `production` environment's directory and it's substructure - it does seem to work: ``` cp -a /etc/puppetlabs/code/environment/production /etc/puppetlabs/code/environment/ puppet agent -t ... So, while it's not a fix, this hopefully will serve as a temporary workaround until this bug is squashed! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title Sam McLeod commented on PUP-1054 Re: Services should support 'reload' in addition to 'restart' Just heard back from Puppet support: I'm so sorry for the delay, and I thank you for patience with this ticket. I was able to speak to our product managers about the feature request https://tickets.puppetlabs.com/browse/PUP-1054. The feature is on our roadmap, but we don't have a timeline for when it will be completed. We do regularly go through and evaluate feature requests to reprioritize them and I have brought this up with the engineering team to take look. The best place to look for status updates will be in that JIRA ticket. Please let me know if you have any questions or concerns. if not, is it alright to close this ticket? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6739) Error running puppet with non-existent and non-default environment
Title: Message Title Sam McLeod commented on PUP-6739 Re: Error running puppet with non-existent and non-default environment This bug is very annoying. Our Puppet 3 (Open Source) workflow was: 1. Create branch (r10k environment) 2. Set nodes to run off branch by setting `environment = ` in the nodes puppet.conf 3. Develop on and test branch 4. Merge branch in to production Now the only way we can reliably test branches is to enable puppet on the node, do interactive puppet runs passing `--environment=` and disable puppet again so it doesn't default back to running off production. I tried creating the branch directory in `/etc/puppetlabs/code/environments/` as suggested above, but that just results in no-change puppet runs. I'm really surprised this has gone unfixed for so long. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title Sam McLeod commented on PUP-1054 Re: Services should support 'reload' in addition to 'restart' I think you should check your attitude, it’s neither constructive or appreciated. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title Sam McLeod commented on PUP-1054 Re: Services should support 'reload' in addition to 'restart' Matthew Patton, respectfully I think you're missing the point debatably the most common use of reload / SIGHUP on modern Linux systems. I agree with Colin Alston, a great deal of functionality within Puppet or indeed any automation platform or subsystem 'could be dangerous' if used unwisely. If you take the stance that people should only use software in one, specific way you'll end up with an inflexible system and in this case - product that doesn't work for many people. When it comes to systems / platform automation and configuration there is (likely more than in any other field of deployment) a diverse range of operating modes with a varying range of scope that the software may be deployed. — One example (of many I can think of) is PostgreSQL, perhaps your solution requires the use of an ACID compliant database - or maybe it's just what your organisation uses as a SOE. PostgreSQL like a lot of software has configuration that can be changed online without needing to restart the service, for example - you might dynamically adjust the size of various memory buffers based on the number of clients deployed to a cluster etc... you don't need to restart your database server for every change and there could be many undesired side affects of doing so, not just disconnections if not handled correctly but also things like loss of memory caching and live query planner optimisations that could affect performance. — What might be useful is a meta-parameter to Service Reload which could take a command to test that reload will work for a specific change and if it doesn't exit 0, subsequent puppet runs will by effect continue to show as failed rather than applying the failed configuration, issuing a Service Reload, failing once and being forgotten about. You can do dangerous things with many commands in Puppet (or indeed any configuration management / automation system), it doesn't mean you shouldn't rule out that the commands that might lead to such situations completely - you'd end up with an inflexible, one-size-fits-none product that would suit very few customers needs. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae25
Jira (PUP-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title Sam McLeod commented on PUP-1054 Re: Services should support 'reload' in addition to 'restart' Is this ticket able to be actioned? Still badly need this unless there's a new way to handle reloads instead of restarts that we haven't come across. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7491) Puppet module won't upload to puppet forge due to false positive error on author
Title: Message Title
Sam McLeod updated an issue
Puppet / PUP-7491
Puppet module won't upload to puppet forge due to false positive error on author
Change By:
Sam McLeod
!Screen Shot 2017-05-03 at 11.37.48 am.jpg |thumbnail !Although the author is set to my username, sammcj:https://github.com/sammcj/puppet-luks/blob/master/metadata.json#L4 :```json{ "name": "puppet-luks", "version": "0.1.2", "author": "sammcj", "summary": "Puppet module for managing LUKS encrypted volumes", "license": "Apache 2.0", "source": "https://github.com/sammcj/puppet-luks.git", "project_page": "https://github.com/sammcj/puppet-luks", "issues_url": "https://github.com/sammcj/puppet-luks/issues", "operatingsystem_support": { "operatingsystem":"RedHat", "operatingsystemrelease":[ "7.0", "7.1", "7.2" ]}, "dependencies": [{"name":"puppetlabs-stdlib","version_requirement":">= 1.0.0"}], "data_provider": "hiera"}```
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7491) Puppet module won't upload to puppet forge due to false positive error on author
Title: Message Title
Sam McLeod created an issue
Puppet / PUP-7491
Puppet module won't upload to puppet forge due to false positive error on author
Issue Type:
Bug
Affects Versions:
PUP 4.10.0, PUP 4.9.4, PUP 4.9.3
Assignee:
Unassigned
Attachments:
Screen Shot 2017-05-03 at 11.37.48 am.jpg
Components:
Modules
Created:
2017/05/02 6:43 PM
Priority:
Normal
Reporter:
Sam McLeod
Although the author is set to my username, sammcj:
https://github.com/sammcj/puppet-luks/blob/master/metadata.json#L4 :
```json { "name": "puppet-luks", "version": "0.1.2", "author": "sammcj", "summary": "Puppet module for managing LUKS encrypted volumes", "license": "Apache 2.0", "source": "https://github.com/sammcj/puppet-luks.git", "project_page": "https://github.com/sammcj/puppet-luks", "issues_url": "https://github.com/sammcj/puppet-luks/issues", "operatingsystem_support": { "operatingsystem":"RedHat", "o
Jira (PUP-7490) puppet / puppet module build fails with ruby null error
Title: Message Title Sam McLeod commented on PUP-7490 Re: puppet / puppet module build fails with ruby null error It appears that puppet relies on an old / specific version of the openssl gem, but isn't specifying to use that exact version when running. If I comment out line 104 in `money_patches.rb` the command works. ```bash ~/git/puppet-luks on master puppet module build . Notice: Building /Users/samm/git/puppet-luks for release Module built: /Users/samm/git/puppet-luks/pkg/puppet-luks-0.1.2.tar.gz ``` Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7490) puppet / puppet module build fails with ruby null error
Title: Message Title Sam McLeod commented on PUP-7490 Re: puppet / puppet module build fails with ruby null error File /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util/monkey_patches.rb Line 104: ```ruby DEFAULT_PARAMS[:ciphers] << ':!SSLv2' ``` Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7490) puppet / puppet module build fails with ruby null error
Title: Message Title Sam McLeod updated an issue Puppet / PUP-7490 puppet / puppet module build fails with ruby null error Change By: Sam McLeod Module source: https://github.com/sammcj/puppet-luks ```rubypuppet module build --help/Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util/monkey_patches.rb:104:in `': undefined method `<<' for nil:NilClass (NoMethodError) from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util/monkey_patches.rb:98:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util.rb:17:in `require' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util.rb:17:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util.rb:16:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util.rb:15:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet.rb:14:in `require' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet.rb:14:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util/command_line.rb:12:in `require' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util/command_line.rb:12:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/bin/puppet:4:in `require' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/bin/puppet:4:in `' from /usr/local/bin/puppet:23:in `load' from /usr/local/bin/puppet:23:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/bin/ruby_executable_hooks:15:in `eval' from /Users/samm/.rvm/gems/ruby-2.4.1/bin/ruby_executable_hooks:15:in `'``rubypuppet --version/Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util/monkey_patches.rb:104:in `': undefined method `<<' for nil:NilClass (NoMethodError) from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util/monkey_patches.rb:98:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util.rb:17:in `require' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util.rb:17:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util.rb:16:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util.rb:15:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet.rb:14:in `require' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet.rb:14:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util/command_line.rb:12:in `require' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util/command_line.rb:12:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/bin/puppet:4:in `require' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/bin/puppet:4:in `' from /usr/local/bin/puppet:23:in `load' from /usr/local/bin/puppet:23:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/bin/ruby_executable_hooks:15:in `eval' from /Users/samm/.rvm/gems/ruby-2.4.1/bin/ruby_executable_hooks:15:in `'``bashgem list*** LOCAL GEMS ***ast (2.3.0)bigdecimal (default: 1.3.0)bundler (1.14.6)bundler-unload (1.0.2)CFPropertyList (2.2.8)did_you_mean (1.1.0)diff-lcs (1.3)executable-hooks (1.3.2)facter (2.4.6 ruby universal-darwin)fast_gettext (1.1.0)gem-wrappers (1.2.7)gettext (3.2.2)gettext-setup (0.24)hiera (3.3.1)io-console (default: 0.4.6)json
Jira (PUP-7490) puppet / puppet module build fails with ruby null error
Title: Message Title Sam McLeod updated an issue Puppet / PUP-7490 puppet / puppet module build fails with ruby null error Change By: Sam McLeod ```rubypuppet module build --help/Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util/monkey_patches.rb:104:in `': undefined method `<<' for nil:NilClass (NoMethodError) from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util/monkey_patches.rb:98:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util.rb:17:in `require' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util.rb:17:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util.rb:16:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util.rb:15:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet.rb:14:in `require' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet.rb:14:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util/command_line.rb:12:in `require' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util/command_line.rb:12:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/bin/puppet:4:in `require' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/bin/puppet:4:in `' from /usr/local/bin/puppet:23:in `load' from /usr/local/bin/puppet:23:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/bin/ruby_executable_hooks:15:in `eval' from /Users/samm/.rvm/gems/ruby-2.4.1/bin/ruby_executable_hooks:15:in `'``rubypuppet --version/Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util/monkey_patches.rb:104:in `': undefined method `<<' for nil:NilClass (NoMethodError) from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util/monkey_patches.rb:98:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util.rb:17:in `require' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util.rb:17:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util.rb:16:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util.rb:15:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet.rb:14:in `require' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet.rb:14:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util/command_line.rb:12:in `require' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util/command_line.rb:12:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/bin/puppet:4:in `require' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/bin/puppet:4:in `' from /usr/local/bin/puppet:23:in `load' from /usr/local/bin/puppet:23:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/bin/ruby_executable_hooks:15:in `eval' from /Users/samm/.rvm/gems/ruby-2.4.1/bin/ruby_executable_hooks:15:in `'``` ```bashgem list*** LOCAL GEMS ***ast (2.3.0)bigdecimal (default: 1.3.0)bundler (1.14.6)bundler-unload (1.0.2)CFPropertyList (2.2.8)did_you_mean (1.1.0)diff-lcs (1.3)executable-hooks (1.3.2)facter (2.4.6 ruby universal-darwin)fast_gettext (1.1.0)gem-wrappers (1.2.7)gettext (3.2.2)gettext-setup (0.24)hiera (3.3.1)io-console (default: 0.4.6)json (2.1.0, default: 2.0.2)json_pure (1.8.6)locale (2.1
Jira (PUP-7490) puppet / puppet module build fails with ruby null error
Title: Message Title Sam McLeod created an issue Puppet / PUP-7490 puppet / puppet module build fails with ruby null error Issue Type: Bug Affects Versions: PUP 4.10.0, PUP 4.9.4, PUP 4.9.3 Assignee: Unassigned Created: 2017/05/02 6:27 PM Environment: ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-darwin16] ruby 2.4.0 ruby 2.3.3 macOS 10.12.4 (16E195) Labels: ruby bug Priority: Normal Reporter: Sam McLeod ```ruby puppet module build --help /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util/monkey_patches.rb:104:in `': undefined method `<<' for nil:NilClass (NoMethodError) from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util/monkey_patches.rb:98:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util.rb:17:in `require' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util.rb:17:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet/util.rb:16:in `' from /Users/samm/.rvm/gems/ruby-2.4.1/gems/puppet-4.10.0/lib/puppet
Jira (PUP-3386) Puppet Module Gem Dependency Metadata and Installation
Title: Message Title Sam McLeod commented on PUP-3386 Re: Puppet Module Gem Dependency Metadata and Installation Howdy, Just wondering if there's any update on this issue? We've just run up against it when needing to install a gem into puppet's environment as part of a provider. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4480) Jira *very* slow to work with
Title: Message Title Sam McLeod created an issue Puppet / PUP-4480 Jira *very* slow to work with Issue Type: Bug Assignee: Unassigned Created: 2015/04/28 7:18 PM Priority: Normal Reporter: Sam McLeod FYI - Jira is VERY slow in Australia - is there any option from your end to use a CDN for it or something? Every click is painful, it feels like an old laggy java application! Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title Sam McLeod commented on an issue Re: Services should support 'reload' in addition to 'restart' Any update on this? It's a pretty critical feature that's missing... Add Comment Puppet / PUP-1054 Services should support 'reload' in addition to 'restart' currently if a service needs kicking (e.g. a config file changed) you can notify the service, but this leads to a restart. It would be nice if a reload was done if the service was already running (although I suppose there are bound to be some services which require restarts for some files, reloads for others). A reload would be far faster (shorter ser... 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-2348) Puppet run randomly fails with "Unknown function at on node "
Title: Message Title Sam McLeod commented on an issue Re: Puppet run randomly fails with "Unknown function at on node " Hi Henrik, Thanks for your reply. Could you please link to the bugfixes in 3.6.1 that you think may fix this bug? Since puppet 3.x there seems to have been a lot more bugs that continue from release to release without being fixed. Add Comment Puppet / PUP-2348 Puppet run randomly fails with "Unknown function at on node " After upgrading puppetmaster to 3.5.1 we started experiencing random manifests failures. A given (manifest, function, node) tuple can work several times and then fail, only to succeed on the next run (with the exact same code base). Running the agent and the master in debug does not bring any more information on why the function cannot be found. ... 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
Jira (PUP-2348) Puppet run randomly fails with "Unknown function at on node "
Title: Message Title Sam McLeod commented on an issue Re: Puppet run randomly fails with "Unknown function at on node " Any movement with this? It's currently preventing us from upgrading puppet on 300+ nodes. Add Comment Puppet / PUP-2348 Puppet run randomly fails with "Unknown function at on node " After upgrading puppetmaster to 3.5.1 we started experiencing random manifests failures. A given (manifest, function, node) tuple can work several times and then fail, only to succeed on the next run (with the exact same code base). Running the agent and the master in debug does not bring any more information on why the function cannot be found. ... 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-1214) File resources: Make source/content parameters and the file/template functions consistent.
Title: Message Title Sam McLeod commented on an issue Re: File resources: Make source/content parameters and the file/template functions consistent. Any update on this? It looks like it's been forgotten about. Add Comment Puppet / PUP-1214 File resources: Make source/content parameters and the file/template functions consistent. We have four main ways we can specify file content in a file resource. 1. The source parameter 2. The content parameter 3. The file function 4. The template function These behave inconsistently in the following ways. The source parameter, file function and template function all can take an array. For source/file, the first file that exists wil... 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-2028) Can't ensure => latest with ensure_packages
Title: Message Title Sam McLeod created an issue Puppet / PUP-2028 Can't ensure => latest with ensure_packages Issue Type: Bug Assignee: Andy Parker Components: Modules Created: 24/Mar/14 5:12 PM Labels: stdlib Priority: Normal Reporter: Sam McLeod Unable to ensure => latest on packages with ensure_packages from puppetlabs_stdlib https://github.com/puppetlabs/puppetlabs-stdlib/blob/master/lib/puppet/parser/functions/ensure_packages.rb Add Comment
Jira (PUP-1054) Services should support 'reload' in addition to 'restart'
Title: Message Title Sam McLeod commented on an issue Re: Services should support 'reload' in addition to 'restart' It seems that I come across the need for this every month or so. Add Comment Puppet / PUP-1054 Services should support 'reload' in addition to 'restart' currently if a service needs kicking (e.g. a config file changed) you can notify the service, but this leads to a restart. It would be nice if a reload was done if the service was already running (although I suppose there are bound to be some services which require restarts for some files, reloads for others). A reload would be far faster (shorter ser... 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/groups/opt_out.
