Jira (PUP-3759) Undefined method for `variable' for :undef:Symbol at...
Title: Message Title Henrik Lindberg commented on PUP-3759 Re: Undefined method for `variable' for :undef:Symbol at... The working example, since it interpolates an undefined variable is fine as an undefined value is then rendered as an empty string. When passed directly it reaches the function as :undef. Functions have to correctly deal with :undef (undefined values) - i.e. something that needs to be addressed in the custom function, not in puppet. Note that in 4.0.0 the handling of undefined values has changes, and when used with the new puppet 4 function API, undefined values are simply Ruby nil, and there is no (at least 'a lot less') confusion over undefined values and how to handle them. Closing this as a non fix, as the problem is really in the custom code. 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-3689) Complex merging not working
Title: Message Title Rene Last updated an issue Puppet / PUP-3689 Complex merging not working Solved this issue. PE 3.7 needs the deep_merge gem installed inside the puppetserver (inside jvm). Running puppetserver gem install deep_merge fixed this issue for me. Maybe this needs be made clear(er) in the docs? Change By: Rene Last Component/s: CatalogApplication Component/s: DOCS Issue Type: Bug Improvement 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
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Gabriele Paggi commented on PUP-1515 Re: Invalid parameter provider for custom types/providers So, to summarize: when the Puppet master loads a Type, it searches the environment that the agent requested. When it loads providers for that type, it searches the default environment instead of the one the agent requested. Charlie Sharpsteen, what is the name of the default environment? Is it production? I'm seeing the same issue with only one environment named prd. The workaround I'm using is to define a production environment pointing to the same directories as the prd one: # Always create production pointing to the first defined environment # to circumvent PUP-1515 (pluginsync, custom provider/type) [production] manifest = /etc/puppet/environments/prd/manifests/ modulepath = /etc/puppet/environments/prd/. [prd] manifest = /etc/puppet/environments/prd/manifests/ modulepath = /etc/puppet/environments/prd/..
Jira (FACT-767) facter always prints the parsed but returned an empty data set
Title: Message Title Laurent Bigonville created an issue Facter / FACT-767 facter always prints the parsed but returned an empty data set Issue Type: Bug Affects Versions: FACT 2.2.0 Assignee: Eric Sorenson Created: 2014/12/11 4:12 AM Priority: Minor Reporter: Laurent Bigonville Hello, I've a custom fact that is not always returning new facts. On the machine nothing is returned I get Fact file /etc/puppetlabs/facter/facts.d/foo.sh was parsed but returned an empty data set Shouldn't this be only be displayed when the --debug flag is passed? https://docs.puppetlabs.com/facter/2.3/custom_facts.html#troubleshooting seems to imply so. Cheers, Add Comment
Jira (FACT-767) facter always prints the parsed but returned an empty data set warning
Title: Message Title Laurent Bigonville updated an issue Facter / FACT-767 facter always prints the parsed but returned an empty data set warning Change By: Laurent Bigonville Summary: facteralwaysprintstheparsedbutreturnedanemptydataset warning 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 (PDB-1061) PR (1175): Allow tilde in resource name, like in puppet - saimonn
Title: Message Title gepetto-bot commented on PDB-1061 Re: PR (1175): Allow tilde in resource name, like in puppet - saimonn hlindberg commented: @kbarber sorry no clue what is going on without setting this up and debugging. If the tilde is in a tag, and it is specified that tags cannot contain one then clearly it is a bug in Puppet. There has been recent changes on master in how tags are computed and set that the problem should be tested against. I suggest logging a jira ticket for puppet. 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-1515) Invalid parameter provider for custom types/providers
Title: Message Title Charlie Sharpsteen commented on PUP-1515 Re: Invalid parameter provider for custom types/providers Gabriele Paggi The default environment for the master is usually, almost nearly always production. Specifically, the default is whatever the environment setting has been set to in the master section of puppet.conf. Since most people don't set that, production is used. You can check what the value of the default environment is by running the following on a Puppet master: puppet config print --section master environment 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 (PDB-1034) Ezbake: switch source based tests to use ezbake somehow and retire that old code
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1034 Ezbake: switch source based tests to use ezbake somehow and retire that old code Change By: Kenneth Barber TheezbakeworkinPDB-663introducedezbakebutwe'renotabletoshedtheoldbuildcodeuntilwehavesourcebasedinstallationsworking.Thistickettrackstheworknecessarytomakethathappen.Twoideasfornow:a) Wesomehowopensourceorrelease Usethe ezbake (sincewetest helpersalready in EC2now) beakertobuildandinstalllocallyonajenkinsslaveshipthetarballtoanec2instance so that wecan build runmake on abox it . Thismightbeagoodtimetoimplementtheleinpluginidea. b)WedoPRtestingwithpackages,butuseRoger'spipeliningideatodothis.Eitherwayourgoalsshouldbe:PRtestsstillwork,andthatoldcodeisdead. 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 (PDB-1034) Ezbake: switch source based tests to use ezbake somehow and retire that old code
Title: Message Title Kenneth Barber commented on PDB-1034 Re: Ezbake: switch source based tests to use ezbake somehow and retire that old code Sent out this email to the PuppetDB team, and to Wayne Warren, Matthaus Owens, Christopher Price, Roger Ignazio and Alice Nodelman for review and visibility: TL;DR source based builds for PuppetDB + ezbake patches up, please review So I've managed to get some patches raised now for the ezbake beaker changes required to support source based installations for PR testing and one off runs. This is the second phase of the PuppetDB ezbake cutover, currently for PR testing and source based testing it is using the old packaging methodology to do this, but that has to go, since it no longer reflects proper 'shipped' reality. This is a 3-way patch, and is reasonably complex to follow, I do apoligise: ezbake: https://github.com/puppetlabs/ezbake/pull/157 beaker: https://github.com/puppetlabs/beaker/pull/571 puppetdb: https://github.com/puppetlabs/puppetdb/pull/1179 I would appreciate some review when people have the time. These are WIP for now, as I expect some more changes to come after discussion, and I anticipate some testing failures potentially, but for now they are good to review at least. Without a doubt, the beaker patch includes the largest set of changes FWIW, the rest are pretty minor in LoC but potentially big in breaking compatibility potential. Here are the tests I've been running, in particular the latest one just before I raised the PR's: https://jenkins.puppetlabs.com/view/PuppetDB/view/Other%20Builds/job/platform_puppetdb_intn-sys_pr2/54/ And the existing production PR testing is here: https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/287/ FYI: there is a transient failure in that second test, due to a maven download error, which can be fixed in the future with a proper maven mirror. FYI: There is also currently a bug on Beaker 2.0.0 and RHEL 7 that kills off SSH connections (I think something changed in the way we manage sshd_config) so please ignore that failure for now (its raised here: https://tickets.puppetlabs.com/browse/QENG-1594). Primarily the things to note: Source based installations need to support the same installation methodology as packages, so I've moved the package build tasks into the Makefile. Some of the actions were already moved over, this moves almost everything over now, so the Makefile is authoritative. I expect this to be something worth discussing. The ezbake helpers are now much dumber, and simpler for the singleton
Jira (PUP-3760) 'puppet agent --test' not getting the configuration and no error is return
Title: Message Title David Truong created an issue Puppet / PUP-3760 'puppet agent --test' not getting the configuration and no error is return Issue Type: Bug Affects Versions: PUP 3.7.2 Assignee: Kylo Ginsberg Components: Client Created: 2014/12/11 11:38 AM Priority: Normal Reporter: David Truong Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (PUP-3759) Undefined method for `variable' for :undef:Symbol at...
Title: Message Title
Adam T Backer commented on PUP-3759
Re: Undefined method for `variable' for :undef:Symbol at...
thanks for the reply, Henrik Lindberg. I think I failed to mention that the variable $ {mycorp::dns::master}
is not an empty string, it was intended to be implied with the comment '#set to any hostname'.
Looks like I also failed to mention I am using the future parser
From this specific working example, I have the following:
modules/mycorp/manifests/dns.pp:
class mycorp::dns {
$master = dns101.qa.mycorp.com
}
Is there something wrong with my scoping? Should it be ${::mycorp::dns::master} when using the future parser? Apologies for opening a non-issue, I've only started using the future parser a couple days ago and am not very knowledgeable on all the changes.
Cheers!
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (PUP-3759) Undefined method for `variable' for :undef:Symbol at...
Title: Message Title
Adam T Backer updated an issue
Puppet / PUP-3759
Undefined method for `variable' for :undef:Symbol at...
Change By:
Adam T Backer
IthinkI'vediscoveredaformofaregressionofoldPuppettrackerbug#8783(https://projects.puppetlabs.com/issues/8783)I'mrunningonUbuntu14.04withruby-1.9.3.484-2ubuntu1.2(viatheubunturuby1.9.1package--ThxUbuntu.)andpuppet-3.7.3-1puppetlabs1 withparser=future Irunmasterless,andhavethefollowingcustomparserfunctiondefinedinmodule:modules/mycorp/lib/puppet/parser/functions/get_ip_addr.rb{noformat}require'resolv'modulePuppet::Parser::Functionsnewfunction(:get_ip_addr,:type=:rvalue)do|args|#SupersexyregextomatchvalidIPsip_addr_re=/\b(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\b/hostname=args[0].stripdns=Resolv::DNS.newifhostname=~ip_addr_rethenreturnhostnameendbeginreturndns.getaddresshostnamerescueResolv::ResolvErrorreturn''endendend{noformat}Whencalledvia:
Jira (PUP-3759) Undefined method for `variable' for :undef:Symbol at...
Title: Message Title
Adam T Backer updated an issue
Puppet / PUP-3759
Undefined method for `variable' for :undef:Symbol at...
Change By:
Adam T Backer
IthinkI'vediscoveredaformofaregressionofoldPuppettrackerbug#8783(https://projects.puppetlabs.com/issues/8783)I'mrunningonUbuntu14.04withruby-1.9.3.484-2ubuntu1.2(viatheubunturuby1.9.1package--ThxUbuntu.)andpuppet-3.7.3-1puppetlabs1withparser=futureIrunmasterless,andhavethefollowingcustomparserfunctiondefinedinmodule:modules/mycorp/lib/puppet/parser/functions/get_ip_addr.rb{noformat}require'resolv'modulePuppet::Parser::Functionsnewfunction(:get_ip_addr,:type=:rvalue)do|args|#SupersexyregextomatchvalidIPsip_addr_re=/\b(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\b/hostname=args[0].stripdns=Resolv::DNS.newifhostname=~ip_addr_rethenreturnhostnameendbeginreturndns.getaddresshostnamerescueResolv::ResolvErrorreturn''endendend{noformat}Whencalledvia:inmodules/mycorp/manifests/dns.pp:{noformat} classmycorp::dns { $master=dns101.qa.mycorp.com}{
Jira (PUP-3759) Undefined method for `variable' for :undef:Symbol at...
Title: Message Title
Adam T Backer updated an issue
Puppet / PUP-3759
Undefined method for `variable' for :undef:Symbol at...
Change By:
Adam T Backer
IthinkI'vediscoveredaformofaregressionofoldPuppettrackerbug#8783(https://projects.puppetlabs.com/issues/8783)I'mrunningonUbuntu14.04withruby-1.9.3.484-2ubuntu1.2(viatheubunturuby1.9.1package--ThxUbuntu.)andpuppet-3.7.3-1puppetlabs1withparser=futureIrunmasterless,andhavethefollowingcustomparserfunctiondefinedinmodule:modules/mycorp/lib/puppet/parser/functions/get_ip_addr.rb{noformat}require'resolv'modulePuppet::Parser::Functionsnewfunction(:get_ip_addr,:type=:rvalue)do|args|#SupersexyregextomatchvalidIPsip_addr_re=/\b(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\b/hostname=args[0].stripdns=Resolv::DNS.newifhostname=~ip_addr_rethenreturnhostnameendbeginreturndns.getaddresshostnamerescueResolv::ResolvErrorreturn''endendend{noformat}Whencalledvia: inmodules/mycorp/manifests/dns.pp: {noformat} {noformat}{noformat}
Jira (PUP-3760) 'puppet agent --test' not getting the configuration and no error is return
Title: Message Title
David Truong updated an issue
Puppet / PUP-3760
'puppet agent --test' not getting the configuration and no error is return
Change By:
David Truong
Environment:
LinuxCentOS6.5andRedHat6.5
WhenIranpuppetapplymanifests/site.ppthecommandisapplylocallyonpuppetserverhost.FromtheagenthostIexecute'puppetagent--test'thecommanddoesnotgetapply.Outputfrom'puppetagent--test'Info:RetrievingpluginfactsInfo:RetrievingpluginInfo:LoadingfactsInfo:Cachingcatalogforops-mon.cisco.comInfo:Applyingconfigurationversion'1418326352'Notice:Finishedcatalogrunin1.68secondsHereisthecontentsfromsite.pp,node'dev-catalog-1.novalocal'{includebvt}nodedefault{includebvt}classbvt{exec{'Runcommandonops-mon':command='/bin/echoPuppetdeploymentHelloWorld!`/bin/date`/root/psc/DT/PuppetTest.txt'}}
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
Jira (PUP-3760) 'puppet agent --test' not getting the configuration and no error is return
Title: Message Title
David Truong updated an issue
Puppet / PUP-3760
'puppet agent --test' not getting the configuration and no error is return
Change By:
David Truong
Attachment:
debug.txt
WhenIranpuppetapplymanifests/site.ppthecommandisapplylocallyonpuppetserverhost.FromtheagenthostIexecute'puppetagent--test'thecommanddoesnotgetapply. I'vealsoattachdebugfilefrom'puppetagent--test--debug'.Iwouldimagineiftheconfigurationdidnotgetapplythereshouldbesomeinformativeerror. Thanksinadvance. Outputfrom'puppetagent--test'Info:RetrievingpluginfactsInfo:RetrievingpluginInfo:LoadingfactsInfo:Cachingcatalogforops-mon.cisco.comInfo:Applyingconfigurationversion'1418326352'Notice:Finishedcatalogrunin1.68secondsHereisthecontentsfromsite.pp,node'dev-catalog-1.novalocal'{includebvt}nodedefault{includebvt}classbvt{exec{'Runcommandonops-mon':command='/bin/echoPuppetdeploymentHelloWorld!`/bin/date`/root/psc/DT/PuppetTest.txt'}}
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
Jira (PUP-3759) Undefined method for `variable' for :undef:Symbol at...
Title: Message Title Adam T Backer commented on PUP-3759 Re: Undefined method for `variable' for :undef:Symbol at... You can also see from the notice line and the provided log that the variable passed to the function is not undef Notice: Scope(Class[Mycorp::Docker::Dnscache]): Setting DNS Master (dns101.qa.mycorp.com) to 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 (FACT-768) Add the option to re-use existing vbscripts to be used for executable facts.
Title: Message Title
Tim Purkerson created an issue
Facter / FACT-768
Add the option to re-use existing _vbscript_s to be used for executable facts.
Issue Type:
New Feature
Assignee:
Eric Sorenson
Components:
PE
Created:
2014/12/11 1:34 PM
Priority:
Normal
Reporter:
Tim Purkerson
User would like to add the option to re-use existing _vbscript_s to be used for executable facts.
Here is the information from their ticket:
Hi, we like the option to re-use existing _vbscript_s to be used for executable facts. This is really easy by putting the below in facter/util/parser.rb (mostly a copy of the powershell part). (No we don't want to execute _vbscript_ from batch file just as you don't want that for powershell). Can this functionality be added to the product so the windows agent gets that? Thanks, looking forward to your response.
Executes and parses the key value output of _vbscript_/Windows Scripting Format scripts class _vbscript_Parser Base
Returns a hash of facts from _vbscript_ output def parse_results cscript = if File.exists?(# {ENV['SYSTEMROOT']}\\sysnativecscript.exe) #{ENV['SYSTEMROOT']}
\\sysnativecscript.exe elsif File.exists?(# {ENV['SYSTEMROOT']}\\system32cscript.exe) #{ENV['SYSTEMROOT']}
Jira (PUP-3761) puppet agent --onetime not honored
Title: Message Title Dan Bode created an issue Puppet / PUP-3761 puppet agent --onetime not honored Issue Type: Bug Assignee: Unassigned Created: 2014/12/11 2:38 PM Priority: Normal Reporter: Dan Bode when running the following command: puppet agent --noop puppet-master.service.consul --test --onetime (NOTE: --onetime added for clarify here, it is also part of the --test alias) I get the following error: Notice: Skipping run of Puppet configuration client; administratively disabled (Reason: 'Disabled by default on new installations'); Use 'puppet agent --enable' to re-enable. After reading about - enable, it looks like I would not want to enable this option ( -onetime means that I just want to run puppet once, and I don't necessarily want it to run in the background. It seems as if --test, --onetime, and --no-daemonize, have been rendered unsupported by this admin lock. Am I missing something, or are these options not going to be supported anymore? That would be a shame b/c they were really useful
Jira (PUP-3736) OpenBSD service provider should restart a service when flags are changed
Title: Message Title Peter Huene updated an issue Puppet / PUP-3736 OpenBSD service provider should restart a service when flags are changed Change By: Peter Huene Component/s: Community 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-3736) OpenBSD service provider should restart a service when flags are changed
Title: Message Title Peter Huene assigned an issue to Peter Huene Puppet / PUP-3736 OpenBSD service provider should restart a service when flags are changed Change By: Peter Huene Assignee: PeterHuene 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-3759) Undefined method for `variable' for :undef:Symbol at...
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3759 Undefined method for `variable' for :undef:Symbol at... Change By: Henrik Lindberg Affects Version/s: PUP3.7.3 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-3759) Undefined method for `variable' for :undef:Symbol at...
Title: Message Title Henrik Lindberg commented on PUP-3759 Re: Undefined method for `variable' for :undef:Symbol at... Maybe I closed this too quickly and may have misread something. Will take a second look. 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-3759) Undefined method for `variable' for :undef:Symbol at...
Title: Message Title Adam T Backer commented on PUP-3759 Re: Undefined method for `variable' for :undef:Symbol at... Your comments encouraged me to look a little deeper and I was able to replicate this in future and current parser. I was able to make this work by making modifications to the usage of Resolv module (calling Resolv.getaddress directly instead of via Resolv.new – not sure why this made a difference.) and making the call as desired (get_ip_addr($variable)) produced the desired result. Thanks for looking, apologies for the bad report 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-3618) Include pkgng provider for FreeBSD
Title: Message Title Peter Huene assigned an issue to Unassigned Puppet / PUP-3618 Include pkgng provider for FreeBSD Change By: Peter Huene Assignee: PeterHuene 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-3760) 'puppet agent --test' not getting the configuration and no error is return
Title: Message Title David Truong assigned an issue to David Truong Puppet / PUP-3760 'puppet agent --test' not getting the configuration and no error is return Change By: David Truong Assignee: KyloGinsberg DavidTruong 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-3760) 'puppet agent --test' not getting the configuration and no error is return
Title: Message Title
David Truong updated an issue
Puppet / PUP-3760
'puppet agent --test' not getting the configuration and no error is return
Change By:
David Truong
WhenIranpuppetapplymanifests/site.ppthecommandisapplylocallyonpuppetserverhost.FromtheagenthostIexecute'puppetagent--test'thecommanddoesnotgetapply.I'vealsoattachdebugfilefrom'puppetagent--test--debug'.Iwouldimagineiftheconfigurationdidnotgetapplythereshouldbesomeinformativeerror.Thanksinadvance.Outputfrom'puppetagent--test'Info:RetrievingpluginfactsInfo:RetrievingpluginInfo:LoadingfactsInfo:Cachingcatalogforops-mon.cisco.comInfo:Applyingconfigurationversion'1418326352'Notice:Finishedcatalogrunin1.68secondsHereisthecontentsfromsite.pp,node' dev ops - catalog-1 mon . novalocal domain-name '{includebvt}nodedefault{includebvt}classbvt{exec{'Runcommandonops-mon':command='/bin/echoPuppetdeploymentHelloWorld!`/bin/date`/root/psc/DT/PuppetTest.txt'}}
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-3759) Undefined method for `variable' for :undef:Symbol at...
Title: Message Title Henrik Lindberg commented on PUP-3759 Re: Undefined method for `variable' for :undef:Symbol at... I glad you found the problem. It was hard to see any details from the trace since it is a trace from a run that did not seem to use future parser. I can only speculate that the Resolve.new lead to some object being produced and returned to puppet that it could then no act on. The reported problem being related to :undef may actually be an error occuring when trying to report the actual problem. The real problem seems to related to applying the operator == on something puppet does not like. 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.
