Jira (PUP-10112) no_proxy config setting is ignored when http_proxy environment variable is set
Title: Message Title Josh Cooper commented on PUP-10112 Re: no_proxy config setting is ignored when http_proxy environment variable is set This was already fixed in 6.9.0 and up (in PUP-9990), so the fix version should only be 5.5.x and 6.4.x Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332037.1571955273000.9881.1572302100262%40Atlassian.JIRA.
Jira (PUP-10112) no_proxy config setting is ignored when http_proxy environment variable is set
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10112 no_proxy config setting is ignored when http_proxy environment variable is set Change By: Josh Cooper Release Notes Summary: Fixes a bug where puppet would attempt to use a proxy specified in the HTTP_PROXY environment variable, even though Puppet[:no_proxy] said to bypass the proxy. Note to docs: This was already fixed in 6.8.0 and up (in PUP-9990), so the fix version should only be 5.5.x and 6.4.x Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332037.1571955273000.9879.1572302100255%40Atlassian.JIRA.
Jira (PUP-10112) no_proxy config setting is ignored when http_proxy environment variable is set
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10112 no_proxy config setting is ignored when http_proxy environment variable is set Change By: Josh Cooper Release Notes Summary: Fixes a bug where puppet would attempt to use a proxy specified in the HTTP_PROXY environment variable, even though Puppet[:no_proxy] said to bypass the proxy.Note to docs: This was already fixed in 6. 8 9 .0 and up (in PUP-9990), so the fix version should only be 5.5.x and 6.4.x Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332037.1571955273000.9882.1572302100266%40Atlassian.JIRA.
Jira (PUP-10112) no_proxy config setting is ignored when http_proxy environment variable is set
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10112 no_proxy config setting is ignored when http_proxy environment variable is set Change By: Josh Cooper Release Notes Summary: Fixes a bug where puppet would attempt to use a proxy specified in the HTTP_PROXY environment variable, even though Puppet[:no_proxy] said to bypass the proxy. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332037.1571955273000.9875.1572302040200%40Atlassian.JIRA.
Jira (PUP-10112) no_proxy config setting is ignored when http_proxy environment variable is set
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10112 no_proxy config setting is ignored when http_proxy environment variable is set Change By: Josh Cooper Fix Version/s: PUP 6.4.5 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332037.1571955273000.9876.1572302040204%40Atlassian.JIRA.
Jira (PUP-10112) no_proxy config setting is ignored when http_proxy environment variable is set
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10112 no_proxy config setting is ignored when http_proxy environment variable is set Change By: Josh Cooper Summary: Backport PUP-9990 no_proxy config setting is ignored when http_proxy environment variable is set Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332037.1571955273000.9873.1572301980095%40Atlassian.JIRA.
Jira (PUP-10112) Backport PUP-9990
Title: Message Title Kris Bosland commented on PUP-10112 Re: Backport PUP-9990 Merged to 5.5.x at 3c8cd54. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332037.1571955273000.9838.1572301080069%40Atlassian.JIRA.
Jira (PUP-10115) "glob" matches are not sorted in alphanumerical order as documented, but in directory order instead
Title: Message Title Henrik Lindberg commented on PUP-10115 Re: "glob" matches are not sorted in alphanumerical order as documented, but in directory order instead Moved ticket to PUP project since HI project is for deprecated Hiera 3 only. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332258.1572282843000.9746.1572299280176%40Atlassian.JIRA.
Jira (PUP-10115) "glob" matches are not sorted in alphanumerical order as documented, but in directory order instead
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-10115 "glob" matches are not sorted in alphanumerical order as documented, but in directory order instead Change By: Henrik Lindberg Component/s: Hiera & Lookup Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332258.1572282843000.9748.1572299280181%40Atlassian.JIRA.
Jira (PUP-10115) "glob" matches are not sorted in alphanumerical order as documented, but in directory order instead
Title: Message Title Henrik Lindberg moved an issue Puppet / PUP-10115 "glob" matches are not sorted in alphanumerical order as documented, but in directory order instead Change By: Henrik Lindberg Key: HI PUP - 614 10115 Project: Hiera Puppet Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332258.1572282843000.9744.1572299220129%40Atlassian.JIRA.
Jira (PUP-10106) no_proxy does not exclude hosts whose FQDN matches based on suffix
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10106 no_proxy does not exclude hosts whose FQDN matches based on suffix Change By: Josh Cooper Fix Version/s: PUP 6.11.0 Fix Version/s: PUP 6.4.5 Fix Version/s: PUP 5.5.18 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.330903.157151114.9664.1572297300598%40Atlassian.JIRA.
Jira (PUP-10106) no_proxy does not exclude hosts whose FQDN matches based on suffix
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10106
no_proxy does not exclude hosts whose FQDN matches based on suffix
Change By:
Josh Cooper
*Puppet Version: 5.5.17* *Puppet Server Version: 5.3.10* *OS Name/Version: CentOS 7* *Original Summary* Since update to puppet 5.5.17 puppetdb forge module cannot connect to puppetdbSince the update to puppet agent 5.5.17 the puppetdb forge module is using the configured proxy server and ignoring the no_proxy setting when trying to validate the connection to puppetdb. This worked properly on 5.5.16. My environment proxy settings are: * {noformat} http_proxy=http://ottinstall.ls.cbn:3128 * * ftp_proxy=http://ottinstall.ls.cbn:3128 * * https_proxy=http://ottinstall.ls.cbn:3128 * * no_proxy=ls.cbn, localhost, puppet, 127.0.0.1 * {noformat} My puppetdb server is: * {{ https://glycon.ls.cbn:8081 * }} *Desired Behavior:* Respect the no_proxy value {{ ls.cbn }} and not proxy connections to {{ https://glycon.ls.cbn:8018 }} *Actual Behavior:* {noformat} opening connection to ottinstall.ls.cbn:3128...opened<- "CONNECT glycon.ls.cbn:8081 HTTP/1.1\r\nHost: glycon.ls.cbn:8081\r\n\r\n"-> "HTTP/1.1 403 Forbidden\r\n"-> "Server: squid/3.5.20\r\n"-> "Mime-Version: 1.0\r\n"-> "Date: Sat, 19 Oct 2019 18:46:40 GMT\r\n"-> "Content-Type: text/html;charset=utf-8\r\n"-> "Content-Length: 3448\r\n"-> "X-Squid-Error: ERR_ACCESS_DENIED 0\r\n"-> "Vary: Accept-Language\r\n"-> "Content-Language: en\r\n"-> "X-Cache: MISS from ottinstall.ls.cbn\r\n"-> "X-Cache-Lookup: NONE from ottinstall.ls.cbn:80\r\n"-> "Via: 1.1 ottinstall.ls.cbn (squid/3.5.20)\r\n"-> "Connection: keep-alive\r\n"-> "\r\n"Conn close because of connect error 403 "Forbidden"Notice: Unable to connect to puppetdb server (https://glycon.ls.cbn:8081): 403 "Forbidden" {noformat}
Add Comment
Jira (PUP-10106) no_proxy does not exclude hosts whose FQDN matches based on suffix
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-10106 no_proxy does not exclude hosts whose FQDN matches based on suffix Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.330903.157151114.9649.1572296940255%40Atlassian.JIRA.
Jira (PUP-10106) no_proxy does not exclude hosts whose FQDN matches based on suffix
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10106 no_proxy does not exclude hosts whose FQDN matches based on suffix Change By: Josh Cooper Summary: no_proxy does not exclude hosts whose FQDN matches based on su suffix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.330903.157151114.9622.1572296820166%40Atlassian.JIRA.
Jira (PUP-10106) no_proxy does not exclude hosts whose FQDN matches based on su
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10106 no_proxy does not exclude hosts whose FQDN matches based on su Change By: Josh Cooper Summary: Since update to puppet 5.5.17 puppetdb forge module cannot connect to puppetdb no_proxy does not exclude hosts whose FQDN matches based on su Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.330903.157151114.9620.1572296820157%40Atlassian.JIRA.
Jira (HI-614) "glob" matches are not sorted in alphanumerical order as documented, but in directory order instead
Title: Message Title Alexander Kurtz created an issue Hiera / HI-614 "glob" matches are not sorted in alphanumerical order as documented, but in directory order instead Issue Type: Bug Assignee: Unassigned Created: 2019/10/28 10:14 AM Priority: Normal Reporter: Alexander Kurtz Puppet Version: 5.5.10 Puppet Server Version: 5.5.10 OS Name/Version: Debian GNU/Linux 10 (buster) The documentation for the glob keyword says the following: glob String One shell-like glob pattern, which might match any number of files. If multiple files are found, Hiera searches all of them in alphanumerical order. However, hiera actually seems to parse the files matching a glob in directory order instead: Consider this environment: # puppet --version 5.5.10 # hiera --version 3.2.0
Jira (PUP-10113) Functions are slower if called with chained syntax than with prefix syntax
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-10113 Functions are slower if called with chained syntax than with prefix syntax Change By: Jorie Tappa Team: Server Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332233.1572273925000.9062.1572281280387%40Atlassian.JIRA.
Jira (PUP-10113) Functions are slower if called with chained syntax than with prefix syntax
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-10113 Functions are slower if called with chained syntax than with prefix syntax Change By: Jorie Tappa Sub-team: Language Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332233.1572273925000.9066.1572281280417%40Atlassian.JIRA.
Jira (PUP-10114) Do not exclude variables explicitly set to `undef` in ParameterScope to_hash method
Title: Message Title Cas Donoghue created an issue Puppet / PUP-10114 Do not exclude variables explicitly set to `undef` in ParameterScope to_hash method Issue Type: Improvement Assignee: Cas Donoghue Created: 2019/10/28 9:20 AM Priority: Normal Reporter: Cas Donoghue Optionally include parameters which have been explicitly set to `undef` when calling the to the to_hash method for the Puppet::Parser::Scope::ParameterScope class. This work enables passing variables from Bolt plan scope accross the apply boundry. See Bolt issue 1288 for more details. https://github.com/puppetlabs/bolt/issues/1288 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10113) Functions are slower if called with chained syntax than with prefix syntax
Title: Message Title Thomas Hallgren commented on PUP-10113 Re: Functions are slower if called with chained syntax than with prefix syntax It's likely that we have the same performance issue in pops/evaluator/access_operator.rb (method accessObject line 31). I think a specialized infer_callable (or similar name) method that would return nil in case the given value don't have that such a type could make a lot of difference. AFAICT, only PObjectType, PObjectTypeExtension and PURIType implements TypeWithMembers. The current @api private method TypeCalculator.infer_Object could serve as model for this new method. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332233.1572273925000.8852.1572276540093%40Atlassian.JIRA.
Jira (PUP-10113) Functions are slower if called with chained syntax than with prefix syntax
Title: Message Title
Henrik Lindberg commented on PUP-10113
Re: Functions are slower if called with chained syntax than with prefix syntax
The peformance issue is this bit in the evaluator:
def eval_CallMethodExpression(o, scope)
unless o.functor_expr.is_a? Model::NamedAccessExpression
fail(Issues::ILLEGAL_EXPRESSION, o.functor_expr, {:feature=>'function accessor', :container => o})
end
receiver = unfold([], [o.functor_expr.left_expr], scope)
name = o.functor_expr.right_expr
unless name.is_a? Model::QualifiedName
fail(Issues::ILLEGAL_EXPRESSION, o.functor_expr, {:feature=>'function name', :container => o})
end
name = name.value # the string function name
obj = receiver[0]
receiver_type = Types::TypeCalculator.infer(obj)
Jira (PUP-10113) Functions are slower if called with chained syntax than with prefix syntax
Title: Message Title
Dimitri Tischenko updated an issue
Puppet / PUP-10113
Functions are slower if called with chained syntax than with prefix syntax
Change By:
Dimitri Tischenko
*Puppet Version: 5.5.17* *Puppet Server Version: 2018.1* *OS Name/Version: Centos 7* *Desired Behavior:*As documented in [https://puppet.com/docs/puppet/5.5/lang_functions.html#chained-function-calls], chained function call syntax should result in same behaviour as prefixed syntax.*Actual Behavior:*Using chained syntax results in slower performance of the function call. The performance depends on the size of the object "before the dot".{{Examples:}} {{ Run puppet apply test.pp --debug --profile}}Please see attached: * test.pp * test.log
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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.
Jira (PUP-10113) Functions are slower if called with chained syntax than with prefix syntax
Title: Message Title
Dimitri Tischenko updated an issue
Puppet / PUP-10113
Functions are slower if called with chained syntax than with prefix syntax
Change By:
Dimitri Tischenko
*Puppet Version: 5.5.17* *Puppet Server Version: 2018.1* *OS Name/Version: Centos 7* *Desired Behavior:*As documented in [ here|[ https://puppet.com/docs/puppet/5.5/lang_functions.html#chained-function-calls] ] , chained function call syntax should result in same behaviour as prefixed syntax.*Actual Behavior:*Using chained syntax results in slower performance of the function call. The performance depends on the size of the object "before the dot". {{ Examples: }} {{ Run ` puppet apply test.pp --debug --profile ` }} Please see attached: * test.pp * test.log
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
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-10113) Functions are slower if called with chained syntax than with prefix syntax
Title: Message Title Dimitri Tischenko commented on PUP-10113 Re: Functions are slower if called with chained syntax than with prefix syntax Henrik Lindberg is aware of this and already has a fix. Also pinging Thomas Hallgren for visibility. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332233.1572273925000.8757.1572274020183%40Atlassian.JIRA.
Jira (PUP-10113) Functions are slower if called with chained syntax than with prefix syntax
Title: Message Title Dimitri Tischenko created an issue Puppet / PUP-10113 Functions are slower if called with chained syntax than with prefix syntax Issue Type: Bug Affects Versions: PUP 5.5.16 Assignee: Unassigned Attachments: test.log, test.pp Created: 2019/10/28 7:45 AM Environment: test.pp test.log Priority: Normal Reporter: Dimitri Tischenko Puppet Version: 5.5.17 Puppet Server Version: 2018.1 OS Name/Version: Centos 7 Desired Behavior: As documented [here|https://puppet.com/docs/puppet/5.5/lang_functions.html#chained-function-calls], chained function call syntax should result in same behaviour as prefixed syntax. Actual Behavior: Using chained syntax results in slower performance of the function call. The performance depends on the size of the object "before the dot". Examples: Run `puppet apply test.pp --debug --profile` Please see attached: test.pp test.log
Jira (FACT-2087) Memory fact for Sles
Title: Message Title Alexandru Popa assigned an issue to Alexandru Popa Facter / FACT-2087 Memory fact for Sles Change By: Alexandru Popa Assignee: Alexandru Popa Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332228.157227112.8700.1572271140284%40Atlassian.JIRA.
Jira (FACT-2087) Memory fact for Sles
Title: Message Title Alexandru Popa created an issue Facter / FACT-2087 Memory fact for Sles Issue Type: Task Assignee: Unassigned Created: 2019/10/28 6:58 AM Priority: Normal Reporter: Alexandru Popa Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit
Jira (FACT-2086) Use core facts when weight of custom facts is 0
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2086 Use core facts when weight of custom facts is 0 Change By: Bogdan Irimie Assignee: Bogdan Irimie Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332226.1572268497000.8655.1572268560136%40Atlassian.JIRA.
Jira (FACT-2086) Use core facts when weight of custom facts is 0
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2086 Use core facts when weight of custom facts is 0 Change By: Bogdan Irimie Issue Type: Bug Task Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332226.1572268497000.8654.1572268560122%40Atlassian.JIRA.
Jira (FACT-2086) Use core facts when weight of custom facts is 0
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2086 Use core facts when weight of custom facts is 0 Issue Type: Bug Assignee: Unassigned Created: 2019/10/28 6:14 AM Priority: Normal Reporter: Bogdan Irimie Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit
Jira (FACT-2085) Fix formatting for non existing facts.
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2085 Fix formatting for non existing facts. Issue Type: Bug Assignee: Unassigned Created: 2019/10/28 4:13 AM Priority: Normal Reporter: Bogdan Irimie cfacter non_existant non_existant2 non_existant => non_existant2 => ./bin/facter-ng non_existent non_existant2 facter-ng doesn't output anything. Same problem for json and yaml outputs.
Jira (FACT-2084) Fix crash when user query cannot be resolved
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2084 Fix crash when user query cannot be resolved Change By: Bogdan Irimie Assignee: Bogdan Irimie Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332215.1572260782000.8581.1572260820218%40Atlassian.JIRA.
Jira (FACT-2084) Fix crash when user query cannot be resolved
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2084 Fix crash when user query cannot be resolved Issue Type: Bug Assignee: Unassigned Created: 2019/10/28 4:06 AM Priority: Normal Reporter: Bogdan Irimie When a user query that cannot be resolved is issues, facter fails with /home/jordi/repos/facter-ng/lib/framework/formatters/hocon_fact_formatter.rb:15:in `format': undefined method `empty?' for nil:NilClass (NoMethodError) This was reported in issue #106 on github. Add Comment
Jira (FACT-2082) Create facts for sles operating system
Title: Message Title Alexandru Popa updated an issue Facter / FACT-2082 Create facts for sles operating system Change By: Alexandru Popa Sub-team: ghost Team/s: Night's Watch Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332208.157225580.8541.1572255960323%40Atlassian.JIRA.
Jira (FACT-2083) Kernel facts for Sles
Title: Message Title Alexandru Popa created an issue Facter / FACT-2083 Kernel facts for Sles Issue Type: Task Assignee: Unassigned Created: 2019/10/28 2:45 AM Priority: Normal Reporter: Alexandru Popa Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit
Jira (FACT-2083) Kernel facts for Sles
Title: Message Title Alexandru Popa assigned an issue to Alexandru Popa Facter / FACT-2083 Kernel facts for Sles Change By: Alexandru Popa Assignee: Alexandru Popa Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332209.1572255939000.8544.1572255960350%40Atlassian.JIRA.
Jira (FACT-2082) Create facts for sles operating system
Title: Message Title Alexandru Popa created an issue Facter / FACT-2082 Create facts for sles operating system Issue Type: Epic Assignee: Unassigned Created: 2019/10/28 2:43 AM Priority: Normal Reporter: Alexandru Popa Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit
Jira (PUP-10102) Systemd provider is not correctly selected on Alpine Linux
Title: Message Title
Christoph Maser commented on PUP-10102
Re: Systemd provider is not correctly selected on Alpine Linux
Mihai Buzgau this basically happens with any unit test where you call a class containing a service. one example of our internal code failing:
# frozen_string_literal: true
require 'spec_helper'
describe 'pocu_base::rsyslog', type: 'class' do
context 'default' do
on_supported_os.each do |os, facts|
context "on #{os}" do
let(:facts) do
facts
end
it { is_expected.to compile }
it {
Jira (PUP-10102) Systemd provider is not correctly selected on Alpine Linux
Title: Message Title Mihai Buzgau commented on PUP-10102 Re: Systemd provider is not correctly selected on Alpine Linux Christoph Maser is the code open-source? can you point me to the tests that are failing? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.329403.1571128033000.8515.1572249060120%40Atlassian.JIRA.
Jira (PUP-10016) Systemd provider is not correctly selected as the service provider if puppet is run as non root
Title: Message Title Christoph Maser commented on PUP-10016 Re: Systemd provider is not correctly selected as the service provider if puppet is run as non root IMHO this is not sufficient for docker testing environments, there PID1 is not systemd, systemd might not even be installed, which is totally acceptable for the catalogue tests. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324178.1568121391000.8503.1572248700594%40Atlassian.JIRA.
Jira (PUP-10102) Systemd provider is not correctly selected on Alpine Linux
Title: Message Title Christoph Maser commented on PUP-10102 Re: Systemd provider is not correctly selected on Alpine Linux Mihai Buzgau some tests run in docker containeres which don't have systemd installed, which don't have systemd as PID 1 and which don't need privileges. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.329403.1571128033000.8500.1572248460151%40Atlassian.JIRA.
