Jira (PUP-11188) HTTP redirect not working on Windows
Title: Message Title
Chris Denneen created an issue
Puppet / PUP-11188
HTTP redirect not working on Windows
Issue Type:
Bug
Affects Versions:
PUP 7.7.0, PUP 6.23.0
Assignee:
Unassigned
Components:
Windows
Created:
2021/07/26 9:03 AM
Priority:
Major
Reporter:
Chris Denneen
Noticed this with archive and remote_file modules trying to download file from JFrog SaaS which performs a Direct Object redirect to the s3 bucket via a Signed URL. This seems to work fine on Mac/Linux but not on Windows. Also looks like in Puppet 6,7 moving this towards the file resource it still doesn't work with the Puppet HTTP client either. Not sure if this is a ruby upstream issue or bug for Puppet/Windows
{{Error: Could not set 'file' on ensure: Error 400 on SERVER:
encoding="UTF-8"?>
InvalidArgumentOnly one auth mechanism allowed; onl
Jira (PUP-10890) empty lookup_options
Title: Message Title Chris Denneen commented on PUP-10890 Re: empty lookup_options @Josh Cooper the issue is seen when the module has empty hash (I had the old keys actually commented out) and you run a “pdk test unit”. Should be pretty straight forward to reproduce? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.386484.1612558652000.135095.1612614960030%40Atlassian.JIRA.
Jira (PUP-10890) empty lookup_options
Title: Message Title Chris Denneen created an issue Puppet / PUP-10890 empty lookup_options Issue Type: Bug Assignee: Unassigned Created: 2021/02/05 12:57 PM Priority: Normal Reporter: Chris Denneen Doing a test on a module with hiera that has an empty `lookup_options:` will result in errors during unit tests like — Caused by: — NoMethodError: undefined method `each_pair' for nil:NilClass /opt/puppetlabs/pdk/private/puppet/ruby/2.4.0/gems/puppet-5.5.21/lib/puppet/pops/lookup/lookup_adapter.rb:292:in `validate_lookup_options' Add Comment
Jira (PUP-8318) Allow client tools and classifier gem to support parameters
Title: Message Title Chris Denneen commented on PUP-8318 Re: Allow client tools and classifier gem to support parameters Sean McDonald I see you closed that issue but there was no comments on it... still would like the parameters or ENV variables to work if possible... think useful for CI/CD purposes rather than having to mock up a configuration file unnecessarily 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.229070.1515102987000.11198.1580754360144%40Atlassian.JIRA.
Jira (PUP-7541) Explore removing export / collect / virtual / realize syntax
Title: Message Title Chris Denneen commented on PUP-7541 Re: Explore removing export / collect / virtual / realize syntax The issue is when using Puppet Enterprise for example there are packages that are virtual and depending upon how you use collectors this will cause some nasty behavior: Notice: /Stage[main]/Puppet_enterprise::Packages/Package[pe-postgresql-pglogical]/ensure: current_value 'purged', should be 'latest' (noop) Notice: /Stage[main]/Puppet_enterprise::Packages/Package[pe-postgresql-pgrepack]/ensure: current_value 'purged', should be 'latest' (noop) Notice: /Stage[main]/Puppet_enterprise::Packages/Package[pe-java-devel]/ensure: current_value 'purged', should be 'latest' (noop) Notice: /Stage[main]/Puppet_enterprise::Packages/Package[pe-activemq]/ensure: current_value 'purged', should be 'latest' (noop) Notice: /Stage[main]/Puppet_enterprise::Packages/Package[pe-razor-libs]/ensure: current_value 'purged', should be 'latest' (noop) Notice: /Stage[main]/Puppet_enterprise::Packages/Package[pe-razor-server]/ensure: current_value 'purged', should be 'latest' (noop) Notice: Class[Puppet_enterprise::Packages]: Would have triggered 'refresh' from 6 events This is caused by the above example (to make sure Package['yum'] -> Yumrepo<| |> -> Package<| |>) Yumrepo<| |>->Package<| title != 'yum' |> How does one propose to continue to use Collectors (or PQL) to allow for the desired behavior that Yum gets updated before yumrepo which are all applied before all other packages. (Reason Yum has to be updated first is because sometimes features being added to yumrepos ssl, parameters, etc won't work with old versions of yum so the package must be applied first) but you want the yumrepos to be applied before all other packages are attempted to be installed/upgraded. Maybe PE should avoid the use of Virtual Resources? But what's to stop Datadog, Sensu, etc vendors from doing the same. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9407) Don't backup to the local filebucket by default
Title: Message Title Chris Denneen commented on PUP-9407 Re: Don't backup to the local filebucket by default I think the filebucket as it's been implemented it might be okay to remove since honestly I don't think anyone actually uses it. The issue there is I don't think they use it because it isn't a useful feature, sadly I think they don't use it because it's not a very clear feature to use. (or simple with needing to use checksums) If this becomes a clearer/easier feature then I think it actually could be very useful for people. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.291105.154707498.23096.1573151520131%40Atlassian.JIRA.
Jira (PUP-1137) Maintenance task for the filebucket
Title: Message Title
Chris Denneen commented on PUP-1137
Re: Maintenance task for the filebucket
Cleaned up my PE with this suggestion in case anyone has this issue still:
tidy { '/opt/puppetlabs/server/data/puppetserver/bucket':
age => '5w',
recurse => true,
rmdirs => true,
backup => false,
}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1542) Install Facter 3 as a gem
Title: Message Title Chris Denneen commented on FACT-1542 Re: Install Facter 3 as a gem Is there a reason this gem wouldn’t become next release of “facter”? I’m sure there will be many Gem dependencies that are currently pulling down legacy one and would then just flip to downloading this instead having to replace facter with cfacter? 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-2782) Yumrepo target attribute does not work
Title: Message Title Chris Denneen commented on PUP-2782 Re: Yumrepo target attribute does not work Jacob Helwig yes it's just a wrapper around the yumrepo resource https://github.com/voxpupuli/puppet-yum/blob/2ecfb6bf0f9ced94dbb911fcf4faa6e5fec982bc/manifests/init.pp#L130-L132 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-8318) Allow client tools and classifier gem to support parameters
Title: Message Title Chris Denneen created an issue Puppet / PUP-8318 Allow client tools and classifier gem to support parameters Issue Type: New Feature Assignee: Unassigned Created: 2018/01/04 1:56 PM Priority: Normal Reporter: Chris Denneen currently you must use files with token, ca-cert, endpoints for use with: classifier gem puppet job puppet query puppet deploy For use with containers for CI/CD purposes and other scripting tasks... it would be beneficial to use ENV variables or --parameter strings to provide the necessary information if the configuration files or token files aren't available. Carl CaumRyan ColemanThomas Linkin Add Comment
Jira (FACT-1542) Install Facter 3 as a gem
Title: Message Title Chris Denneen commented on FACT-1542 Re: Install Facter 3 as a gem 1,000% Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-6729) NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators
Title: Message Title Chris Denneen commented on PUP-6729 Re: NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators Definitely running into same issue when running via Services, Orchestrator, or even via Cloudformation steps the ACL get's too restrictive that logging in as local Administrator doesn't have permissions to apply/agent run properly. 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-5889) Add a --strict flag to Puppet
Title: Message Title Chris Denneen commented on PUP-5889 Re: Add a --strict flag to Puppet Henrik Lindberg Where would that be? require 'puppetlabs_spec_helper/module_spec_helper' Dir[File.absolute_path(File.dirname(__FILE__) + '/support/*.rb')].each do |f| require f end begin require 'spec_helper_local' rescue LoadError => e handle_error(e) end
Jira (PUP-5889) Add a --strict flag to Puppet
Title: Message Title Chris Denneen commented on PUP-5889 Re: Add a --strict flag to Puppet Henrik Lindberg I know this is old issue but just recently I added the following to my spec testing: if Puppet::Util::Package.versioncmp(Puppet.version, '4.5.0') >= 0 RSpec.configure do |c| c.before :each do Puppet.settings[:strict] = :warning end end end and if I have multiple _spec.rb it seems to work for the first one just the rest it seems to default back to :error If I run the same tests with STRICT_VARIABLES=no they all pass Is there something that would revert this upon subsequent test? Add Comment
Jira (PUP-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Chris Denneen commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Same issue with `sensu_gem` provider with the master branch of sensu/sensu on github (this fixed some other issues for Windows installs that haven't been released to forge). Current `package` installs of `sensu-plugins-windows` using `provider => sensu_gem` install the gem's in puppet/sys/ruby/bin instead of sensu/embedded/bin/ Can this be fixed in LTS as well. 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-5874) Purging doesn't work when a package dependancy is required inside same catalog
Title: Message Title Chris Denneen commented on PUP-5874 Re: Purging doesn't work when a package dependancy is required inside same catalog Branan Riley I know this has been open a while. What's the fix to avoid the iptables_save missing Error being generated? 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-6067) Pip3 provider does not include features from Pip
Title: Message Title
Chris Denneen commented on PUP-6067
Re: Pip3 provider does not include features from Pip
Michael Smith I know it's been a while but wanted to show something. Using 4.7.1 and Ruby 2.3.0.
Currently when I run my tests I get the following output and error:
Error:
Failures:
1) profile_base::amazon supported operating systems on centos-5-x86_64 profile_base::amazon class without any parameters should contain Class[profile_base::amazon] Failure/Error: it { is_expected.to contain_class(puppet_class)} Puppet::PreformattedError: Evaluation Error: Error while evaluating a Resource Statement, Could not autoload puppet/type/package: Could not autoload puppet/provider/package/pip: cannot load such file – xmlrpc/client at /Users/cdenneen/src/gitlab/puppet/profile_base/spec/fixtures/modules/profile_base/manifests/amazon.pp:7:3 output: profile_base::amazon supported operating systems on centos-5-x86_64 profile_base::amazon class without any parameters should contain Class[profile_base::amazon] (FAILED - 1) should compile into a catalogue without dependency cycles should contain Package[aws-sdk] with ensure => "2.1.30" on centos-6-x86_64 profile_base::amazon class without any parameters should contain Class[profile_base::amazon] should compile into a catalogue without dependency cycles should contain Package[aws-sdk] with ensure => "2.1.30" on centos-7-x86_64 profile_base::amazon class without any parameters should contain Class[profile_base::amazon] should compile into a catalogue without dependency cycles should contain Package[aws-sdk] with ensure => "2.1.30" on ubuntu-12.04-x86_64 profile_base::amazon class without any parameters should contain Class[profile_base::amazon] should compile into a catalogue without dependency cycles should contain Package[aws-sdk] with ensure => "2.1.30" on ubuntu-14.04-x86_64 profile_base::amazon class without any parameters should contain Class[profile_base::amazon] should compile into a catalogue without dependency cycles should contain Package[aws-sdk] with ensure => "2.1.30" on ubuntu-16.04-x86_64 profile_base::amazon class without any parameters should contain Class[profile_base::amazon] should compile into a catalogue without dependency cycles should contain Package[aws-sdk] with ensure => "2.1.30" on windows-2012 R2-x64 profile_base::amazon class without any parameters should contain Class[profile_base::amazon] should compile into a catalogue without dependency cycles should contain Package[aws-sdk] with ensure => "2.1.30" If I remove centos 5 from the metadata.json as supported OS the failure just moves to centos 6 for the same class that as you see above passed when 5 was enabled. With CentOS 5 removed: profile_base::amazon supported operating systems on centos-6-x86_64 profile_base::amazon class without any parameters should contain Class[profile_base::amazon] (FAILED - 1) should compile into a catalogue without dependency cycles should contain Package[aws-sdk] with ensure => "2.1.30" on centos-7-x86_64 profile_base::amazon class without any parameters should contain Class[profile_base::amazon] should compile into a catalogue without dependency cycles should contain Package[aws-sdk] with ensure => "2.1.30" on ubuntu-12.04-x86_64 profile_base::amazon class without any parameters should contain Class[profile_base::amazon] should compile into a catalogue without dependency cycles should contain Package[aws-sdk] with ensure => "2.1.30" on ubuntu-14.04-x86_64 profile_base::amazon class without any parameters should contain Class[profile_base::amazon] should compile into a catalogue without dependency cycles should contain Package[aws-sdk] with ensure => "2.1.30" on ubuntu-16.04-x86_64 profile_
Jira (PUP-2782) Yumrepo target attribute does not work
Title: Message Title Chris Denneen commented on PUP-2782 Re: Yumrepo target attribute does not work I know fixing the target to work properly is most important but I was wondering if you look at some of the repo files for like the CentOS legacy 7.x repos as new versions release. They combine a bunch in single repo files. So target would have to be treated more like a "tag" of some sort and files based in that target used to generate based on iteration in a template (so repo file could be single or have 20 in one file) 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 (HI-295) When using hiera to create_resources for puppet, allow to pass puppet template function
Title: Message Title
Chris Denneen commented on HI-295
Re: When using hiera to create_resources for puppet, allow to pass puppet template function
Thanks for the reply Henrik. I was actually curious if there was a way
%{file('profile/logstash.json')}
could evaluate.
My problem was something like:
elasticsearch::templates:
default:
content: '{ "template" : "*", "order" : 1, "settings" : { "index.routing.allocation.require.node_type" : "hot" } } '
logstash:
content: "file('profile/logstash.json')"
And then code like the following:
$templates = hiera_hash('elasticsearch::templates', {})
Jira (HI-295) When using hiera to create_resources for puppet, allow to pass puppet template function
Title: Message Title Chris Denneen commented on HI-295 Re: When using hiera to create_resources for puppet, allow to pass puppet template function This is same issue with using bunch of hiera hashes and using the file() function won't work either. Would be nice if there was a way around this. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6067) Pip3 provider does not include features from Pip
Title: Message Title Chris Denneen commented on PUP-6067 Re: Pip3 provider does not include features from Pip I've added a PUP-6067 branch to repo to reflect the work-around. Can you explain the alternative? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-503) Automatic Parameter Lookup Multi Hierarchy
Title: Message Title
Chris Denneen commented on HI-503
Re: Automatic Parameter Lookup Multi Hierarchy
Henrik, no the above was NOT a typo. Only the class is parameterized... the config is referencing it. The multi-hierarchy only works if realized within the puppet code {...}
and not in the class params (...). If
PUP-5395
fixes this that's fine, just want to confirm we are talking about the same thing.
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-503) Automatic Parameter Lookup Multi Hierarchy
Title: Message Title
Chris Denneen created an issue
Hiera / HI-503
Automatic Parameter Lookup Multi Hierarchy
Issue Type:
New Feature
Affects Versions:
HI 3.0.6
Assignee:
Aaron Armstrong
Components:
Community, PE
Created:
2016/03/15 8:17 AM
Priority:
Normal
Reporter:
Chris Denneen
Currently since 1.x and still in 3.x there is a limitation of multi hierarchy in automatic parameter lookups. Many public component modules found online (including forge) utilize parameterized classes but if someone is using multi-hierarchy merging via deep or deeper merge_behavior this doesn't work and is known/documented limitation. Problem is this is fine probably for 90% of people but those people who are utilizing multi hierarchy lookups or different hiera backends (yaml/eyaml even at same hierarchy level) are now required to open pull requests to change:
class foo ( $config = undef ) {...} class foo::config { $config = $::foo::config } to class foo ( $config = undef ){...}
class foo::config { $config = hiera_hash('foo::config',$::foo::config) }
While this is doable it's a work around for a long time known limitation. Can we correct the limitation so it works within the parameterized class?
Jira (PUP-5683) $puppetversion and other top level variables not present when running tests
Title: Message Title
Chris Denneen commented on PUP-5683
Re: $puppetversion and other top level variables not present when running tests
bash-3.2$ cat manifests/init.pp
class testpuppet {
notice ("Puppet version is ${::puppetversion}")
if versioncmp($::puppetversion, '4.0.0') > 0 {
notice ('Puppet version is greater than 4')
}
assert_type(Undef, $::puppetversion)
Jira (PUP-5683) $puppetversion and other top level variables not present when running tests
Title: Message Title Chris Denneen commented on PUP-5683 Re: $puppetversion and other top level variables not present when running tests According to bundle install it's facter 2.4.4 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5683) String evaluates as Undef
Title: Message Title Chris Denneen commented on PUP-5683 Re: String evaluates as Undef As example shows it's other toplevel variables as well. I've opened bug with rspec-puppet just incase that's where the issue resides. I'm not sure I follow what you mean by "different versions of the testing framework". Does the rspec test work for you? At least we can now agree that it's not my puppet install Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5683) String evaluates as Undef
Title: Message Title Chris Denneen commented on PUP-5683 Re: String evaluates as Undef The apply worked in my example to. Did the spec test work? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5683) String evaluates as Undef
Title: Message Title Chris Denneen commented on PUP-5683 Re: String evaluates as Undef changing to 4.2.1 works: bash-3.2$ export PUPPET_VERSION=4.2.1 bash-3.2$ bundle install Fetching gem metadata from https://rubygems.org/. Fetching version metadata from https://rubygems.org/.. Resolving dependencies... Installing metaclass 0.0.4 Installing CFPropertyList 2.2.8 Using bundler 1.10.6 Installing diff-lcs 1.2.5 Installing puppet-lint 1.1.0 Installing r
Jira (PUP-5683) String evaluates as Undef
Title: Message Title Chris Denneen updated an issue Puppet / PUP-5683 String evaluates as Undef Change By: Chris Denneen Attachment: testpuppet.zip Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5683) String evaluates as Undef
Title: Message Title
Chris Denneen commented on PUP-5683
Re: String evaluates as Undef
Henrik,
There is nothing specific to my install... this is all being freshly built and on multiple machines (rvm, rbenv, 2.1.6, 2.1.7, osx, centos7):
bash-3.2$ bundle exec puppet apply -e 'include testpuppet' --modulepath ../
Notice: Scope(Class[Testpuppet]): Puppet version is 4.3.1
Notice: Scope(Class[Testpuppet]): Puppet version is greater than 4
Notice: Compiled catalog for ctctecmbcden.local in environment production in 0.08 seconds
Notice: Applied catalog in 0.01 seconds
bash-3.2$ more manifests/init.pp
class testpuppet {
notice ("
Jira (PUP-5683) String evaluates as Undef
Title: Message Title Chris Denneen assigned an issue to Henrik Lindberg Puppet / PUP-5683 String evaluates as Undef Change By: Chris Denneen Assignee: Chris Denneen Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5683) String evaluates as Undef
Title: Message Title Chris Denneen commented on PUP-5683 Re: String evaluates as Undef Henrik, If you put that if versioncmp in test file and do a spec test for it should compile you'll reproduce. -Chris Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5683) String evaluates as Undef
Title: Message Title
Chris Denneen commented on PUP-5683
Re: String evaluates as Undef
But it's not just $:puppetversion it's also any sort of evaluation for example in saz-sudo:
if (versioncmp($::sudoversion, '1.7.2p1') < 0) { ... }
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5683) String evaluates as Undef
Title: Message Title Chris Denneen commented on PUP-5683 Re: String evaluates as Undef The test works fine in < 4.3.x so then $::puppetversion was being set and now it isn't anymore? Would "$::puppetversion not set in 4.3.x causing evaluation to undef" be better title? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5683) String evaluates as Undef
Title: Message Title
Chris Denneen commented on PUP-5683
Re: String evaluates as Undef
Fix would be to quote the $::puppetversion variable which seems to work even though stylistically a single variable shouldn't be quoted:
So while the following fails:
if versioncmp($::puppetversion, '4.0.0') >= 0 { ... } This will make it pass tests: if versioncmp("${::puppetversion}", '4.0.0') >= 0 { ... }
But linting WARNS:
WARNING: string containing only a variable
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5683) String evaluates as Undef
Title: Message Title Chris Denneen commented on PUP-5683 Re: String evaluates as Undef Is it possible the following broke it? PUP-4780 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5683) String evaluates as Undef
Title: Message Title
Chris Denneen created an issue
Puppet / PUP-5683
String evaluates as Undef
Issue Type:
Bug
Affects Versions:
PUP 4.3.1, PUP 4.3.0
Assignee:
Unassigned
Created:
2016/01/10 8:10 AM
Environment:
RSpec Testing
Labels:
puppet puppet-agent 4.3.0 testing spec rspec
Priority:
Normal
Reporter:
Chris Denneen
Seems 4.3.0 and 4.3.1 versions are affected:
Failure/Error: it {should compile}
error during compilation: Evaluation Error: Error while evaluating a Function Call, 'versioncmp' parameter 'a' expects a String value, got Undef at ...
Example 1:
{{ if (versioncmp($::puppetversion, '3') != -1) { ... }}} h3. Example 2: {{ if versioncmp($::puppetversion, '4.0.0') >= 0 { ... }
}}
Jira (PUP-5344) Could not evaluate: invalid byte sequence in US-ASCII
Title: Message Title Chris Denneen commented on PUP-5344 Re: Could not evaluate: invalid byte sequence in US-ASCII This was an issue few years back and suggested fix was to set default LANG into the puppetmaster rack instance. Now with puppetserver not sure if that's the solution anymore or why it was working with 3.8.2 and broke again with 3.8.3. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5344) Could not evaluate: invalid byte sequence in US-ASCII
Title: Message Title Chris Denneen created an issue Puppet / PUP-5344 Could not evaluate: invalid byte sequence in US-ASCII Issue Type: Bug Affects Versions: PUP 3.8.3 Assignee: Unassigned Created: 2015/10/08 7:43 AM Fix Versions: PUP 3.8.2 Labels: ubuntu puppet Priority: Normal Reporter: Chris Denneen Could not evaluate: invalid byte sequence in US-ASCII puppetserver-1.1.1 Agent: Ubuntu Trusty agent 3.8.3 has issue, downgrade to 3.8.2 and issue goes away.
Jira (HI-283) native, deep, or deeper merge not working as expected
Title: Message Title
Chris Denneen commented on HI-283
Re: native, deep, or deeper merge not working as expected
Adrien Thebo I actually just ran into this issue as well it seems with class parameters mixed with hiera:
https://github.com/vshn/puppet-gitlab/issues/28
class {'gitlab':
edition => 'ce',
external_url => 'https://git.ap.org',
gitlab_rails => {
gitlab_username_changing_enabled => false,
gitlab_default_can_create_group => 'false',
gitlab_default_projects_features_visibility_level => 'public',
},
}
and Hiera:
Jira (PUP-4425) restore deprecated "respository" parameter in metadata.json and ref
Title: Message Title Chris Denneen created an issue Puppet / PUP-4425 restore deprecated "respository" parameter in metadata.json and ref Issue Type: Improvement Assignee: Unassigned Created: 2015/04/16 9:39 AM Labels: puppet gepetto metadata deprecation dependencies Priority: Normal Reporter: Chris Denneen When creating private modules you sometimes need to create dependencies on other private modules or sometimes other modules not on the forge (github, etc). In those cases to conform to module writing standards and give the ability to use an internal forge proxy or just module list with versions showing we would need the ability to refer to a repository and possibly even a ref. Currently repository is still an option but is marked as deprecated in Gepetto UI but still would only reference master branch. Add Comment
Jira (FACT-957) module facts.d sync'd to agent not shown in facter -p output
Title: Message Title Chris Denneen created an issue Facter / FACT-957 module facts.d sync'd to agent not shown in facter -p output Issue Type: Bug Affects Versions: FACT 2.4.3 Assignee: Unassigned Components: Community Created: 2015/04/15 8:27 AM Priority: Normal Reporter: Chris Denneen modules/test/facts.d/myfact_role.txt: role=testserver This get's sync'd to /var/lib/puppet/facts.d/myfact_role.txt $role is available during puppet run but verifying role is available via facter CLI doesn't work facter -p | grep role yields no result. Add Comment
Jira (PUP-1131) Puppet raises error when trying to set owner to non-existant user
Title: Message Title
Chris Denneen commented on PUP-1131
Re: Puppet raises error when trying to set owner to non-existant user
I've manually added puppet user and group. I've manually added /etc/puppet/puppet.conf, and /var/lib/puppet/ {bucket,clientbucket,lib,log,run,ssl,state,yaml}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1131) Puppet raises error when trying to set owner to non-existant user
Title: Message Title Chris Denneen commented on PUP-1131 Re: Puppet raises error when trying to set owner to non-existant user Installed 3.7.5 on Solaris 2.6 with rubygems. Getting this via trace: bash-2.05# puppet agent -t --noop --verbose --debug --trace Debug: Failed to load library 'selinux' for feature 'selinux' Debug: Failed to load library 'shadow' for feature 'libshadow' Debug: Puppet::Type::User::ProviderPw: file pw does not exist Debug: Puppet::Type::User::ProviderLdap: true value when expecting false Debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist Debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/uuidgen does not exist Debug: Puppet::Type::User::ProviderUseradd: file chage does not exist Debug: Puppet::Type::User::ProviderPw: file pw does not exist Debug: Puppet::Type::User::ProviderLdap: true value when expecting false Debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist Debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/uuidgen does not exist Debug: Puppet::Type::User::ProviderUseradd: file chage does not exist Error: Could not create resources for managing Puppet's files and directories in sections [:main, :agent, :ssl]: undefined method `exists?' for nil:NilClass /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/type/user.rb:382:in `exists?' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings.rb:800:in `service_user_available?' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:52:in `send' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:52:in `safe_to_use_settings_value?' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:43:in `value' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:106:in `owner' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:160:in `to_resource' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings.rb:916:in `to_catalog' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings.rb:912:in `each' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings.rb:912:in `to_catalog' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings.rb:982:in `use' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/application/agent.rb:404:in `setup' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/application.rb:378:in `run' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/application.rb:507:in `plugin_hook' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/application.rb:378:in `run' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/util.rb:488:in `exit_on_fail' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/application.rb:378:in `run' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/util/command_line.rb:146:in `run' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/util/command_line.rb:92:in `execute' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/bin/puppet:8 /usr/local/bin/puppet:23:in `load' /usr/local/bin/puppet:23 Error: Could not prepare for execution: Could not create resources for managing Puppet's files and directories in sections [:main, :agent, :ssl]: undefined method `exists?' for nil:NilClass undefined method `exists?' for nil:NilClass /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/type/user.rb:382:in `exists?' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings.rb:800:in `service_user_available?' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:52:in `send' /usr/local/lib/ruby/gems/1.8/gems/puppet-3.7.5/lib/puppet/settings/file_setting.rb:52:in `safe_to_use_settings_value?' /usr/local/lib/ruby/gems/1.8/
Jira (PUP-2746) new parameter "allow_virtual"
Title: Message Title
Chris Denneen commented on an issue
Re: new parameter "allow_virtual"
Josh Cooper Appears puppetlabs-ntp 3.x (even 3.2.1) can't utilize the global allow_virtual in site.pp:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter allow_virtual on Package[ntp] at /etc/puppet/environments/production/modules/ntp/manifests/install.pp:7
I removed the global setting and will deal with the client complaining about deprecation for now. Any idea when that module will get updated? Changelog shows it's been updated for 3.6 and 4.0 compatibility but still seems to have this issue.
Thanks
Add Comment
Puppet / PUP-2746
new parameter "allow_virtual"
So, this whole "allow_virtual" new parameter has been extremely frustrating. We use puppet to manage package updates, i.e. package{'puppet': ensure=>latest} Therefore, we added Package{allow_virtual=>false} in order to remove the extraneous warning, of which because its in RED, our customers think something broke. Then, since not all of the pup...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (HI-283) native, deep, or deeper merge not working as expected
Title: Message Title
Chris Denneen commented on an issue
Re: native, deep, or deeper merge not working as expected
Thanks I guess I'm not understanding why this wouldn't work with parameterized class
so doesn't work:
class mymodule (
$template = undef,
$options= hiera_hash($options, undef),
){}
doesn't work:
class mymodule (
$template = undef,
$options= hiera_hash('mymodule::options', undef),
){}
works:
class mymodule (
$template = undef,
){
$options= hiera_hash('mymodule::options', undef)
}
Add Comment
Hiera / HI-283
native, deep, or deeper merge not working as expected
I have uploaded a complete test using vagrant for someone to test. https://github.com/cdenneen/hiera_test Currently hiera output regardless of merge_behavior is showing as "deep" Currently puppet erb with hiera is showing as "native" regardless of merge_behavior setting
Jira (HI-283) native, deep, or deeper merge not working as expected
Title: Message Title
Chris Denneen commented on an issue
Re: native, deep, or deeper merge not working as expected
Oddly you can use parameterized class hiera_hash just as long as you reset it in the body (so strange):
# = Class: mymodule
class mymodule (
$template = undef,
$my_options = hiera_hash('mymodule::options', undef)
){
$options = $my_options
file { "mymodule_config":
path=> '/tmp/mymodule.conf',
content => template($template),
}
}
Add Comment
Hiera / HI-283
native, deep, or deeper merge not working as expected
I have uploaded a complete test using vagrant for someone to test. https://github.com/cdenneen/hiera_test Currently hiera output regardless of merge_behavior is showing as "deep" Currently puppet erb with hiera is showing as "native" regardless of merge_behavior setting
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are
Jira (HI-283) native, deep, or deeper merge not working as expected
Title: Message Title Chris Denneen commented on an issue Re: native, deep, or deeper merge not working as expected Nevermind... found it: https://docs.puppetlabs.com/hiera/1/puppet.html#limitations If you need to merge arrays or merge hashes from multiple hierarchy levels, you will have to use the hiera_array or hiera_hash functions in the body of your classes. Thanks for the help explaining this... documentation is great but sometimes very hard to find exactly what you are looking for like this. Add Comment Hiera / HI-283 native, deep, or deeper merge not working as expected I have uploaded a complete test using vagrant for someone to test. https://github.com/cdenneen/hiera_test Currently hiera output regardless of merge_behavior is showing as "deep" Currently puppet erb with hiera is showing as "native" regardless of merge_behavior setting This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message
Jira (HI-283) native, deep, or deeper merge not working as expected
Title: Message Title
Chris Denneen commented on an issue
Re: native, deep, or deeper merge not working as expected
Ok yeah I forgot to put the ::fqdn=centos65.vm.local on the command which now works:
hiera --hash -c /vagrant/puppet/hiera.yaml mymodule::options ::fqdn=centos65.vm.local {"nested"=> {"param1"=>"nested_param1", "param2"=>"nested_param2", "param3"=>"nested_param3", "param4"=>"new_nested_param4"}
, "param1"=>"param1", "param2"=>"param2", "param3"=>"param3", "param4"=>"param4"}
So the issue isn't with hiera it is with Puppet.
Based on this info (and leaving ::fqdn in hiera.yaml) my /tmp/mymodule.conf should have the values shown here above populated but only populates the nested:param4 from the node yaml.
Am I doing something wrong to get this to work with Puppet?
Add Comment
Hiera / HI-283
native, deep, or deeper merge not working as expected
I have uploaded a complete test using vagrant for someone to test. https://github.com/cdenneen/hiera_test Currently hiera output regardless of merge_behavior is showing as "deep" Currently puppet erb with hiera is showing as "native" regardless of merge_behavior setting
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (HI-283) native, deep, or deeper merge not working as expected
Title: Message Title Chris Denneen created an issue Hiera / HI-283 native, deep, or deeper merge not working as expected Issue Type: Bug Affects Versions: 1.3.4 Assignee: Adrien Thebo Components: Community Created: 08/Aug/14 9:15 AM Priority: Normal Reporter: Chris Denneen I have uploaded a complete test using vagrant for someone to test. https://github.com/cdenneen/hiera_test Currently hiera output regardless of merge_behavior is showing as "deep" Currently puppet erb with hiera is showing as "native" regardless of merge_behavior setting Add Comment
