Jira (PUP-8498) No title provided and "foo" is not a valid resource reference
Title: Message Title
Gavin Williams updated an issue
Puppet / PUP-8498
No title provided and "foo" is not a valid resource reference
Change By:
Gavin Williams
*Puppet Version:* 5.3.3 *Puppet Server Version:* N/AUpon creating some rspec-puppet tests for a new Puppet module, the following error was encountered:{code:java} 1) actora on centos-7-x86_64 with defaults should compile into a catalogue without dependency cyclesFailure/Error: it { should compile }error during compilation: No title provided and "actora" is not a valid resource reference on node lt0772.local{code}As there was no traceback to a specific file/line provided, this one proved challenging to track down. In the end, the following code was at fault:{code:java} ## install actora rpm (which should install nodejs and npm)package { $actora::package_name: ensure => $actora::version, notify => $actora::service_name, tag => ['actora::package']}{code}The notify here resolves to {{'actora'}}.A simple reproducer is:{code:java} $ cat foo/manifests/init.ppclass foo () { notify { 'testing':notify => xyz, }}$ puppet apply -t --exec 'include foo'Info: Loading factsError: No title provided and "xyz" is not a valid resource reference on node host.example.net{code}Thanks to [~JohnsonEarls] for the reproducer.
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8498) No title provided and "foo" is not a valid resource reference
Title: Message Title
Gavin Williams created an issue
Puppet / PUP-8498
No title provided and "foo" is not a valid resource reference
Issue Type:
Improvement
Affects Versions:
PUP 5.3.3
Assignee:
Unassigned
Components:
AIO
Created:
2018/02/28 8:43 AM
Priority:
Normal
Reporter:
Gavin Williams
Puppet Version: 5.3.3 Puppet Server Version: N/A Upon creating some rspec-puppet tests for a new Puppet module, the following error was encountered:
1) actora on centos-7-x86_64 with defaults should compile into a catalogue without dependency cycles
Failure/Error: it { should compile }
error during compilation: No title provided and "actora" is not a valid resource reference on node lt0772.local
As there was no traceback to a specific file/line provided, this one proved
Jira (PUP-8419) Puppet-Run WARNING after upgrading to 5.3.4
Title: Message Title Gavin Williams commented on PUP-8419 Re: Puppet-Run WARNING after upgrading to 5.3.4 PUP-8418 is probably related... 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-8418) TypeError no implicit conversion of nil into String in puppet 5.3.4
Title: Message Title Gavin Williams updated an issue Puppet / PUP-8418 TypeError no implicit conversion of nil into String in puppet 5.3.4 Change By: Gavin Williams Priority: Normal Blocker 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-8418) TypeError no implicit conversion of nil into String in puppet 5.3.4
Title: Message Title Gavin Williams commented on PUP-8418 Re: TypeError no implicit conversion of nil into String in puppet 5.3.4 For completeness, I've just raised an issue against rspec-puppet - https://github.com/rodjek/rspec-puppet/issues/647 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 (PDB-3509) PuppetDB facts insert fails due to PostgreSQL 'invalid byte sequence'
Title: Message Title Gavin Williams created an issue PuppetDB / PDB-3509 PuppetDB facts insert fails due to PostgreSQL 'invalid byte sequence' Issue Type: Bug Affects Versions: PDB 4.4.0 Assignee: Unassigned Components: PuppetDB Created: 2017/05/10 7:30 AM Priority: Major Reporter: Gavin Williams I'm getting repeated errors in our PuppetDB server log with the following exception: 2017-05-10 15:23:17,979 ERROR [p.p.command] [54] [replace facts] Retrying after attempt 0 for sdi01.cre.uk1a.weareact.net, due to: java.sql.BatchUpdateException: Batch entry 175 INSERT INTO facts ( factset_id, fact_path_id, value_type_id, large_value_hash, value, value_string, value_integer, value_float, value_boolean ) VALUES [snipped] as aborted. Call getNextException to see the cause.
Jira (PUP-3656) Prefetch eats all exceptions, there is no way to fail out.
Title: Message Title Gavin Williams commented on PUP-3656 Re: Prefetch eats all exceptions, there is no way to fail out. +1 from me. I've been hit by this with my NetApp types/providers before, but never tracked the issue down... So thank's for that Tomas Doran. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3336) Puppet defaults.rb doesn't split :libdir if multiple paths provided
Title: Message Title Gavin Williams created an issue Puppet / PUP-3336 Puppet defaults.rb doesn't split :libdir if multiple paths provided Issue Type: Bug Affects Versions: 3.7.1, 3.6.2, 3.3.3 Assignee: Andy Parker Components: Server Created: 24/Sep/14 8:17 AM Environment: Puppet gem Rspec-puppet Priority: Normal Reporter: Gavin Williams When attempting to rspec-puppet test one of my profiles modules, that has multiple module dependencies, an issue was identified whereby it wasn't auto-loading module fixture lib dirs. Example error that was seeing was: Error: Could not autoload puppet/provider/domain/asadmin: cannot load such file -- puppet/provider/asadmin Error: Could not autoload puppet/type/domain: Could not autoload puppet/provider/domain/asadmin: cannot load such file -- puppet/provider/asadmin Error: Could not autoload puppet/type/domain: Could not autoload puppet/provider/domain/asadmin: cannot load such file -- puppet/provider/asadmin on node
Jira (PUP-3336) Puppet defaults.rb doesn't split :libdir if multiple paths provided
Title: Message Title
Gavin Williams commented on an issue
Re: Puppet defaults.rb doesn't split :libdir if multiple paths provided
A simple module that illustrates this behaviour is: https://github.com/fatmcgav/rspec-deptest
Add Comment
Puppet / PUP-3336
Puppet defaults.rb doesn't split :libdir if multiple paths provided
When attempting to rspec-puppet test one of my profiles modules, that has multiple module dependencies, an issue was identified whereby it wasn't auto-loading module fixture lib dirs. Example error that was seeing was: {code} Error: Could not autoload puppet/provider/domain/asadmin: cannot load such file -- puppet/provider/asadmin Error: Could not...
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-3336) Puppet defaults.rb doesn't split :libdir if multiple paths provided
Title: Message Title
Gavin Williams commented on an issue
Re: Puppet defaults.rb doesn't split :libdir if multiple paths provided
Work-around for this can be added to spec_helper.rb:
# Add fixture lib dirs to LOAD_PATH. Work-around for PUP-3336
#
if Puppet.version 4.0.0
Dir[#{fixture_path}/modules/*/lib].entries.each do |lib_dir|
$LOAD_PATH lib_dir
end
end
Is there appetite to add this work-around to puppetlabs_spec_helper to make ppl's lives easier?
Add Comment
Jira (PUP-2717) Unable to confine NetworkDevice using facter values
Title: Message Title Gavin Williams created an issue Puppet / PUP-2717 Unable to confine NetworkDevice using facter values Issue Type: Bug Affects Versions: 3.5.1 Assignee: Andy Parker Components: Server Created: 03/Jun/14 1:24 AM Priority: Major Reporter: Gavin Williams Currently, it appears that it is impossible to use confine with facter values when running against a NetworkDevice, as discussed here[1]. [1] https://groups.google.com/forum/#!topic/puppet-dev/_DXOY8UrDXs Add Comment
Jira (PUP-1544) Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError)
Title: Message Title
Gavin Williams commented on an issue
Re: Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError)
Andy Parker I didn't ever get it working tbh.
The patches attached were from my hacking around trying to get things working, and quickly got out of my depth... Adrien Thebo did give me some assistance at various points, so might remember the issues...
Add Comment
Puppet / PUP-1544
Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError)
When trying to test some tweaks to support PUP-958, an issue has been encountered whereby Puppet is throwing the following error: {noformat} sudo bundle exec puppet resource package bash ensure=held /home/vagrant/puppet/lib/puppet/util/logging.rb:34:in `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError) f...
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
Jira (PUP-1072) support HTTP(S) URL as the file 'source'
Title: Message Title
Gavin Williams commented on an issue
Re: support HTTP(S) URL as the file 'source'
+1 from me... Would make working with Windows clients much easier, as there's no command line wget to use
Add Comment
Puppet / PUP-1072
support HTTP(S) URL as the file 'source'
Lots and lots of folks want to be able to do this: file { /tmp/example.txt: source = 'http://example.com/example.txt#39; } This would be good to support; obviously the metadata for the HTTP URI is much less available than via puppet file serving, but this would make a lot of people very, very happy.
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.
Jira (PUP-1542) Puppet::Util::Log requires a message
Title: Message Title
Gavin Williams updated an issue
Puppet / PUP-1542
Puppet::Util::Log requires a message
Change By:
Gavin Williams
WhentryingtoaddholdablesupporttotheyumpackageproviderunderPUP-958,thefollowingerrorisbeingthrownwhenattemptingtocatchanexceptioninvoking'provider.hold'.{noformat}$sudobundleexecpuppetresourcepackagebashensure=held--traceError:/Package[bash]:Couldnotevaluate:Puppet::Util::Logrequiresamessage/mnt/data/Puppet/lib/puppet/util/log.rb:298:in`message='/mnt/data/Puppet/lib/puppet/util/log.rb:247:in`initialize'/mnt/data/Puppet/lib/puppet/util/log.rb:84:in`new'/mnt/data/Puppet/lib/puppet/util/log.rb:84:in`create'/mnt/data/Puppet/lib/puppet/util/logging.rb:8:in`send_log'/mnt/data/Puppet/lib/puppet/transaction/event.rb:78:in`send_log'/mnt/data/Puppet/lib/puppet/transaction/resource_harness.rb:154:in`ensureinsync_if_needed'/mnt/data/Puppet/lib/puppet/transaction/resource_harness.rb:155:in`sync_if_needed'/mnt/data/Puppet/lib/puppet/transaction/resource_harness.rb:107:in`manage_via_ensure_if_possible'/mnt/data/Puppet/lib/puppet/transaction/resource_harness.rb:77:in`perform_changes'/mnt/data/Puppet/lib/puppet/transaction/resource_harness.rb:18:in`evaluate'/mnt/data/Puppet/lib/puppet/transaction.rb:174:in`apply'/mnt/data/Puppet/lib/puppet/transaction.rb:187:in`eval_resource'/mnt/data/Puppet/lib/puppet/transaction.rb:117:in`call'/mnt/data/Puppet/lib/puppet/transaction.rb:117:in`block(2levels)inevaluate'/mnt/data/Puppet/lib/puppet/util.rb:327:in`blockinthinmark'/usr/share/ruby/benchmark.rb:296:in`realtime'/mnt/data/Puppet/lib/puppet/util.rb:326:in`thinmark'/mnt/data/Puppet/lib/puppet/transaction.rb:117:in`blockinevaluate'/mnt/data/Puppet/lib/puppet/graph/relationship_graph.rb:118:in`traverse'/mnt/data/Puppet/lib/puppet/transaction.rb:108:in`evaluate'/mnt/data/Puppet/lib/puppet/resource/catalog.rb:164:in`blockinapply'/mnt/data/Puppet/lib/puppet/util/log.rb:153:in`with_destination'/mnt/data/Puppet/lib/puppet/transaction/report.rb:107:in`as_logging_destination'/mnt/data/Puppet/lib/puppet/resource/catalog.rb:163:in`apply'/mnt/data/Puppet/lib/puppet/indirector/resource/ral.rb:41:in`save'/mnt/data/Puppet/lib/puppet/indirector/indirection.rb:283:in`save'/mnt/data/Puppet/lib/puppet/application/resource.rb:219:in`find_or_save_resources'/mnt/data/Puppet/lib/puppet/application/resource.rb:143:in`main'/mnt/data/Puppet/lib/puppet/application.rb:376:in`run_command'/mnt/data/Puppet/lib/puppet/application.rb:367:in`block(3levels)inrun'/mnt/data/Puppet/lib/puppet/application.rb:474:in`plugin_hook'/mnt/data/Puppet/lib/puppet/application.rb:367:in`block(2levels)inrun'/mnt/data/Puppet/lib/puppet/util.rb:479:in`exit_on_fail'/mnt/data/Puppet/lib/puppet/application.rb:367:in`blockinrun'/mnt/data/Puppet/lib/puppet/context.rb:51:in`override'/mnt/data/Puppet/lib/puppet.rb:224:in`override'/mnt/data/Puppet/lib/puppet/application.rb:357:in`run'/mnt/data/Puppet/lib/puppet/util/command_line.rb:137:in`run'/mnt/data/Puppet/lib/puppet/util/command_line.rb:91:in`execute'/mnt/data/Puppet/bin/puppet:4:in`top(required)'/usr/local/share/gems/bin/puppet:23:in`load'/usr/local/share/gems/bin/puppet:23:in`main'package{'bash':ensure='4.2.45-1.fc19',}{noformat}Thisiswiththefollowingpatchapplied:{code: diff none
Jira (PUP-1542) Puppet::Util::Log requires a message
Title: Message Title
Gavin Williams updated an issue
Puppet / PUP-1542
Puppet::Util::Log requires a message
Change By:
Gavin Williams
WhentryingtoaddholdablesupporttotheyumpackageproviderunderPUP-958,thefollowingerrorisbeingthrownwhenattemptingtocatchanexceptioninvoking'provider.hold'.{noformat}$sudobundleexecpuppetresourcepackagebashensure=held--traceError:/Package[bash]:Couldnotevaluate:Puppet::Util::Logrequiresamessage/mnt/data/Puppet/lib/puppet/util/log.rb:298:in`message='/mnt/data/Puppet/lib/puppet/util/log.rb:247:in`initialize'/mnt/data/Puppet/lib/puppet/util/log.rb:84:in`new'/mnt/data/Puppet/lib/puppet/util/log.rb:84:in`create'/mnt/data/Puppet/lib/puppet/util/logging.rb:8:in`send_log'/mnt/data/Puppet/lib/puppet/transaction/event.rb:78:in`send_log'/mnt/data/Puppet/lib/puppet/transaction/resource_harness.rb:154:in`ensureinsync_if_needed'/mnt/data/Puppet/lib/puppet/transaction/resource_harness.rb:155:in`sync_if_needed'/mnt/data/Puppet/lib/puppet/transaction/resource_harness.rb:107:in`manage_via_ensure_if_possible'/mnt/data/Puppet/lib/puppet/transaction/resource_harness.rb:77:in`perform_changes'/mnt/data/Puppet/lib/puppet/transaction/resource_harness.rb:18:in`evaluate'/mnt/data/Puppet/lib/puppet/transaction.rb:174:in`apply'/mnt/data/Puppet/lib/puppet/transaction.rb:187:in`eval_resource'/mnt/data/Puppet/lib/puppet/transaction.rb:117:in`call'/mnt/data/Puppet/lib/puppet/transaction.rb:117:in`block(2levels)inevaluate'/mnt/data/Puppet/lib/puppet/util.rb:327:in`blockinthinmark'/usr/share/ruby/benchmark.rb:296:in`realtime'/mnt/data/Puppet/lib/puppet/util.rb:326:in`thinmark'/mnt/data/Puppet/lib/puppet/transaction.rb:117:in`blockinevaluate'/mnt/data/Puppet/lib/puppet/graph/relationship_graph.rb:118:in`traverse'/mnt/data/Puppet/lib/puppet/transaction.rb:108:in`evaluate'/mnt/data/Puppet/lib/puppet/resource/catalog.rb:164:in`blockinapply'/mnt/data/Puppet/lib/puppet/util/log.rb:153:in`with_destination'/mnt/data/Puppet/lib/puppet/transaction/report.rb:107:in`as_logging_destination'/mnt/data/Puppet/lib/puppet/resource/catalog.rb:163:in`apply'/mnt/data/Puppet/lib/puppet/indirector/resource/ral.rb:41:in`save'/mnt/data/Puppet/lib/puppet/indirector/indirection.rb:283:in`save'/mnt/data/Puppet/lib/puppet/application/resource.rb:219:in`find_or_save_resources'/mnt/data/Puppet/lib/puppet/application/resource.rb:143:in`main'/mnt/data/Puppet/lib/puppet/application.rb:376:in`run_command'/mnt/data/Puppet/lib/puppet/application.rb:367:in`block(3levels)inrun'/mnt/data/Puppet/lib/puppet/application.rb:474:in`plugin_hook'/mnt/data/Puppet/lib/puppet/application.rb:367:in`block(2levels)inrun'/mnt/data/Puppet/lib/puppet/util.rb:479:in`exit_on_fail'/mnt/data/Puppet/lib/puppet/application.rb:367:in`blockinrun'/mnt/data/Puppet/lib/puppet/context.rb:51:in`override'/mnt/data/Puppet/lib/puppet.rb:224:in`override'/mnt/data/Puppet/lib/puppet/application.rb:357:in`run'/mnt/data/Puppet/lib/puppet/util/command_line.rb:137:in`run'/mnt/data/Puppet/lib/puppet/util/command_line.rb:91:in`execute'/mnt/data/Puppet/bin/puppet:4:in`top(required)'/usr/local/share/gems/bin/puppet:23:in`load'/usr/local/share/gems/bin/puppet:23:in`main'package{'bash':ensure='4.2.45-1.fc19',}{noformat}Thisiswiththefollowingpatchapplied:{code :diff
Jira (PUP-1542) Puppet::Util::Log requires a message
Title: Message Title Gavin Williams updated an issue Puppet / PUP-1542 Puppet::Util::Log requires a message Patch file for package type to add catch block around provider.hold. Change By: Gavin Williams Attachment: lib_puppet_type_package_rb.diff Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1542) Puppet::Util::Log requires a message
Title: Message Title
Gavin Williams updated an issue
Puppet / PUP-1542
Puppet::Util::Log requires a message
Change By:
Gavin Williams
WhentryingtoaddholdablesupporttotheyumpackageproviderunderPUP-958,thefollowingerrorisbeingthrownwhenattemptingtocatchanexceptioninvoking'provider.hold'.{noformat}$sudobundleexecpuppetresourcepackagebashensure=held--traceError:/Package[bash]:Couldnotevaluate:Puppet::Util::Logrequiresamessage/mnt/data/Puppet/lib/puppet/util/log.rb:298:in`message='/mnt/data/Puppet/lib/puppet/util/log.rb:247:in`initialize'/mnt/data/Puppet/lib/puppet/util/log.rb:84:in`new'/mnt/data/Puppet/lib/puppet/util/log.rb:84:in`create'/mnt/data/Puppet/lib/puppet/util/logging.rb:8:in`send_log'/mnt/data/Puppet/lib/puppet/transaction/event.rb:78:in`send_log'/mnt/data/Puppet/lib/puppet/transaction/resource_harness.rb:154:in`ensureinsync_if_needed'/mnt/data/Puppet/lib/puppet/transaction/resource_harness.rb:155:in`sync_if_needed'/mnt/data/Puppet/lib/puppet/transaction/resource_harness.rb:107:in`manage_via_ensure_if_possible'/mnt/data/Puppet/lib/puppet/transaction/resource_harness.rb:77:in`perform_changes'/mnt/data/Puppet/lib/puppet/transaction/resource_harness.rb:18:in`evaluate'/mnt/data/Puppet/lib/puppet/transaction.rb:174:in`apply'/mnt/data/Puppet/lib/puppet/transaction.rb:187:in`eval_resource'/mnt/data/Puppet/lib/puppet/transaction.rb:117:in`call'/mnt/data/Puppet/lib/puppet/transaction.rb:117:in`block(2levels)inevaluate'/mnt/data/Puppet/lib/puppet/util.rb:327:in`blockinthinmark'/usr/share/ruby/benchmark.rb:296:in`realtime'/mnt/data/Puppet/lib/puppet/util.rb:326:in`thinmark'/mnt/data/Puppet/lib/puppet/transaction.rb:117:in`blockinevaluate'/mnt/data/Puppet/lib/puppet/graph/relationship_graph.rb:118:in`traverse'/mnt/data/Puppet/lib/puppet/transaction.rb:108:in`evaluate'/mnt/data/Puppet/lib/puppet/resource/catalog.rb:164:in`blockinapply'/mnt/data/Puppet/lib/puppet/util/log.rb:153:in`with_destination'/mnt/data/Puppet/lib/puppet/transaction/report.rb:107:in`as_logging_destination'/mnt/data/Puppet/lib/puppet/resource/catalog.rb:163:in`apply'/mnt/data/Puppet/lib/puppet/indirector/resource/ral.rb:41:in`save'/mnt/data/Puppet/lib/puppet/indirector/indirection.rb:283:in`save'/mnt/data/Puppet/lib/puppet/application/resource.rb:219:in`find_or_save_resources'/mnt/data/Puppet/lib/puppet/application/resource.rb:143:in`main'/mnt/data/Puppet/lib/puppet/application.rb:376:in`run_command'/mnt/data/Puppet/lib/puppet/application.rb:367:in`block(3levels)inrun'/mnt/data/Puppet/lib/puppet/application.rb:474:in`plugin_hook'/mnt/data/Puppet/lib/puppet/application.rb:367:in`block(2levels)inrun'/mnt/data/Puppet/lib/puppet/util.rb:479:in`exit_on_fail'/mnt/data/Puppet/lib/puppet/application.rb:367:in`blockinrun'/mnt/data/Puppet/lib/puppet/context.rb:51:in`override'/mnt/data/Puppet/lib/puppet.rb:224:in`override'/mnt/data/Puppet/lib/puppet/application.rb:357:in`run'/mnt/data/Puppet/lib/puppet/util/command_line.rb:137:in`run'/mnt/data/Puppet/lib/puppet/util/command_line.rb:91:in`execute'/mnt/data/Puppet/bin/puppet:4:in`top(required)'/usr/local/share/gems/bin/puppet:23:in`load'/usr/local/share/gems/bin/puppet:23:in`main'package{'bash':ensure='4.2.45-1.fc19',}{noformat}Thisiswiththefollowingpatchapplied: {code Edit : none}diff--gita/lib/puppet/type/package Addedpatchasattachmentasformattingwasbreakingit .
Jira (PUP-1544) Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError)
Title: Message Title Gavin Williams updated an issue Puppet / PUP-1544 Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError) Relevant patch files. Change By: Gavin Williams Attachment: lib_puppet_util_rb.diff Attachment: lib_puppet_type_package_rb.diff Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1544) Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError)
Title: Message Title
Gavin Williams commented on an issue
Re: Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError)
Issues are likely related.
Add Comment
Puppet / PUP-1544
Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError)
When trying to test some tweaks to support PUP-958, an issue has been encountered whereby Puppet is throwing the following error: {noformat} sudo bundle exec puppet resource package bash ensure=held /home/vagrant/puppet/lib/puppet/util/logging.rb:34:in `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError) f...
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.
Jira (PUP-1544) Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError)
Title: Message Title Gavin Williams created an issue Puppet / PUP-1544 Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError) Issue Type: Bug Affects Versions: 3.5.0 Assignee: Kylo Ginsberg Attachments: lib_puppet_type_package_rb.diff, lib_puppet_util_rb.diff Components: Types and Providers Created: 30/Jan/14 1:40 AM Priority: Normal Reporter: Gavin Williams When trying to test some tweaks to support PUP-958 , an issue has been encountered whereby Puppet is throwing the following error: sudo bundle exec puppet resource package bash ensure=held /home/vagrant/puppet/lib/puppet/util/logging.rb:34:in `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError) from /home/vagrant/puppet/lib/puppet/util/logging.rb:46:in `format_exception' from
Jira (PUP-1544) Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError)
Title: Message Title Gavin Williams updated an issue Puppet / PUP-1544 Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError) Change By: Gavin Williams Attachment: lib_puppet_type_package_rb.diff Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1544) Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError)
Title: Message Title Gavin Williams updated an issue Puppet / PUP-1544 Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError) Change By: Gavin Williams Attachment: lib_puppet_type_package_rb-2.diff Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1544) Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError)
Title: Message Title
Gavin Williams updated an issue
Puppet / PUP-1544
Puppet Logging - `format_exception': undefined method `message' for #Array:0x7f40783b5848 (NoMethodError)
Change By:
Gavin Williams
WhentryingtotestsometweakstosupportPUP-958,anissuehasbeenencounteredwherebyPuppetisthrowingthefollowingerror:{noformat}sudobundleexecpuppetresourcepackagebashensure=held/home/vagrant/puppet/lib/puppet/util/logging.rb:34:in`format_exception':undefinedmethod`message'for#Array:0x7f40783b5848(NoMethodError)from/home/vagrant/puppet/lib/puppet/util/logging.rb:46:in`format_exception'from/home/vagrant/puppet/lib/puppet/util/logging.rb:27:in`log_exception'from/home/vagrant/puppet/lib/puppet/util.rb:491:in`exit_on_fail'from/home/vagrant/puppet/lib/puppet/application.rb:367:in`run'from/home/vagrant/puppet/lib/puppet/context.rb:51:in`override'from/home/vagrant/puppet/lib/puppet.rb:224:in`override'from/home/vagrant/puppet/lib/puppet/application.rb:357:in`run'from/home/vagrant/puppet/lib/puppet/util/command_line.rb:137:in`run'from/home/vagrant/puppet/lib/puppet/util/command_line.rb:91:in`execute'from/home/vagrant/puppet/bin/puppet:4from/usr/lib/ruby/gems/1.8/bin/puppet:19:in`load'from/usr/lib/ruby/gems/1.8/bin/puppet:19{noformat}Thisiswiththeattachedlib_puppet_type_package_rb -2
Jira (PUP-1542) Puppet::Util::Log requires a message
Title: Message Title
Gavin Williams commented on an issue
Re: Puppet::Util::Log requires a message
Tried to do some ruby-debug tracing of this issue - Not sure if it's of any value...
Output is: https://gist.github.com/fatmcgav/8689846#file-ruby-debug-output
Add Comment
Puppet / PUP-1542
Puppet::Util::Log requires a message
When trying to add holdable support to the yum package provider under PUP-958, the following error is being thrown when attempting to catch an exception invoking 'provider.hold'. {noformat} $ sudo bundle exec puppet resource package bash ensure=held --trace Error: /Package[bash]: Could not evaluate: Puppet::Util::Log requires a message /mnt/data/Pu...
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
Jira (PUP-1457) fail should be usable in a selector
Title: Message Title
Gavin Williams commented on an issue
Re: fail should be usable in a selector
Migrated this in case it's become easier to address with the future parser???
Add Comment
Puppet / PUP-1457
fail should be usable in a selector
It would be nice if this worked better: pre notify { test: message = $environment ? { production = http://blah/blah/prod, development = http://blah/blah/dev, default = fail(environment '${environment}' is not yet supported), } } /pre Desired result when the default branch of the selector is taken...
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.
Jira (PUP-1391) puppet device cannot create certs when run as root
Title: Message Title Gavin Williams commented on an issue Re: puppet device cannot create certs when run as root Have migrated this one from Redmine, as have been emailed by someone attempting to use my NetApp Device module who has hit this same error... Can we get a fix in for it? Add Comment Puppet / PUP-1391 puppet device cannot create certs when run as root broken -- output of `puppet device --debug` when ran as root: pre info: Creating a new SSL key for 10.0.1.3 err: Could not request certificate: Could not write /var/opt/lib/pe-puppet/devices/10.0.1.3/ssl/private_keys/10.0.1.3.pem to privatekeydir: Permission denied - /var/opt/lib/pe-puppet/devices/10.0.1.3/ssl/private_keys/10.0.1.3.pem /pre suc... 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
