Jira (PUP-1113) Ability to display messages during agent run without creating resource changes
Title: Message Title Amir Barkal commented on PUP-1113 Re: Ability to display messages during agent run without creating resource changes I'd like to join Rodney and say that this issue is making deployment of puppet extremely difficult in situations where you want Puppet to do some monitoring, more specifically when applying compliance audits. Are there any work-arounds present? (We use Puppet 3.8) 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-484) Implement convert_to/value_from function
Title: Message Title
Henrik Lindberg assigned an issue to Henrik Lindberg
I have been working on a weekend spike of this. It is problematic to do certain things without being able to convert values. The one most commonly bumped into by users is the String => Integer conversion where they have to use something like (($val + 0}} which users find quite magic. The other alternative is to pick one of the many functions on the format "to_xxx" in standard lib, but there seems to always be exactly the one you need missing (or it does something odd).
In the spike, I have written a convert_to function that takes a value and a Type. The task of turning a String into an Integer (or any Numeric) would be:
$val.convert_to(Integer)
$val.convert_to(Numeric)
The function can work in two modes 'strict' (the default) which uses the same rules as in the puppt language regarding what is "truthy", and the formats of numbers in string form, and the mode 'extended' which is much more flexible conversion that for Boolean values accept things like 'yes', 'no', 'TRUE', etc. And numbers can be converted in octal without leading 0, hex without leading 0x, and string content may have trailing text e.g. {code:puppet] "99 bottles hanging on the wall".convert_to(Integer, extended)
would return the Integer 99.
Regarding naming, I considered the shorter 'to', or 'as', but decided that 'to' seemed more useful in some future fature for describing a range e.g. 3.to(11). And 'as' is more useful for naming alias and being a potential keyword. I also felt the users would like "value.convert_to(a_type)", rather than the reverse "a_type.value_from(value)" (they would do exactly the same thing).
I also concluded that a conversion is not the same thing as an instantiation (i.e. a new operator), even if the result is the same in simple cases like the basic data types which really just have a value (a single attribute), but for more complex data types there is a difference.
Will throw up a branch soon for early feedback.
Jira (PUP-5728) Change default parsing of manifest files to UTF-8
Title: Message Title Ethan Brown commented on PUP-5728 Re: Change default parsing of manifest files to UTF-8 Ryan Gard - I somehow missed earlier that you had changed the codepage to 65001 during FR. Per the original ticket description, these behavioral changes should exist even without the code page being set like that. In other words, even with a codepage of 437 or 1252 set, manifests should always be interpreted as UTF-8 without any additional / out of the ordinary config changes by an end user, like forcefully setting chcp 65001. In fact, Puppet previously behaved properly parsing / applying manifests when that codepage was set. Sorry I missed this earlier, but we should probably double check this with 437 just to be on the safe side. The unit tests already ensure that 65001 isn't set (so that we don't get false positive test passes) - https://github.com/puppetlabs/puppet/blob/c384ddacdc24167f6395cc4c29e1dd28a7ab4018/spec/unit/pops/parser/lexer2_spec.rb#L755-L757 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-5899) Empty hiera data in modules causes whole lookup to fail
Title: Message Title
Andrey Galkin updated an issue
Puppet / PUP-5899
Empty hiera data in modules causes whole lookup to fail
Change By:
Andrey Galkin
Situation:1. Module has "data_provider: 'hiera'" in metadata.json2. Module has simple hiera.yaml version 4 pointing to 'data/common.yaml'2. Module's data/common.yaml is empty with only three dashes:{code:yaml}---{code}4. "puppet lookup" or "puppet agent -t" leads to error below.5. The error is easily fixed by changing common.yaml content to:{code:yaml}---{}{code}{code}rror: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Function Call, undefined method `[]' for nil:NilClass at /etc/puppetlabs/code/environments/production/modules/cffirehol/manifests/init.pp:12:5 on node cfpuppet . codingfuture . net . /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:207:in `is_http_200?'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/rest.rb:105:in `find'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:194:in `find'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:299:in `block in retrieve_new_catalog'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:292:in `block in thinmark'/opt/puppetlabs/puppet/lib/ruby/2.1.0/benchmark.rb:294:in `realtime'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:291:in `thinmark'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:298:in `retrieve_new_catalog'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:59:in `retrieve_catalog'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:104:in `prepare_and_retrieve_catalog'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:206:in `run_internal'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:134:in `block in run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in `override'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:240:in `override'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:133:in `run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/agent.rb:45:in `block (4 levels) in run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/agent/locker.rb:21:in `lock'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/agent.rb:45:in `block (3 levels) in run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/agent.rb:98:in `with_client'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/agent.rb:42:in `block (2 levels) in run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/agent.rb:65:in `run_in_fork'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/agent.rb:41:in `block in run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:179:in `call'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:179:in `controlled_run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/agent.rb:39:in `run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/agent.rb:353:in `onetime'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/agent.rb:331:in `run_command'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:344:in `block in run'/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:446:in
Jira (PUP-5899) Empty hiera data in modules causes whole lookup to fail
Title: Message Title Andrey Galkin created an issue Puppet / PUP-5899 Empty hiera data in modules causes whole lookup to fail Issue Type: Bug Affects Versions: PUP 4.3.2 Assignee: Unassigned Components: Modules, Puppet Server Created: 2016/02/14 4:04 PM Priority: Normal Reporter: Andrey Galkin Situation: 1. Module has "data_provider: 'hiera'" in metadata.json 2. Module has simple hiera.yaml version 4 pointing to 'data/common.yaml' 2. Module's data/common.yaml is empty with only three dashes: ---
Jira (PUP-4911) Parameters on exported resources consiting of an array with a single element are "de-arrayified"
Title: Message Title Henrik Lindberg commented on PUP-4911 Re: Parameters on exported resources consiting of an array with a single element are "de-arrayified" Does that mean we can close this as it is supposedly fixed in 4.x ? 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-5645) Can't install gems on Arch Linux
Title: Message Title
Victor Engmark updated an issue
Puppet / PUP-5645
Can't install gems on Arch Linux
Change By:
Victor Engmark
Update: This might be a [gem issue|https://bugs.ruby-lang.org/issues/12070] rather than a Puppet issue. Keeping this open since it's not clear yet what the issue is, and since I can only reproduce when the gem command is run with Puppet. From [unix.stackexchange.com post|https://unix.stackexchange.com/q/252937/3645]:I've got [the following|https://github.com/l0b0/root/blob/cf94a48397bb2323bbecfd657b43d6fd748818c8/modules/travis_linter/manifests/init.pp]:{code:puppet}class travis_linter { include shell package { 'travis-lint':ensure => latest,provider => gem, }}{code}When I try to [test it|https://github.com/l0b0/root/tree/cf94a48397bb2323bbecfd657b43d6fd748818c8#test], however, I get the following Puppet output:{noformat}==> default: Debug: Executing: '/usr/bin/gem install --no-rdoc --no-ri travis-lint'==> default: Error: Could not update: Execution of '/usr/bin/gem install --no-rdoc --no-ri travis-lint' returned 1: ERROR: While executing gem ... (TypeError)==> default: wrong argument type nil (expected Regexp)==> default: Error: /Stage[main]/Travis_linter/Package[travis-lint]/ensure: change from absent to latest failed: Could not update: Execution of '/usr/bin/gem install --no-rdoc --no-ri travis-lint' returned 1: ERROR: While executing gem ... (TypeError)==> default: wrong argument type nil (expected Regexp){noformat}Other possibly relevant output from the [full log file|http://pastebin.com/GgT3Vy1E]:{noformat}Debug: Puppet::Type::Package::ProviderPuppet_gem: file /opt/puppetlabs/puppet/bin/gem does not existDebug: /Package[puppet-lint]: Provider gem does not support features virtual_packages; not managing attribute allow_virtualDebug: /Package[reek]: Provider gem does not support features virtual_packages; not managing attribute allow_virtualDebug: /Package[travis-lint]: Provider gem does not support features virtual_packages; not managing attribute allow_virtual{noformat}Setting `ensure` to `2.0.0` didn't help, so it's not related to the `latest` keyword:{noformat}Error: Could not update: Execution of '/usr/bin/gem install -v 2.0.0 --no-rdoc --no-ri travis-lint' returned 1: ERROR: While executing gem ... (TypeError)wrong argument type nil (expected Regexp){noformat}I am able to run the exact same command manually:{noformat}[vagrant@archlinux ~]$ /usr/bin/gem install --no-rdoc --no-ri travis-lintFetching: travis-lint-2.0.0.gem (100%)WARNING: You don't have /home/vagrant/.gem/ruby/2.3.0/bin in your PATH, gem executables will not run.Successfully installed travis-lint-2.0.01 gem installed{noformat}Is my Puppet manifest wrong, or is something broken about Puppet/Gem? Is it possible that `latest` is not a valid value for gems?It works fine on [Travis CI (Ubuntu 12.04)|https://travis-ci.org/l0b0/root/builds/99846406#L1153-L1156]:{noformat}Debug: Executing: '/home/travis/.rvm/rubies/ruby-2.2.3/bin/gem list --local ^travis-lint$'Debug: Executing: '/home/travis/.rvm/rubies/ruby-2.2.3/bin/gem install --no-rdoc --no-ri travis-lint'Notice: /Stage[main]/Travis_linter/Package[travis-lint]/ensure: createdDebug: /Package[travis-lint]: The container Class[Travis_linter] will propagate my refresh
Jira (PUP-5645) Can't install gems on Arch Linux
Title: Message Title Kylo Ginsberg commented on PUP-5645 Re: Can't install gems on Arch Linux It occurred to me that maybe this was an issue with ruby 2.3 (which is not widely exercised with puppet so far AFAIK), but I tried to reproduce this (on OSX) with ruby 2.3 and I couldn't reproduce it. One other idea, but I didn't have a chance to run this down, was that it might be the stderr output you're getting with gem that's tripping puppet up somehow (though I'd expect to see that elsewhere tbh). You might get more useful output if you also specified "--trace" - if so, please attach a gist with that output. And of course, if you're comfortable debugging ruby code, I'd try setting breakpoints and poking around a bit. Btw, the "possibly relevant output" you snipped is stuff I'd expect to see regardless, so probably isn't a lead. 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-5645) Can't install gems on Arch Linux
Title: Message Title Victor Engmark commented on PUP-5645 Re: Can't install gems on Arch Linux ==> default: Debug: Executing: '/usr/bin/gem install --no-rdoc --no-ri --trace travis-lint'==> default: Notice: /Stage[main]/Travis_linter/Exec[/usr/bin/gem install --no-rdoc --no-ri --trace travis-lint]/returns: ERROR: While executing gem ... (OptionParser::InvalidOption)==> default: Notice: /Stage[main]/Travis_linter/Exec[/usr/bin/gem install --no-rdoc --no-ri --trace travis-lint]/returns: invalid option: --trace==> default: Error: /usr/bin/gem install --no-rdoc --no-ri --trace travis-lint returned 1 instead of one of [0]==> default: Error: /Stage[main]/Travis_linter/Exec[/usr/bin/gem install --no-rdoc --no-ri --trace travis-lint]/returns: change from notrun to 0 failed: /usr/bin/gem install --no-rdoc --no-ri --trace travis-lint returned 1 instead of one of [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-5645) Can't install gems on Arch Linux
Title: Message Title
Victor Engmark commented on PUP-5645
Re: Can't install gems on Arch Linux
{{code}}Debug: Executing: '/usr/bin/gem install --no-rdoc --no-ri --trace travis-lint'Notice: /Stage[main]/Travis_linter/Exec[/usr/bin/gem install --no-rdoc --no-ri --trace travis-lint]/returns: ERROR: While executing gem ... (OptionParser::InvalidOption)Notice: /Stage[main]/Travis_linter/Exec[/usr/bin/gem install --no-rdoc --no-ri --trace travis-lint]/returns: invalid option: --traceError: /usr/bin/gem install --no-rdoc --no-ri --trace travis-lint returned 1 instead of one of [0]/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util/errors.rb:106:in `fail'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/type/exec.rb:160:in `sync'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction/resource_harness.rb:214:in `sync'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction/resource_harness.rb:139:in `sync_if_needed'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction/resource_harness.rb:89:in `block in perform_changes'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction/resource_harness.rb:88:in `each'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction/resource_harness.rb:88:in `perform_changes'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction/resource_harness.rb:20:in `evaluate'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction.rb:207:in `apply'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction.rb:223:in `eval_resource'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction.rb:150:in `call'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction.rb:150:in `block (2 levels) in evaluate'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util.rb:292:in `block in thinmark'/usr/lib/ruby/2.3.0/benchmark.rb:308:in `realtime'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util.rb:291:in `thinmark'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction.rb:150:in `block in evaluate'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/graph/relationship_graph.rb:118:in `traverse'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction.rb:141:in `evaluate'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/resource/catalog.rb:202:in `block in apply'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util/log.rb:153:in `with_destination'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction/report.rb:107:in `as_logging_destination'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/resource/catalog.rb:201:in `apply'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/configurer.rb:119:in `block in apply_catalog'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util.rb:129:in `block in benchmark'/usr/lib/ruby/2.3.0/benchmark.rb:308:in `realtime'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util.rb:128:in `benchmark' /usr/lib/ruby/vendor_ruby/2.3.0/puppet/configurer.rb:118:in `apply_catalog'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/configurer.rb:232:in `run_internal' /usr/lib/ruby/vendor_ruby/2.3.0/puppet/configurer.rb:134:in `block in run'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/context.rb:65:in `override'/usr/lib/ruby/vendor_ruby/2.3.0/puppet.rb:240:in `override'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/configurer.rb:133:in `run'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/application/apply.rb:347:in `apply_catalog'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/application/apply.rb:274:in `block in main'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/context.rb:65:in `override'/usr/lib/ruby/vendor_ruby/2.3.0/puppet.rb:240:in `override'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/application/apply.rb:225:in `main'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/application/apply.rb:170:in `run_command'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/application.rb:344:in `block in run'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util.rb:446:in `exit_on_fail'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/application.rb:344:in `run'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util/command_line.rb:128:in `run'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util/command_line.rb:72:in `execute'/usr/bin/puppet:5:in `'Error: /Stage[main]/Travis_linter/Exec[/usr/bin/gem install --no-rdoc
Jira (PUP-5645) Can't install gems on Arch Linux
Title: Message Title
Victor Engmark updated an issue
Puppet / PUP-5645
Can't install gems on Arch Linux
Change By:
Victor Engmark
Comment:
{{code}}Debug: Executing: '/usr/bin/gem install --no-rdoc --no-ri --trace travis-lint'Notice: /Stage[main]/Travis_linter/Exec[/usr/bin/gem install --no-rdoc --no-ri --trace travis-lint]/returns: ERROR: While executing gem ... (OptionParser::InvalidOption)Notice: /Stage[main]/Travis_linter/Exec[/usr/bin/gem install --no-rdoc --no-ri --trace travis-lint]/returns: invalid option: --traceError: /usr/bin/gem install --no-rdoc --no-ri --trace travis-lint returned 1 instead of one of [0]/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util/errors.rb:106:in `fail'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/type/exec.rb:160:in `sync'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction/resource_harness.rb:214:in `sync'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction/resource_harness.rb:139:in `sync_if_needed'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction/resource_harness.rb:89:in `block in perform_changes'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction/resource_harness.rb:88:in `each'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction/resource_harness.rb:88:in `perform_changes'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction/resource_harness.rb:20:in `evaluate'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction.rb:207:in `apply'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction.rb:223:in `eval_resource'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction.rb:150:in `call'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction.rb:150:in `block (2 levels) in evaluate'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util.rb:292:in `block in thinmark'/usr/lib/ruby/2.3.0/benchmark.rb:308:in `realtime'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util.rb:291:in `thinmark'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction.rb:150:in `block in evaluate'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/graph/relationship_graph.rb:118:in `traverse'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction.rb:141:in `evaluate'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/resource/catalog.rb:202:in `block in apply'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util/log.rb:153:in `with_destination'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction/report.rb:107:in `as_logging_destination'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/resource/catalog.rb:201:in `apply'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/configurer.rb:119:in `block in apply_catalog'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util.rb:129:in `block in benchmark'/usr/lib/ruby/2.3.0/benchmark.rb:308:in `realtime'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util.rb:128:in `benchmark' /usr/lib/ruby/vendor_ruby/2.3.0/puppet/configurer.rb:118:in `apply_catalog'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/configurer.rb:232:in `run_internal' /usr/lib/ruby/vendor_ruby/2.3.0/puppet/configurer.rb:134:in `block in run'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/context.rb:65:in `override'/usr/lib/ruby/vendor_ruby/2.3.0/puppet.rb:240:in `override'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/configurer.rb:133:in `run'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/application/apply.rb:347:in `apply_catalog'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/application/apply.rb:274:in `block in main'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/context.rb:65:in `override'/usr/lib/ruby/vendor_ruby/2.3.0/puppet.rb:240:in
Jira (PUP-5645) Can't install gems on Arch Linux
Title: Message Title Victor Engmark commented on PUP-5645 Re: Can't install gems on Arch Linux code}}Error: Could not update: Execution of '/usr/bin/gem install --no-rdoc --no-ri travis-lint' returned 1: ERROR: While executing gem ... (TypeError) wrong argument type nil (expected Regexp)/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util/execution.rb:232:in `execute'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/provider.rb:102:in `execute'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/provider/package/gem.rb:128:in `install'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/provider/package/gem.rb:159:in `update'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/type/package.rb:106:in `block (3 levels) in '/usr/lib/ruby/vendor_ruby/2.3.0/puppet/property.rb:427:in `set'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/property.rb:501:in `sync'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction/resource_harness.rb:214:in `sync'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction/resource_harness.rb:139:in `sync_if_needed'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction/resource_harness.rb:81:in `perform_changes'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction/resource_harness.rb:20:in `evaluate'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction.rb:207:in `apply'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction.rb:223:in `eval_resource'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction.rb:150:in `call'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction.rb:150:in `block (2 levels) in evaluate'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util.rb:292:in `block in thinmark'/usr/lib/ruby/2.3.0/benchmark.rb:308:in `realtime'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util.rb:291:in `thinmark'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction.rb:150:in `block in evaluate'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/graph/relationship_graph.rb:118:in `traverse'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction.rb:141:in `evaluate'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/resource/catalog.rb:202:in `block in apply'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util/log.rb:153:in `with_destination'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/transaction/report.rb:107:in `as_logging_destination'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/resource/catalog.rb:201:in `apply'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/configurer.rb:119:in `block in apply_catalog'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util.rb:129:in `block in benchmark'/usr/lib/ruby/2.3.0/benchmark.rb:308:in `realtime'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util.rb:128:in `benchmark' /usr/lib/ruby/vendor_ruby/2.3.0/puppet/configurer.rb:118:in `apply_catalog'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/configurer.rb:232:in `run_internal' /usr/lib/ruby/vendor_ruby/2.3.0/puppet/configurer.rb:134:in `block in run'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/context.rb:65:in `override'/usr/lib/ruby/vendor_ruby/2.3.0/puppet.rb:240:in `override'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/configurer.rb:133:in `run'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/application/apply.rb:347:in `apply_catalog'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/application/apply.rb:274:in `block in main'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/context.rb:65:in `override'/usr/lib/ruby/vendor_ruby/2.3.0/puppet.rb:240:in `override'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/application/apply.rb:225:in `main'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/application/apply.rb:170:in `run_command'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/application.rb:344:in `block in run'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util.rb:446:in `exit_on_fail'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/application.rb:344:in `run'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util/command_line.rb:128:in `run'/usr/lib/ruby/vendor_ruby/2.3.0/puppet/util/command_line.rb:72:in `execute'/usr/bin/puppet:5:in `'Error: /Stage[main]/Travis_linter/Package[travis-lint]/ensure: change from absent to latest failed: Could not update: Execution of '/usr/bin/gem install --no-rdoc --no-ri
Jira (PUP-5645) Can't install gems on Arch Linux
Title: Message Title Victor Engmark commented on PUP-5645 Re: Can't install gems on Arch Linux Still all good: [vagrant@archlinux ~]$ LANG=C LC_ALL=C /usr/bin/gem install -v 2.0.0 --no-rdoc --no-ri travis-lintFetching: travis-lint-2.0.0.gem (100%)WARNING: You don't have /home/vagrant/.gem/ruby/2.3.0/bin in your PATH, gem executables will not run.Successfully installed travis-lint-2.0.01 gem installed 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-4911) Parameters on exported resources consiting of an array with a single element are "de-arrayified"
Title: Message Title Reinhard Vicinus commented on PUP-4911 Re: Parameters on exported resources consiting of an array with a single element are "de-arrayified" From my site, this can be closed. I switched to puppet 4.x and there it works. 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-5645) Can't install gems on Arch Linux
Title: Message Title Kylo Ginsberg commented on PUP-5645 Re: Can't install gems on Arch Linux Hmm, that kinda confirms it's failing where I assumed it was failing but that's mostly good from a ruling-things-out perspective. The error it's reporting is coming from gem AFAICT so maybe it's something about how puppet is setting up the execution environment when it runs the command. Another experiment: can you try LANG=C LC_ALL=C /usr/bin/gem install -v 2.0.0 --no-rdoc --no-ri travis-lint? That isn't the full list of environment setup (see https://github.com/puppetlabs/puppet/blob/4.3.2/lib/puppet/util/execution.rb#L276-L299) but it's an easy-ish thing to try 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-5645) Can't install gems on Arch Linux
Title: Message Title
Victor Engmark updated an issue
Puppet / PUP-5645
Can't install gems on Arch Linux
Change By:
Victor Engmark
Comment:
{code:java}==> default: Debug: Executing: '/usr/bin/gem install --no-rdoc --no-ri --trace travis-lint'==> default: Notice: /Stage[main]/Travis_linter/Exec[/usr/bin/gem install --no-rdoc --no-ri --trace travis-lint]/returns: ERROR: While executing gem ... (OptionParser::InvalidOption)==> default: Notice: /Stage[main]/Travis_linter/Exec[/usr/bin/gem install --no-rdoc --no-ri --trace travis-lint]/returns: invalid option: --trace==> default: Error: /usr/bin/gem install --no-rdoc --no-ri --trace travis-lint returned 1 instead of one of [0]==> default: Error: /Stage[main]/Travis_linter/Exec[/usr/bin/gem install --no-rdoc --no-ri --trace travis-lint]/returns: change from notrun to 0 failed: /usr/bin/gem install --no-rdoc --no-ri --trace travis-lint returned 1 instead of one of [0]{code}
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-4911) Parameters on exported resources consiting of an array with a single element are "de-arrayified"
Title: Message Title Reinhard Vicinus commented on PUP-4911 Re: Parameters on exported resources consiting of an array with a single element are "de-arrayified" Spontaneously I would say I run it with future parser off, because I'm pretty sure I would have mentioned if the future parser was active. But it's quite some time in the past and I don't have a puppet 3.x setup anymore for testing it. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
