Jira (PUP-8084) Hiera lookup failed when using serialized regex in yaml
Title: Message Title
Olivier Hanesse commented on PUP-8084
Re: Hiera lookup failed when using serialized regex in yaml
Thanks for your answer. In fact, explicit lookup didn't work either.
The aim of having a regexp in "hiera yaml" was to generate a yaml file from that hash that need to get regexp as key (searchguard plugin configuration for elasticsearch) To do that, I was using a function with a "hash.to_yaml"
Now in Hiera, I put a string like ''!ruby/regexp ^foo-\S*' , and I wrote to function to get a real regexp in my hash before converting it to a yaml file.
def transform_regexpkeys_to_regexp(value)
return value if not value.is_a?(Hash)
hash = value.inject({}) { |memo,(k,v)|
memo[k.start_with?('!ruby/regexp') ? Regexp.new(k.gsub(/!ruby\/regexp /,'')) : k] = transform_regexpkeys_to_regexp(v); memo
}
return hash
end
And I got the same yaml output as with earlier Puppet version Maybe I could write this function using Puppet Language only
Jira (PUP-8084) Hiera lookup failed when using serialized regex in yaml
Title: Message Title Olivier Hanesse commented on PUP-8084 Re: Hiera lookup failed when using serialized regex in yaml Thanks for this quick and detailed answer ! I will try to adapt my configuration not to use APL for this parameter. 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-8084) Hiera lookup failed when using serialized regex in yaml
Title: Message Title
Olivier Hanesse updated an issue
Puppet / PUP-8084
Hiera lookup failed when using serialized regex in yaml
Change By:
Olivier Hanesse
Hello, There is a regression in the handling of serialized regexps in yaml ( http://yaml.org/YAML_for_ruby.html#regexps); starting with Puppet 4.10.2 an error occured about a type mismatch.{color:red}[ ... ] has wrong type, expects Puppet::LookupValue, got Hash[Regexp[/a.b/] [...] at [...]{color}Steps to reproduce :Using Docker, it is easy to reproduce :In a repository, create the following files * _+ data/common.yaml +_ {code}foo::bar: !ruby/regexp '/a.b/':'test': {}{code} * +_data data /hiera5.yaml _+ {code}---version: 5hierarchy: - name: Common path: common.yaml defaults: data_hash: yaml_data datadir: /tmp/bug_puppet/data {code} * _+ data/foo.pp +_ {code}class foo ( $bar = 'Toto',){ notify{"${bar}":}}node /.*/{ class{'foo':}}{code} * _+ Dockerfile +_ {code}ARG PUPPET_VERSION=latestFROM puppet/puppet-agent:${PUPPET_VERSION}RUN mkdir /tmp/bug_puppet/ADD . /tmp/bug_puppet{code}Then run the following commands :{code}for i in 1.9.3 1.9.2 1.9.1 1.10.1 1.10.2 1.10.3 1.10.4 ; do docker build --build-arg PUPPET_VERSION=$i . -t puppet-test:$i ; donefor i in 1.9.3 1.9.2 1.9.1 1.10.1 1.10.2 1.10.3 1.10.4 ; do echo "Puppet Version $i "; docker run -it --rm puppet-test:$i apply --hiera_config /tmp/bug_puppet/data/hiera5.yaml /tmp/bug_puppet/data/foo.pp ; done{code}You will see the following output : {code}for i in 1.9.3 1.9.2 1.9.1 1.10.1 1.10.2 1.10.3 1.10.4 ; do echo "Puppet Version $i "; docker run -it --rm puppet-test:$i apply --hiera_config /tmp/bug_puppet/data/hiera5.yaml /tmp/bug_puppet/data/foo.pp ; donePuppet Version 1.9.3 Notice: Compiled catalog for e8d8df813253 in environment production in 0.06 secondsNotice: {(?-mix:a.b) => {test => {}}}Notice: /Stage[main]/Foo/Notify[{(?-mix:a.b) => {test => {}}}]/message: defined 'message' as '{(?-mix:a.b) => {test => {}}}'Notice: Applied catalog in 0.02 secondsPuppet Version 1.9.2 Notice: Compiled catalog for 763be4c8093e in environment production in 0.06 secondsNotice: {(?-mix:a.b) => {test => {}}}Notice: /Stage[main]/Foo/Notify[{(?-mix:a.b) => {test => {}}}]/message: defined 'message' as '{(?-mix:a.b) => {test => {}}}'Notice: Applied catalog in 0.02 secondsPuppet Version 1.9.1 Notice: Compiled catalog for 51794a142499 in environment production in 0.06 secondsNotice: {(?-mix:a.b) => {test => {}}}Notice: /Stage[main]/Foo/Notify[{(?-mix:a.b) => {test => {}}}]/message: defined 'message' as '{(?-mix:a.b) => {test => {}}}'Notice: Applied catalog in 0.02 secondsPuppet Version 1.10.1 Notice: Compiled catalog for b037e978fee2 in environment production in 0.07 secondsNotice: {(?-mix:a.b) => {test => {}}}Notice: /Stage[main]/Foo/Notify[{(?-mix:a.b) => {test => {}}}]/message: defined 'message' as '{(?-mix:a.b) => {test => {}}}'Notice: Applied catalog in 0.02 secondsPuppet Version 1.10.2 Error: Evaluation Error: Error while evaluating a Resource Statement, Lookup of key 'foo::bar' failed: Value for key 'foo::bar', in hash returned from data_hash function 'yaml_data', when using location '/tmp/bug_puppet/data/common.yaml', has wrong type, expects Puppet::LookupValue, got Hash[Regexp[/a.b/], Hash[String, Hash[0, 0],
Jira (PUP-8084) Hiera lookup failed when using serialized regex in yaml
Title: Message Title
Olivier Hanesse updated an issue
Puppet / PUP-8084
Hiera lookup failed when using serialized regex in yaml
Change By:
Olivier Hanesse
Hello, There is a regression in the handling of serialized regexps in yaml ( http://yaml.org/YAML_for_ruby.html#regexps); starting with Puppet 4.10.2 an error occured about a type mismatch.{color:red}[ ... ] has wrong type, expects Puppet::LookupValue, got Hash[Regexp[/a.b/] [...] at [...]{color}Steps to reproduce :Using Docker, it is easy to reproduce :In a repository, create the following files * _+data/common.yaml +_{code}foo::bar: !ruby/regexp '/a.b/':'test': {}{code} * +_data/hiera5.yaml _+{code}---version: 5hierarchy: - name: Common path: common.yaml defaults: data_hash: yaml_data datadir: /tmp/bug_puppet/data {code} * _+ data/foo.pp +_{code}class foo ( $bar = 'Toto',){ notify{"${bar}":}}node /.*/{ class{'foo':}}{code}* _+Dockerfile+_{code}ARG PUPPET_VERSION=latestFROM puppet/puppet-agent:${PUPPET_VERSION}RUN mkdir /tmp/bug_puppet/ADD . /tmp/bug_puppet{code}Then run the following commands :{code}for i in 1.9.3 1.9.2 1.9.1 1.10.1 1.10.2 1.10.3 1.10.4 ; do docker build --build-arg PUPPET_VERSION=$i . -t puppet-test:$i ; donefor i in 1.9.3 1.9.2 1.9.1 1.10.1 1.10.2 1.10.3 1.10.4 ; do echo "Puppet Version $i "; docker run -it --rm puppet-test:$i apply --hiera_config /tmp/bug_puppet/data/hiera5.yaml /tmp/bug_puppet/data/foo.pp ; done{code}You will see the following output : {code}for i in 1.9.3 1.9.2 1.9.1 1.10.1 1.10.2 1.10.3 1.10.4 ; do echo "Puppet Version $i "; docker run -it --rm puppet-test:$i apply --hiera_config /tmp/bug_puppet/data/hiera5.yaml /tmp/bug_puppet/data/foo.pp ; donePuppet Version 1.9.3 Notice: Compiled catalog for e8d8df813253 in environment production in 0.06 secondsNotice: {(?-mix:a.b) => {test => {}}}Notice: /Stage[main]/Foo/Notify[{(?-mix:a.b) => {test => {}}}]/message: defined 'message' as '{(?-mix:a.b) => {test => {}}}'Notice: Applied catalog in 0.02 secondsPuppet Version 1.9.2 Notice: Compiled catalog for 763be4c8093e in environment production in 0.06 secondsNotice: {(?-mix:a.b) => {test => {}}}Notice: /Stage[main]/Foo/Notify[{(?-mix:a.b) => {test => {}}}]/message: defined 'message' as '{(?-mix:a.b) => {test => {}}}'Notice: Applied catalog in 0.02 secondsPuppet Version 1.9.1 Notice: Compiled catalog for 51794a142499 in environment production in 0.06 secondsNotice: {(?-mix:a.b) => {test => {}}}Notice: /Stage[main]/Foo/Notify[{(?-mix:a.b) => {test => {}}}]/message: defined 'message' as '{(?-mix:a.b) => {test => {}}}'Notice: Applied catalog in 0.02 secondsPuppet Version 1.10.1 Notice: Compiled catalog for b037e978fee2 in environment production in 0.07 secondsNotice: {(?-mix:a.b) => {test => {}}}Notice: /Stage[main]/Foo/Notify[{(?-mix:a.b) => {test => {}}}]/message: defined 'message' as '{(?-mix:a.b) => {test => {}}}'Notice: Applied catalog in 0.02 secondsPuppet Version 1.10.2 Error: Evaluation Error: Error while evaluating a Resource Statement, Lookup of key 'foo::bar' failed: Value for key 'foo::bar', in hash returned from data_hash function 'yaml_data', when using location '/tmp/bug_puppet/data/common.yaml', has wrong type, expects Puppet::LookupValue, got Hash[Regexp[/a.b/], Hash[String, Hash[0, 0], 1, 1], 1, 1] at
Jira (PUP-8084) Hiera lookup failed when using serialized regex in yaml
Title: Message Title Olivier Hanesse created an issue Puppet / PUP-8084 Hiera lookup failed when using serialized regex in yaml Issue Type: Bug Affects Versions: PUP 5.3.2, PUP 4.10.2 Assignee: Thomas Hallgren Components: Hiera & Lookup Created: 2017/10/24 7:51 AM Fix Versions: PUP 4.10.1 Labels: hiera yaml Priority: Normal Reporter: Olivier Hanesse Hello, There is a regression in the handling of serialized regexps in yaml ( http://yaml.org/YAML_for_ruby.html#regexps); starting with Puppet 4.10.2 an error occured about a type mismatch. [ ... ] has wrong type, expects Puppet::LookupValue, got Hash[Regexp[/a.b/] [...] at [...]
Jira (PUP-6698) create_resources does not honor '@@resource' as exported resource
Title: Message Title Olivier Hanesse commented on PUP-6698 Re: create_resources does not honor '@@resource' as exported resource Hello, I think https://tickets.puppetlabs.com/browse/PA-513 seems to be related to this issue (puppet bug and not a puppet agent issue) Regards 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 (PDB-2256) Regression/Performance Issue introduced by PDB-135
Title: Message Title Olivier Hanesse created an issue PuppetDB / PDB-2256 Regression/Performance Issue introduced by PDB-135 Issue Type: Bug Affects Versions: PDB 3.2.2, PDB 3.2.1, PDB 3.2.0 Assignee: Unassigned Created: 2015/12/13 4:32 AM Priority: Normal Reporter: Olivier Hanesse Hello, I got a regression/performance issue using puppetdb-termini, version > 3.2 PR #1640 has introduced a warning message when using invalid UTF-8 sequence. The issue is located here : https://github.com/puppetlabs/puppetdb/blob/master/puppet/lib/puppet/util/puppetdb/char_encoding.rb#L38 This function just takes forever to complete when using a "big" catalog. Step to reproduce : It's pretty easy, you just need to trigger this function (so with a catalog with some non UTF-8 caracters), and a "big" catalog. For example :
Jira (PDB-135) Improve warning message for invalid UTF-8 byte sequences
Title: Message Title Olivier Hanesse commented on PDB-135 Re: Improve warning message for invalid UTF-8 byte sequences Kenneth Barber Done. I've just created PDB-2256 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 (PDB-135) Improve warning message for invalid UTF-8 byte sequences
Title: Message Title Olivier Hanesse commented on PDB-135 Re: Improve warning message for invalid UTF-8 byte sequences Hello Everyone, I think, there is a regression with PR #1640. Indeed, using puppetdb-termini 3.2 (which includes this PR), puppetserver is "hanging" when sending catalog to PuppetDB. Catalog Compilation is working. My catalog contains a binary file (a kerberos keytab in fact), that is the cause of the hanging. If I use the "char_encoding.rb" file from version 3.1, sending catalog to puppetdb is working again. Do you want me to open a new ticket ? 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4450) Cannot load 'provider/network_route/routes.rb'
Title: Message Title Olivier Hanesse commented on PUP-4450 Re: Cannot load 'provider/network_route/routes.rb' Josh Cooper Thanks for the explanation. 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4450) Cannot load 'provider/network_route/routes.rb'
Title: Message Title
Olivier Hanesse commented on PUP-4450
Re: Cannot load 'provider/network_route/routes.rb'
Josh Cooper Help me understand please
In my case, I saw this kind of error in the puppetlabs-netscaler module. This module was working using Puppetmaster 3.x , but it isn't working using PuppetServer. So for me there is a regression somewhere. It can't be related to this old bug ?
And indeed, to bypass this issue, I replace {{ { require 'puppet/provider/netscaler' }
}}
by
{{ { require File.expand_path(File.join(File.dirname(__FILE__), '..', '..', '..', 'puppet', 'provider', 'netscaler.rb')) }
}}
which is kinda "ugly".
Regards
Olivier
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5428) Add a query string with environment when sending HTTP POST
Title: Message Title Olivier Hanesse updated an issue Puppet / PUP-5428 Add a query string with environment when sending HTTP POST Change By: Olivier Hanesse Summary: Add a query string with environment when requesting catalog ( sending HTTP POST call) 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5428) Add a query string with environment when requesting catalog (POST call)
Title: Message Title Olivier Hanesse commented on PUP-5428 Re: Add a query string with environment when requesting catalog (POST call) Hello, I've created a PR with a fix : https://github.com/puppetlabs/puppet/pull/4400 Regards Olivier 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5428) Add a query string with environment when requesting catalog (POST call)
Title: Message Title Olivier Hanesse commented on PUP-5428 Re: Add a query string with environment when requesting catalog (POST call) Do you need for information about this issue (can we call it a "bug" ?) Regards Olivier 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5428) Add a query string with environment when requesting catalog (POST call)
Title: Message Title
Olivier Hanesse updated an issue
Puppet / PUP-5428
Add a query string with environment when requesting catalog (POST call)
Change By:
Olivier Hanesse
Hello, When running a Puppet 4 run, every http call to PuppetServer includes a query string with the current "environment".{quote}GET /puppet/v3/node/test.dc01?environment=productionGET /puppet/v3/file_metadata/modules/concat/concatfragments.rb?environment=production...PUT /puppet/v3/report/test.dc01?environment=production& {quote}All except the POST to get the catalog {quote}POST /puppet/v3/catalog/test.dc01 HTTP/1.1{quote}It makes it hard to load-balance puppet load accross several puppetservers running differents environnments.Using Puppet3.x, the environment was in the uri, so it was easy to loadbalance :{quote} ProxyPassMatch ^/stable/ balancer://puppetserver timeout=600 RequestHeader set X-Client-DN "CN=%{SSL_CLIENT_S_DN_CN}e" ProxyPassReverse balancer://puppetserver {quote}Using Puppet4, I am using ModRewrite : {quote} RewriteCond \ \ %{QUERY_STRING} ^(.*)environment=production(.*)$ RewriteRule ^(.*) balancer://puppetserver$1 [P]{quote}It works well, except for the POST Catalog call.Is it possible to add also add a query string to this specific call ? RegardsOlivier
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
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-5428) Add a query string with environment when requesting catalog (POST call)
Title: Message Title
Olivier Hanesse updated an issue
Puppet / PUP-5428
Add a query string with environment when requesting catalog (POST call)
Change By:
Olivier Hanesse
Hello, When running a Puppet 4 run, every http call to PuppetServer includes a query string with the current "environment".{quote}GET /puppet/v3/node/test.dc01?environment=productionGET /puppet/v3/file_metadata/modules/concat/concatfragments.rb?environment=production...PUT /puppet/v3/report/test.dc01?environment=production& {quote}All except the POST to get the catalog {quote}POST /puppet/v3/catalog/test.dc01 HTTP/1.1{quote}It makes it hard to load-balance puppet load accross several puppetservers running differents environnments.Using Puppet3.x, the environment was in the uri, so it was easy to loadbalance :{quote} ProxyPassMatch ^/stable/ balancer://puppetserver timeout=600 RequestHeader set X-Client-DN "CN=%{SSL_CLIENT_S_DN_CN}e" ProxyPassReverse balancer://puppetserver {quote}Using Puppet4, I am using ModRewrite : {quote} RewriteCond \ %{QUERY_STRING} ^(.*)environment=production(.*)$ RewriteRule ^(.*) balancer://puppetserver$1 [P]{quote}It works well, except for the POST Catalog call.Is it possible to add also add a query string to this specific call ? RegardsOlivier
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
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-5428) Add a query string with environment when requesting catalog (POST call)
Title: Message Title Olivier Hanesse created an issue Puppet / PUP-5428 Add a query string with environment when requesting catalog (POST call) Issue Type: Bug Affects Versions: PUP 4.2.2, PUP 4.2.1, PUP 4.2.0, PUP 4.1.0, PUP 4.0.0 Assignee: Unassigned Created: 2015/10/24 2:14 AM Environment: Puppet 4.x agent Priority: Normal Reporter: Olivier Hanesse Hello, When running a Puppet 4 run, every http call to PuppetServer includes a query string with the current "environment". GET /puppet/v3/node/test.dc01?environment=production GET /puppet/v3/file_metadata/modules/concat/concatfragments.rb?environment=production... PUT /puppet/v3/report/test.dc01?environment=production& All except the POST to get the catalog POST /puppet/v3/catalog/test.dc01 HTTP/1.1 It makes it hard to load-balance puppet load accross several puppetservers running differents environnments. Using Puppet3.x, the
Jira (PUP-5428) Add a query string with environment when requesting catalog (POST call)
Title: Message Title
Olivier Hanesse updated an issue
Puppet / PUP-5428
Add a query string with environment when requesting catalog (POST call)
Change By:
Olivier Hanesse
Hello, When running a Puppet 4 run, every http call to PuppetServer includes a query string with the current "environment".{code}GET /puppet/v3/node/test.dc01?environment=productionGET /puppet/v3/file_metadata/modules/concat/concatfragments.rb?environment=production...PUT /puppet/v3/report/test.dc01?environment=production& {code}All except the POST to get the catalog {code}POST /puppet/v3/catalog/test.dc01 HTTP/1.1{code}It makes it hard to load-balance puppet load accross several puppetservers running differents environnments.Using Puppet3.x, the environment was in the uri, so it was easy to loadbalance :{code} ProxyPassMatch ^/stable/ balancer://puppetserver timeout=600 RequestHeader set X-Client-DN "CN=%{SSL_CLIENT_S_DN_CN}e" ProxyPassReverse balancer://puppetserver {code}Using Puppet4, I am using ModRewrite : {code} RewriteCond \\ %{QUERY_STRING} ^(.*)environment=production(.*)$ RewriteRule ^(.*) balancer://puppetserver$1 [P]{code}It works well, except for the POST Catalog call.Is it possible to add also add a query string to this specific call ? RegardsOlivier
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
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-5428) Add a query string with environment when requesting catalog (POST call)
Title: Message Title
Olivier Hanesse updated an issue
Puppet / PUP-5428
Add a query string with environment when requesting catalog (POST call)
Change By:
Olivier Hanesse
Hello, When running a Puppet 4 run, every http call to PuppetServer includes a query string with the current "environment".{ quote code }GET /puppet/v3/node/test.dc01?environment=productionGET /puppet/v3/file_metadata/modules/concat/concatfragments.rb?environment=production...PUT /puppet/v3/report/test.dc01?environment=production& { quote code }All except the POST to get the catalog { quote code }POST /puppet/v3/catalog/test.dc01 HTTP/1.1{ quote code }It makes it hard to load-balance puppet load accross several puppetservers running differents environnments.Using Puppet3.x, the environment was in the uri, so it was easy to loadbalance :{code} ProxyPassMatch ^/stable/ balancer://puppetserver timeout=600 RequestHeader set X-Client-DN "CN=%{SSL_CLIENT_S_DN_CN}e" ProxyPassReverse balancer://puppetserver {code}Using Puppet4, I am using ModRewrite : { quote code } RewriteCond \\%{QUERY_STRING} ^(.*)environment=production(.*)$ RewriteRule ^(.*) balancer://puppetserver$1 [P]{ quote code }It works well, except for the POST Catalog call.Is it possible to add also add a query string to this specific call ? RegardsOlivier
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
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
Jira (PUP-5428) Add a query string with environment when requesting catalog (POST call)
Title: Message Title
Olivier Hanesse updated an issue
Puppet / PUP-5428
Add a query string with environment when requesting catalog (POST call)
Change By:
Olivier Hanesse
Hello, When running a Puppet 4 run, every http call to PuppetServer includes a query string with the current "environment".{quote}GET /puppet/v3/node/test.dc01?environment=productionGET /puppet/v3/file_metadata/modules/concat/concatfragments.rb?environment=production...PUT /puppet/v3/report/test.dc01?environment=production& {quote}All except the POST to get the catalog {quote}POST /puppet/v3/catalog/test.dc01 HTTP/1.1{quote}It makes it hard to load-balance puppet load accross several puppetservers running differents environnments.Using Puppet3.x, the environment was in the uri, so it was easy to loadbalance :{ quote code } ProxyPassMatch ^/stable/ balancer://puppetserver timeout=600 RequestHeader set X-Client-DN "CN=%{SSL_CLIENT_S_DN_CN}e" ProxyPassReverse balancer://puppetserver { quote code }Using Puppet4, I am using ModRewrite : {quote} RewriteCond \\%{QUERY_STRING} ^(.*)environment=production(.*)$ RewriteRule ^(.*) balancer://puppetserver$1 [P]{quote}It works well, except for the POST Catalog call.Is it possible to add also add a query string to this specific call ? RegardsOlivier
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
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-4450) Cannot load 'provider/network_route/routes.rb'
Title: Message Title Olivier Hanesse commented on PUP-4450 Re: Cannot load 'provider/network_route/routes.rb' Hello I think I got the same issue with the puppetlabs-netscaler module : Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Resource Statement, Could not autoload puppet/type/netscaler_server: no such file to load – puppet/parameter/netscaler_name at test.pp:15:3 Regards Olivier Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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.
