Jira (PUP-5603) Unset metaparameters throw strict_variables errors
Title: Message Title Thomas Hallgren commented on PUP-5603 Re: Unset metaparameters throw strict_variables errors This bug should be fixed as part of the refactoring made for 4.x parameter signatures in PUP-4458 . Perhaps you are running with a Puppet version older than 4.3.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-5602) Expand puppet functions: return types, return values
Title: Message Title Igor Galić created an issue Puppet / PUP-5602 Expand puppet functions: return types, return values Issue Type: Task Assignee: Nicholas Fagerlund Components: DOCS Created: 2015/12/12 9:23 AM Priority: Normal Reporter: Igor Galić as a followup to PUP-5561 , i pointed out that the current doc is missing a few important points: is there a possibility to declare the return type? is the return value (like in ruby), simply the last value in the block? a full example, or two…
Jira (FACT-1280) Empty 'aio_agent_version' fact on AIO agent
Title: Message Title Antoine Cotten commented on FACT-1280 Re: Empty 'aio_agent_version' fact on AIO agent Thanks for the answer Josh. My assumption was that this fact was set regardless of the environment (Enterprise or Open Source), and I think this is something that could benefit to everyone. The reason is simple: some Linux distributions like Fedora provide Puppet 4.1 packages in their repositories, and rely on other OS packages like ruby, etc. Therefore Puppet itself is installed in standard OS paths (/usr, /var, /etc) instead of /opt. I can think about at least one problem caused by this: if one can not determine whether Puppet was installed using OS packages or the AIO package, it is simply impossible to guess what provider to use when installing a package as a Ruby Gem. In one case there is puppet_gem, which uses a hardcoded path and is expected to be the default with FOSS AIO agents, in the other case there is gem, which is the only acceptable option when Puppet is using the system/os ruby, like i.e. Fedora does. 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 (FACT-1280) Empty 'aio_agent_version' fact on AIO agent
Title: Message Title Antoine Cotten assigned an issue to Josh Cooper Facter / FACT-1280 Empty 'aio_agent_version' fact on AIO agent Change By: Antoine Cotten Assignee: Antoine Cotten Josh Cooper 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-5603) Unset metaparameters throw strict_variables errors
Title: Message Title Bob Vincent created an issue Puppet / PUP-5603 Unset metaparameters throw strict_variables errors Issue Type: Bug Affects Versions: PUP 4.0.0 Assignee: Unassigned Created: 2015/12/12 12:42 PM Environment: Puppet 4.0+ with strict_variables=true Fix Versions: PUP 5.0.0 Priority: Normal Reporter: Bob Vincent The documentation for metaparameters implies that they are available to every resource, but when strict_variables=true, unset metaparameters are not assigned default values. The following code fails with strict_variables=true
Jira (FACT-1284) Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result
Title: Message Title Michael Smith updated an issue Facter / FACT-1284 Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result Change By: Michael Smith Labels: PE regression 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-5603) Unset metaparameters throw strict_variables errors
Title: Message Title Bob Vincent commented on PUP-5603 Re: Unset metaparameters throw strict_variables errors The maestrodev/wget module suffers from this bug. See my workaround here. 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-5603) Unset metaparameters throw strict_variables errors
Title: Message Title
Bob Vincent updated an issue
Puppet / PUP-5603
Unset metaparameters throw strict_variables errors
Change By:
Bob Vincent
The documentation for metaparameters implies that they are available to every resource, but when strict_variables=true, some unset metaparameters are not assigned default values.In the following test code, neither the $name and nor the $schedule metaparameters are explicitly set, but only the $schedule reference aborts compilation. {noformat:title=The following code fails with strict_variables=true}B { schedule => undef,}define a { notify { $name:message => 'Success', }}define b { a { $name:schedule => $schedule, }}b { 'no schedule': }{noformat}{panel:title=Error}Evaluation Error: Unknown variable: 'schedule'. at test.pp:11:17{panel}{noformat:title=Explicitly setting the metaparameter results in a warning}define a { notify { $name:message => 'Success', }}define b ( $schedule = undef,){ a { $name:schedule => $schedule, }}b { 'no schedule': }{noformat}{panel:title=Warning}schedule is a metaparam; this value will inherit to all contained resources in the b definition{panel}{noformat:title=Currently, I am using the following ugly workaround}define a { notify { $name:message => 'Success', }}define b { $strict = defined('$::settings::strict_variables') and $::settings::strict_variables if $strict and !defined('$schedule') {$schedule = undef } a { $name:schedule => $schedule, }}b { 'no schedule': }{noformat}{panel:title=Notice}Success{panel}
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5603) Unset metaparameters throw strict_variables errors
Title: Message Title
Bob Vincent updated an issue
Puppet / PUP-5603
Unset metaparameters throw strict_variables errors
Change By:
Bob Vincent
The documentation for metaparameters implies that they are available to every resource, but when strict_variables=true, some unset metaparameters are not assigned default values. In the following test code, neither the $name and $schedule metaparameters are explicitly set, but only the $schedule reference aborts compilation. {noformat:title=The following code fails with strict_variables=true}B { schedule => undef,}define a { notify { $name:message => 'Success', }}define b { a { $name:schedule => $schedule, }}b { 'no schedule': }{noformat}{panel:title=Error}Evaluation Error: Unknown variable: 'schedule'. at test.pp:11:17{panel}{noformat:title=Explicitly setting the metaparameter results in a warning}define a { notify { $name:message => 'Success', }}define b ( $schedule = undef,){ a { $name:schedule => $schedule, }}b { 'no schedule': }{noformat}{panel:title=Warning}schedule is a metaparam; this value will inherit to all contained resources in the b definition{panel}{noformat:title=Currently, I am using the following ugly workaround}define a { notify { $name:message => 'Success', }}define b { $strict = defined('$::settings::strict_variables') and $::settings::strict_variables if $strict and !defined('$schedule') {$schedule = undef } a { $name:schedule => $schedule, }}b { 'no schedule': }{noformat}{panel:title=Notice}Success{panel}
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (FACT-1284) Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result
Title: Message Title
Michael Smith created an issue
Facter / FACT-1284
Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/12/12 12:20 PM
Labels:
regression
Priority:
Normal
Reporter:
Michael Smith
The following worked with Facter 2, but produces an error in Facter 3.
Facter.add("foo") do
setcode do
Facter::Util::Resolution.exec('echo hello')
Jira (FACT-1284) Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result
Title: Message Title Michael Smith updated an issue Facter / FACT-1284 Facter::Util::Resolution.exec no longer sets $?.exitstatus based on exec result Change By: Michael Smith Affects Version/s: FACT 3.0.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-1072) support HTTP(S) URL as the file 'source'
Title: Message Title Felix Frank assigned an issue to Michael Smith Puppet / PUP-1072 support HTTP(S) URL as the file 'source' Change By: Felix Frank Assignee: Michael Smith 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-5604) Add journalctl command when service fails for systemd
Title: Message Title Peter Souter created an issue Puppet / PUP-5604 Add journalctl command when service fails for systemd Issue Type: Improvement Assignee: Unassigned Created: 2015/12/12 2:57 PM Priority: Normal Reporter: Peter Souter It's not super easy to diagnose issues when services fail to start with systemd: Error: Could not start Service[corosync]: Execution of '/usr/bin/systemctl start corosync' returned 1: Job for corosync.service failed. See 'systemctl status corosync.service' and 'journalctl -xn' for details. Would be nice to add some logic to actually run the journalctl for the service if it fails so we can get full details of the logs. Add Comment
Jira (PUP-5604) Add journalctl command when service fails for systemd
Title: Message Title Tim Meusel commented on PUP-5604 Re: Add journalctl command when service fails for systemd +1 for this. Would be great if Puppet could run "systemctl -u $servicewebroke --full". "-n linenumberthatwelike" would also be good so we don't blow up the output. 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-5604) Add journalctl command when service fails for systemd
Title: Message Title Peter Souter updated an issue Puppet / PUP-5604 Add journalctl command when service fails for systemd Change By: Peter Souter Labels: puppethack 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-4508) systemd provider should support manual
Title: Message Title Peter Souter updated an issue Puppet / PUP-4508 systemd provider should support manual Change By: Peter Souter Labels: puppethack 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.
