Jira (PUP-6680) Descendant providers do not inherit features from ancestors
Title: Message Title Mikhail T. created an issue Puppet / PUP-6680 Descendant providers do not inherit features from ancestors Issue Type: Bug Affects Versions: PUP 3.8.7 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/09/05 6:44 PM Priority: Normal Reporter: Mikhail T. My package-provider is very simple – it derives from the stock gem-provider and overwrites gemcmd to use the gem-executable installed with RedHat's rh-ruby22 package for RHEL/CentOS-6 (where the default Ruby is 1.8.7): require 'puppet/provider/package'
Jira (PUP-620) (PR 2429) Add install_options to gem provider
Title: Message Title
Mikhail T. commented on PUP-620
Re: (PR 2429) Add install_options to gem provider
I can't get this to work either:
package {'sensu':
ensure => installed,
provider=> 'gem22',
install_options => ['--clear-sources', {'--source' => $gemsrc}],
}
While Puppet is running, I can see the gem's complete command-line – neither of the two install-options are on it:
/opt/rh/rh-ruby22/root/usr/bin/ruby /opt/rh/rh-ruby22/root/usr/bin/gem install --no-rdoc --no-ri sensu
The gem22 is our own little provider here, which descends from the official Puppet's gem by replacing the gemcmd:
require 'puppet/provider/package'
Jira (PUP-6290) Overriding evaluated resources silently changes its parameters wo re-eval
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6290
Overriding evaluated resources silently changes its parameters wo re-eval
Change By:
Henrik Lindberg
Acceptance Criteria:
That if a user defined resource has been evaluated and is overridden that one of the following actions are being taken by puppet:* {{\--strict=off}}: Silently skip, parameters overridden are change (current 4.6.2 behaviour)* {{\--strict=warning}}: Warn on each evaluated resource and skip (and current 4.6.2 behaviour)* {{\--strict=error}}: Error on override of evaluated resource, fail compilation.
Story Points:
1 2
Release Notes Summary:
Overriding attributes of user defined resources after the resources have been evaluated leads to an inconsistent catalog in that the parameters shown are not the actual values used to produce the content of the resource.Now, the {{\--strict}} flag will help find and correct these issues in manifests. A setting of {{{\--strict=off}} will continue to behave as it does now, a {{\--strict=warning}} will issue a warning for each override, and {{\--strict=error}} will fail the compilation.It is expected that a future version of puppet will always fail the compilation in this situation.
Release Notes:
Bug Fix
Add Comment
Jira (PUP-6290) Overriding evaluated resources silently changes its parameters wo re-eval
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6290 Overriding evaluated resources silently changes its parameters wo re-eval Change By: Henrik Lindberg Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6670) Newlines break Puppet tag validation
Title: Message Title Henrik Lindberg assigned an issue to Charlie Sharpsteen Puppet / PUP-6670 Newlines break Puppet tag validation Change By: Henrik Lindberg Assignee: Charlie Sharpsteen Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6669) Puppet should return better errors for Enum mismatches
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6669 Puppet should return better errors for Enum mismatches Change By: Henrik Lindberg Acceptance Criteria: That a type mismatch between an Enum and a String indicates the value of the String. Release Notes Summary: The error message shown when there is a type mismatch between and Enum data type and a String has been improved to show the value of the string. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6679) Error while evaluating function call, Invalid tag # in defined()
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-6679 Error while evaluating function call, Invalid tag # in defined() Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6679) Error while evaluating function call, Invalid tag # in defined()
Title: Message Title Matthias Hörmann assigned an issue to Henrik Lindberg Puppet / PUP-6679 Error while evaluating function call, Invalid tag # in defined() Change By: Matthias Hörmann Assignee: Matthias Hörmann Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6679) Error while evaluating function call, Invalid tag # in defined()
Title: Message Title Matthias Hörmann commented on PUP-6679 Re: Error while evaluating function call, Invalid tag # in defined() The problem seems to have disappeared after restarting the Puppetserver. It might be sensible to add some sort of detection to the running Puppetserver so it at least shows some sort of error when the Puppet-Agent files on disk are not the ones it initially loaded (or alternatively to purge the old ones when new ones are detected). Anyway, seems the lack of a restart was our fault. On a related note, is there a reason there are still no Debian packages for this release? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6679) Error while evaluating function call, Invalid tag # in defined()
Title: Message Title Matthias Hörmann commented on PUP-6679 Re: Error while evaluating function call, Invalid tag # in defined() We will try to produce a test case but the Puppetserver where this happens was installed after the Puppet 3->4 Migration so it should not have files in a different path. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6679) Error while evaluating function call, Invalid tag # in defined()
Title: Message Title Henrik Lindberg commented on PUP-6679 Re: Error while evaluating function call, Invalid tag # in defined() Matthias Hörmann The puppet::resource::type:0x61890ff6 is a reference to one particular resource instance - the number is the internal ID (basically a reference to the place that object is in memory. It will, as you noticed, change for every run). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6679) Error while evaluating function call, Invalid tag # in defined()
Title: Message Title Henrik Lindberg assigned an issue to Matthias Hörmann Puppet / PUP-6679 Error while evaluating function call, Invalid tag # in defined() Change By: Henrik Lindberg Assignee: Matthias Hörmann Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6679) Error while evaluating function call, Invalid tag # in defined()
Title: Message Title Henrik Lindberg commented on PUP-6679 Re: Error while evaluating function call, Invalid tag # in defined() I have not been able to recreate this problem with a simple test. Matthias Hörmann it would be great if you could reduce the failing code into a small reproducible example. I have one suspicion that you may have ended up with a broken installation hitting an older version of the defined function than the one shipping with puppet 4.6.2. Please investigate if you have an older puppet on the loadpath. (Others have had similar trange problems because of that). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6679) Error while evaluating function call, Invalid tag # in defined()
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6679 Error while evaluating function call, Invalid tag # in defined() Change By: Henrik Lindberg Priority: Critical Normal Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6679) Error while evaluating function call, Invalid tag # in defined()
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6679 Error while evaluating function call, Invalid tag # in defined() Change By: Henrik Lindberg Fix Version/s: PUP 4.6.3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6677) alias parameter in nagios_host type clashes with metaparameter alias
Title: Message Title Henrik Lindberg commented on PUP-6677 Re: alias parameter in nagios_host type clashes with metaparameter alias Matt Schuchard Target the oldest versions where you want to see the fix go in. For 3.x it is the 3.x branch, for 4.6.3 (currently) target 'stable', and for 4.7.8 (currently) target 'master'. The 4.6.7 release is planned to only be about packaging. Thanks for tackling this. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6679) Error while evaluating function call, Invalid tag # in defined()
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6679 Error while evaluating function call, Invalid tag # in defined() Change By: Henrik Lindberg Sprint: Language 2016-09-07 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6679) Error while evaluating function call, Invalid tag # in defined()
Title: Message Title Henrik Lindberg commented on PUP-6679 Re: Error while evaluating function call, Invalid tag # in defined() Upgraded this to Critical as it affects all calls to define that are given a resource reference. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6679) Error while evaluating function call, Invalid tag # in defined()
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6679 Error while evaluating function call, Invalid tag # in defined() Change By: Henrik Lindberg Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6679) Error while evaluating function call, Invalid tag # in defined()
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6679 Error while evaluating function call, Invalid tag # in defined() Change By: Henrik Lindberg Fix Version/s: PUP 4.6.3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6679) Error while evaluating function call, Invalid tag # in defined()
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6679 Error while evaluating function call, Invalid tag # in defined() Change By: Henrik Lindberg Labels: regression Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5834) Handle extended data in the catalog
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-5834
Handle extended data in the catalog
Change By:
Thomas Hallgren
In our current catalog format, parameters of a resource are encoded in json like this:{code:json}"parameters": { "description": "Parameters: regex is from http://docs.puppetlabs.com/puppet/3/reference/lang_reserved.html", "type": "object", "patternProperties": { "^[a-z][a-z0-9_]*$": {} }, "additionalProperties": false}{code}This is not enough as it does not allow for any non Json native types to be expressed.In order to retain the existing format, we should add a new "ext_parameters" that allows for more complex values (in particular {{Binary}} and {{Sensitive}}. {code:json} "ext_parameters": { "description": "Parameters: regex is from http://docs.puppetlabs.com/puppet/3/reference/lang_reserved.html", "type": "object", "patternProperties": { "^[a-z][a-z0-9_]*$": {} }, "additionalProperties": false}{code}The only difference is that the values of each json property is an object (the scheme should reflect that). The values are encoded using ext_properties encoding (since we need to be able handling a {{Binary}} inside of a {{Sensitive}}.In this ticket:* The catalog schema should be updated* The serialization should have a mechanism for ext_parameters* The deserialization should have a mechanism for ext_parameters* When serializing check the version of the catalog that will be produced, and fail if there is an attempt to serialize unsupported data types (i.e. the use case when older agent requests a catalog and the data is too advanced).* when this ticket is accepted, log tickets for other projects (PDB, Catalog Preview, etc.)* unit test both server (serialization), and client side (deserialization)This ticket is blocked by the Binary type (PUP-5831); as without it, there is no sensible data to serialize/deserialize as all such special types needs to be handled specifically at both ends.
Add Comment
Jira (PUP-4643) Add continue/next/break for iteration control
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-4643 Add continue/next/break for iteration control Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4643) Add continue/next/break for iteration control
Title: Message Title Thomas Hallgren commented on PUP-4643 Re: Add continue/next/break for iteration control Merged to master at 871e7b2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4643) Add continue/next/break for iteration control
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-4643 Add continue/next/break for iteration control Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6679) Error while evaluating function call, Invalid tag # in defined()
Title: Message Title
Matthias Hörmann updated an issue
Puppet / PUP-6679
Error while evaluating function call, Invalid tag # in defined()
Change By:
Matthias Hörmann
Environment:
With the puppet-agent package for 1 Puppetserver 2 . 6 5 . 2 from the Puppetlabs repositories 0 on a RHEL Puppetmaster (what is up with that being in there for RHEL/Centos but not Debian/... btw?) we get the following error{code:puppetlog}Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, Invalid tag '#' at /etc/puppetlabs/code/environments/development20/modules/saltweb/manifests/config.pp:692:11 at /etc/puppetlabs/code/environments/development20/common/saltpwportal/manifests/init.pp:18 on node bpobs11.bpo.pwit.com{code}The relevant line 692 it mentions is {code:puppet}if(!defined(Saltnagios::Client::Nrpe_Check["vhost_${provider}_${virtual_host}_long_requests"])) {{code}where character 11 is the start of the function name "defined".The type referenced is a defined type. All the variables are defined and the whole bit of code has been working fine for months now (with strict and strict_variables settings on).The hex code after #puppet:resource:type (presumably the memory location of the object) changes with every run but the error remains otherwise unchanged.A downgrade to Puppet Agent 1.6. 1 2 on the Master only fixes this issue.We are using Puppetserver 2.5.0-1.el7
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you
Jira (PUP-6679) Error while evaluating function call, Invalid tag # in defined()
Title: Message Title
Matthias Hörmann updated an issue
Puppet / PUP-6679
Error while evaluating function call, Invalid tag # in defined()
Change By:
Matthias Hörmann
With the puppet-agent package for 1.6.2 from the Puppetlabs repositories on a RHEL Puppetmaster (what is up with that being in there for RHEL/Centos but not Debian/... btw?) we get the following error{code:puppetlog}Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, Invalid tag '#' at /etc/puppetlabs/code/environments/development20/modules/saltweb/manifests/config.pp:692:11 at /etc/puppetlabs/code/environments/development20/common/saltpwportal/manifests/init.pp:18 on node bpobs11.bpo.pwit.com{code}The relevant line 692 it mentions is {code:puppet}if(!defined(Saltnagios::Client::Nrpe_Check["vhost_${provider}_${virtual_host}_long_requests"])) {{code}where character 11 is the start of the function name "defined".The type referenced is a defined type. All the variables are defined and the whole bit of code has been working fine for months now (with strict and strict_variables settings on).The hex code after #puppet:resource:type (presumably the memory location of the object) changes with every run but the error remains otherwise unchanged.A downgrade to 1.6.1 on the Master only fixes this issue.We are using Puppetserver 2.5.0-1.el7
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are
Jira (PUP-6679) Error while evaluating function call, Invalid tag # in defined()
Title: Message Title Matthias Hörmann created an issue Puppet / PUP-6679 Error while evaluating function call, Invalid tag # in defined() Issue Type: Bug Affects Versions: PUP 4.6.2 Assignee: Unassigned Components: Breaking Change Created: 2016/09/05 12:38 AM Environment: With the puppet-agent package for 1.6.2 from the Puppetlabs repositories on a RHEL Puppetmaster (what is up with that being in there for RHEL/Centos but not Debian/... btw?) we get the following error Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, Invalid tag '#' at /etc/puppetlabs/code/environments/development20/modules/saltweb/manifests/config.pp:692:11 at /etc/puppetlabs/code/environments/development20/common/saltpwportal/manifests/init.pp:18 on node bpobs11.bpo.pwit.com The relevant line 692 it mentions is
