Jira (FACT-2618) Incorrect log format on non-executable external fact scripts
Title: Message Title Garrett Guillotte updated an issue Facter / FACT-2618 Incorrect log format on non-executable external fact scripts CC Jean Bond — this was an issue fixed in Facter 3.14.10/PE 2019.7 but did not have a JIRA ticket prior to the release. Can we get a release note for this? Change By: Garrett Guillotte Release Notes: Bug Fix Release Notes Summary: If an external fact script cannot be executed, Facter 3.14.9's logging will not indicate what happened, and instead outputs `error while processing "%1%" for external facts: %2%`. This is fixed in Facter 3.14.10, which will output the reported error. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2618) Incorrect log format on non-executable external fact scripts
Title: Message Title Garrett Guillotte created an issue Facter / FACT-2618 Incorrect log format on non-executable external fact scripts Issue Type: Bug Affects Versions: FACT 3.14.9 Assignee: Ciprian Badescu Created: 2020/05/15 5:57 PM Fix Versions: FACT 3.14.10 Priority: Normal Reporter: Garrett Guillotte Ciprian Badescu in https://github.com/puppetlabs/facter/commit/76a7bab5c75ff0b1b6a46cc7242582c24adf701d: Before this change, the log message format is wrong and the following is logged in case external facts file is not proper executable: 2020-04-09 15:07:49.499276 ERROR puppetlabs.facter - error while processing "%1%" for external facts: %2% After this fix, the proper message will be logged:
Jira (PUP-10500) Puppet settings catalog requires codedir to be a directory
Title: Message Title
Josh Cooper commented on PUP-10500
Re: Puppet settings catalog requires codedir to be a directory
I think this may only be an issue if confdir is a dangling symlink or if the symlink points to a file. If I create a symlink pointing to a directory:
$ bx puppet apply -e "file { '$HOME/.puppetlabs/etc/puppet-target': ensure => directory }; file { '$HOME/.puppetlabs/etc/puppet-conf': ensure => link, target => '$HOME/.puppetlabs/etc/puppet-target' }"
...
$ ls -la ~/.puppetlabs/etc/puppet-conf
lrwxr-xr-x 1 josh staff41B May 15 13:21 /Users/josh/.puppetlabs/etc/puppet-conf@ -> /Users/josh/.puppetlabs/etc/puppet-target
$ ls -la ~/.puppetlabs/etc/puppet-conf/
total 0
drwxr-xr-x 2 josh staff64B May 15 13:20 ./
drwxr-xr-x 6 josh staff 192B May 15 13:21 ../
Then puppet runs ok and resolves the confdir:
$ bx puppet apply -e 'notice($settings::confdir)' --confdir $HOME/.puppetlabs/etc/puppet-conf
Notice: Scope(Class[main]): /Users/josh/.puppetlabs/etc/puppet-conf
Jira (PUP-10513) Do not recursively type check collections when creating iterables in puppet functions
Title: Message Title Justin Stoller updated an issue Puppet / PUP-10513 Do not recursively type check collections when creating iterables in puppet functions Change By: Justin Stoller When a user calls the Puppet functions `map`, `each`, etc. we create a Puppet Iterator and proxy requests through it to the wrapped Ruby object. When creating a Puppet Iterator in this way we recursively infer the type of the entire collection passed in.Some times these Iterators are directly exposed to users ( via the non-block arities of `reverse_each` and `step`). Unfortunately, where we expose Iterators they may use all of Puppet's type system and may be specialized like "Iterator[String]" or "Iterator[Variant[Hash[String,String],Undef]]". Consequently, to be backwards compatible we will need to recursively check the type for these invocations. (Maybe we can deprecate and remove them in Puppet 7??)In every other case the Iterator is not exposed to the user. Either the original collection, a new, modified collection, or elements of one of the afore mentioned collections is returned.The method invoked in Puppet functions to create the Iterator Iterators is `Iterable.asserted_iterable`, and as far as I can tell, it does additional type checking that the dispatcher doesn't do and then largely discards the computed type information. We should should probably keep the call to asserted_iterable (assuming the additional type checking is a good thing to do there ) , but make it non-recursive where possible.Note, `asserted_iterable` defers to `Iterable.on` to do a lot of this work, `Iterable.on` is used by other aspects of the type system so we might want to keep existing calls to `Iterable.on` backwards compatible with those invocations. (We might also want to look into whether or not those calls are unnecessarily doing recursive type inference.) Add Comment
Jira (PUP-10513) Do not recursively type check collections when creating iterables in puppet functions
Title: Message Title Justin Stoller updated an issue Puppet / PUP-10513 Do not recursively type check collections when creating iterables in puppet functions Change By: Justin Stoller Environment: When a user calls the Puppet functions `map`, `each`, etc. we create a Puppet Iterator and proxy requests through it to the wrapped Ruby object. When creating a Puppet Iterator in this way we recursively infer the type of the entire collection passed in.Some times these Iterators are directly exposed to users (via the non-block arities of `reverse_each` and `step`). Unfortunately, where we expose Iterators they may use all of Puppet's type system and may be specialized like "Iterator[String]" or "Iterator[Variant[Hash[String,String],Undef]]". Consequently, to be backwards compatible we will need to recursively check the type for these invocations. (Maybe we can deprecate and remove them in Puppet 7??)In every other case the Iterator is not exposed to the user. Either the original collection, a new, modified collection, or elements of one of the afore mentioned collections is returned.The method invoked in Puppet functions to create the Iterators is `Iterable.asserted_iterable`, and as far as I can tell, it does additional type checking that the dispatcher doesn't do and then largely discards the computed type information. We should should probably keep the call to asserted_iterable (assuming the additional type checking is a good thing to do there), but make it non-recursive where possible.Note, `asserted_iterable` defers to `Iterable.on` to do a lot of this work, `Iterable.on` is used by other aspects of the type system so we might want to keep existing calls to `Iterable.on` backwards compatible with those invocations. (We might also want to look into whether or not those calls are unnecessarily doing recursive type inference.) Add Comment
Jira (PUP-10513) Do not recursively type check collections when creating iterables in puppet functions
Title: Message Title Justin Stoller updated an issue Puppet / PUP-10513 Do not recursively type check collections when creating iterables in puppet functions Change By: Justin Stoller (the method invoked in Puppet functions to create the Iterator) Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.359002.1589581228000.64008.1589581260131%40Atlassian.JIRA.
Jira (PUP-10513) Do not recursively type check collections when creating iterables in puppet functions
Title: Message Title Justin Stoller created an issue Puppet / PUP-10513 Do not recursively type check collections when creating iterables in puppet functions Issue Type: Task Assignee: Justin Stoller Created: 2020/05/15 3:20 PM Environment: When a user calls the Puppet functions `map`, `each`, etc. we create a Puppet Iterator and proxy requests through it to the wrapped Ruby object. When creating a Puppet Iterator in this way we recursively infer the type of the entire collection passed in. Some times these Iterators are directly exposed to users (via the non-block arities of `reverse_each` and `step`). Unfortunately, where we expose Iterators they may use all of Puppet's type system and may be specialized like "Iterator[String]" or "Iterator[Variant[Hash[String,String],Undef]]". Consequently, to be backwards compatible we will need to recursively check the type for these invocations. (Maybe we can deprecate and remove them in Puppet 7??) In every other case the Iterator is not exposed to the user. Either the original collection, a new, modified collection, or elements of one of the afore mentioned collections is returned. The method invoked in Puppet functions to create the Iterators is `Iterable.asserted_iterable`, and as far as I can tell, it does additional type checking that the dispatcher doesn't do and then largely discards the computed type information. We should should probably keep the call to asserted_iterable (assuming the additional type checking is a good thing to do there), but make it non-recursive where possible. Note, `asserted_iterable` defers to `Iterable.on` to do a lot of this work, `Iterable.on` is used by other aspects of the type system so we might want to keep existing calls to `Iterable.on` backwards compatible with those invocations. (We might also want to look into whether or not those calls are unnecessarily doing recursive type inference.) Priority: Normal Reporter: Justin Stoller
Jira (PUP-10247) Support ruby 2.7
Title: Message Title Rob Braden commented on PUP-10247 Re: Support ruby 2.7 Hadmut DanischWe provide tested, supported packages for 20.04 at http://apt.puppet.com/ Installing as a gem under Ruby 2.7 will not work until this ticket is completed. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.342962.1579675679000.63898.1589576940167%40Atlassian.JIRA.
Jira (PUP-10247) Support ruby 2.7
Title: Message Title Hadmut Danisch commented on PUP-10247 Re: Support ruby 2.7 Josh Cooper So how exactly do you expect puppet to be used on Ubuntu 20.04? Should it be used at all on Ubuntu 20.04? And if so: When? Forcing people into running that JDK stuff might scare many users just away. I currently do not see any concept here of getting puppet run in 20.04 and other recent distributions. You're currently committing some sort of suicide. People will drop puppet and move to other solutions like ansible or chef. 20.04 is out now for almost a month, but there's still no running solution for puppet on 20.04, but in an act of denying reality puppet claims that it has been tested on 20.04 (which is obviously incorrect since it just does not come on 20.04 with working packages) Maybe just let's face reality: Puppet Labs are unable to provide a running puppet for 20.04. Which more or less translates to puppet's death. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.342962.1579675679000.63806.1589573940087%40Atlassian.JIRA.
Jira (PDB-4734) subquery operator can take page order opts
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4734 subquery operator can take page order opts Issue Type: Bug Assignee: Unassigned Created: 2020/05/15 11:10 AM Priority: Normal Reporter: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.358968.158956
Jira (PUP-9251) Deprecate 'application orchestration' features
Title: Message Title Rob Braden updated an issue Puppet / PUP-9251 Deprecate 'application orchestration' features Change By: Rob Braden Fix Version/s: PUP 6.16.0 Fix Version/s: PUP 6.y Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.281366.1539943536000.63617.1589563620041%40Atlassian.JIRA.
Jira (FACT-2584) Puppet Gem 6 on Ubuntu 20.04 missing $::is_virtual fact
Title: Message Title Josh Cooper updated an issue Facter / FACT-2584 Puppet Gem 6 on Ubuntu 20.04 missing $::is_virtual fact Change By: Josh Cooper Summary: Puppet Gem 6 on Ubuntu 20.04 missing $::is_virtual fact Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.356817.1587845996000.63541.1589561340100%40Atlassian.JIRA.
Jira (PUP-10247) Support ruby 2.7
Title: Message Title Josh Cooper commented on PUP-10247 Re: Support ruby 2.7 Anthony Sottile I left a comment on the FACT ticket. Note that issue occurs when running puppet as a gem. If you using puppet-agent packages, then it shouldn't be an issue. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.342962.1579675679000.63532.1589560980119%40Atlassian.JIRA.
Jira (FACT-2584) Puppet 6 on Ubuntu 20.04 missing $::is_virtual fact
Title: Message Title Josh Cooper commented on FACT-2584 Re: Puppet 6 on Ubuntu 20.04 missing $::is_virtual fact Ah Anthony Sottile, this issue occurs because you're using puppet as a gem, and it relaxed the facter dependency to allow facter-ng 4. If you override the gem constraint then you'll get facter 2.5.7 again. $ env FACTER_LOCATION='< 4' bundle update ... $ bundle exec gem which facter /Users/josh/work/puppet/.bundle/gems/ruby/2.7.0/gems/facter-2.5.7/lib/facter.rb We'll keep this ticket open to track the virtual facts in facter-ng Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-4045) Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket
Title: Message Title Josh Cooper assigned an issue to Unassigned Puppet / PUP-4045 Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket Change By: Josh Cooper Assignee: Peter Souter Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.69478.1424944721000.63516.1589559900027%40Atlassian.JIRA.
Jira (PUP-10247) Support ruby 2.7
Title: Message Title Anthony Sottile commented on PUP-10247 Re: Support ruby 2.7 it's a bit unfortunate to skip puppet 5 on 20.04 as it's not yet feature complete (for example many facts are missing: https://tickets.puppetlabs.com/browse/FACT-2584) Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.342962.1579675679000.63513.1589559600022%40Atlassian.JIRA.
Jira (PUP-10289) Route HttpPool.connection through http client
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10289 Route HttpPool.connection through http client Change By: Josh Cooper Release Notes: Deprecation Release Notes Summary: Calls to Puppet::Network::HttpPool (http_instance, http_ssl_instance, connection) are routed to the new HTTP client, but preserve the existing behavior for that API. The HttpPool class will be deprecated in a future 6.y release and removed in Puppet 7. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.345755.1581357737000.63509.1589559420025%40Atlassian.JIRA.
Jira (PUP-10407) "Unable to set ownership" error with logdest on agents running as root
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10407 "Unable to set ownership" error with logdest on agents running as root Change By: Josh Cooper Release Notes: Bug Fix Release Notes Summary: Puppet no longer generates an error when using a log file destination. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.353908.1585812512000.63505.1589559300339%40Atlassian.JIRA.
Jira (PUP-10407) "Unable to set ownership" error with logdest on agents running as root
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10407 "Unable to set ownership" error with logdest on agents running as root Change By: Josh Cooper Fix Version/s: PUP 6.16.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.353908.1585812512000.63506.1589559300383%40Atlassian.JIRA.
Jira (PUP-10391) URI.escape is obsolete in Ruby 2.7
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10391 URI.escape is obsolete in Ruby 2.7 Change By: Josh Cooper Epic Link: PUP-10247 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.351394.1585310712000.63494.1589559120059%40Atlassian.JIRA.
Jira (PUP-10391) URI.escape is obsolete in Ruby 2.7
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10391 URI.escape is obsolete in Ruby 2.7 Change By: Josh Cooper Fix Version/s: PUP 6.16.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.351394.1585310712000.63493.1589559120042%40Atlassian.JIRA.
Jira (PUP-10491) Allow adding descriptive or administrative information to resources
Title: Message Title Reid Vandewiele commented on PUP-10491 Re: Allow adding descriptive or administrative information to resources I've managed to come up with one possible reason to prefer "annotation" over "metadata". Recording it here for consideration. In the specific context of Puppet, we've already used "meta-" to describe the general space that a parameter like this exists in. It is literally a meta parameter. In a sense, all of the metaparameters (tag, notify, loglevel) are metadata; just different kinds of metadata. Perhaps the name "annotation" should be preferred as it is a clarification of what metadata is being assigned, and that it is metadata is already communicated by way of the set of parameters, metaparameters, to which it belongs. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.357687.1588699805000.63415.1589555760039%40Atlassian.JIRA.
Jira (FACT-2603) GCE resolver
Title: Message Title Oana Tanasoiu assigned an issue to Oana Tanasoiu Facter / FACT-2603 GCE resolver Change By: Oana Tanasoiu Assignee: Oana Tanasoiu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.357833.1588775106000.63382.1589551800051%40Atlassian.JIRA.
Jira (FACT-2617) Fix for tests/external_facts.external_fact_stderr_messages_output_to_stderr.rb
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2617 Fix for tests/external_facts.external_fact_stderr_messages_output_to_stderr.rb Change By: Bogdan Irimie Issue Type: Task Bug Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.358946.1589550376000.63368.1589550420119%40Atlassian.JIRA.
Jira (FACT-2617) Fix for tests/external_facts.external_fact_stderr_messages_output_to_stderr.rb
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2617 Fix for tests/external_facts.external_fact_stderr_messages_output_to_stderr.rb Issue Type: Task Assignee: Unassigned Created: 2020/05/15 6:46 AM Priority: Normal Reporter: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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
Jira (FACT-2529) Fix for tests/facts/non_root_users_without_errors.rb
Title: Message Title Bogdan Irimie commented on FACT-2529 Re: Fix for tests/facts/non_root_users_without_errors.rb The test is passing, it might have been resolved by another PR. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.353951.1585825926000.63343.1589548560100%40Atlassian.JIRA.
Jira (FACT-2529) Fix for tests/facts/non_root_users_without_errors.rb
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2529 Fix for tests/facts/non_root_users_without_errors.rb Change By: Bogdan Irimie Assignee: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.353951.1585825926000.63341.1589548080076%40Atlassian.JIRA.
Jira (FACT-2595) Update tests to use host method for env command
Title: Message Title Andrei Filipovici assigned an issue to Unassigned Facter / FACT-2595 Update tests to use host method for env command Change By: Andrei Filipovici Assignee: Andrei Filipovici Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.357169.158816676.63330.1589546340026%40Atlassian.JIRA.
Jira (FACT-2595) Update tests to use host method for env command
Title: Message Title Andrei Filipovici assigned an issue to Andrei Filipovici Facter / FACT-2595 Update tests to use host method for env command Change By: Andrei Filipovici Assignee: Andrei Filipovici Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.357169.158816676.63329.1589545860034%40Atlassian.JIRA.
Jira (PUP-6909) useradd provider fails if the current value of user's expiry is nil
Title: Message Title Dorin Pleava commented on PUP-6909 Re: useradd provider fails if the current value of user's expiry is nil Was unable to reproduce the issue, even with the user::managed module, but added an extra check in this PR: https://github.com/puppetlabs/puppet/pull/8159 in case the function that retrieves the current expiry settings is not a numeric type. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.160414.1478752472000.63326.1589544720026%40Atlassian.JIRA.
Jira (FACT-2616) tests/external_facts.handle_same_filename_in_different_dirs.rb failing
Title: Message Title Florin Dragos created an issue Facter / FACT-2616 tests/external_facts.handle_same_filename_in_different_dirs.rb failing Issue Type: Bug Assignee: Florin Dragos Components: Facter 4 Created: 2020/05/15 4:15 AM Priority: Normal Reporter: Florin Dragos Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Googl
Jira (FACT-2523) Fix for tests/external_facts/non_root_users_default_external_fact_directory.rb
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2523 Fix for tests/external_facts/non_root_users_default_external_fact_directory.rb Change By: Bogdan Irimie Assignee: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.353944.1585825612000.63308.1589539980114%40Atlassian.JIRA.
Jira (FACT-2520) Fix for tests/external_facts/external_dir_overrides_default_external_fact.rb
Title: Message Title Bogdan Irimie commented on FACT-2520 Re: Fix for tests/external_facts/external_dir_overrides_default_external_fact.rb The test is passing on all platforms, maybe it was fixed by an earlier PR. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.353941.1585825438000.63307.1589539860028%40Atlassian.JIRA.
Jira (FACT-2520) Fix for tests/external_facts/external_dir_overrides_default_external_fact.rb
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2520 Fix for tests/external_facts/external_dir_overrides_default_external_fact.rb Change By: Bogdan Irimie Assignee: Bogdan Irimie Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.353941.1585825438000.63291.1589534160035%40Atlassian.JIRA.
Jira (BOLT-1548) Wrong value for fact os.release.major
Title: Message Title
Daniel updated an issue
Puppet Task Runner / BOLT-1548
Wrong value for fact os.release.major
Change By:
Daniel
I am seeing a weird behavior when I run a simple bolt plan on my RHEL 7 box. The fact os.release.major seems to get the wrong value. It gets 7.8, instead of 7.If I execute:{code:java} $ bolt plan run test:server nodes=localhost --debug{code} {noformat} ...Running '/opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-2.8.0/libexec/custom_facts.rb' with {"plugins":"Sensitive [value redacted]","_task":"apply_helpers::custom_facts"} using '/opt/puppetlabs/bolt/bin/ruby' interpreterExecuting: mkdir -m 700 /tmp/fc15ffb9-7182-45a8-ae93-05376d86adccCommand returned successfullyUploading /opt/puppetlabs/bolt/lib/ruby/gems/2.5.0/gems/bolt-2.8.0/libexec/custom_facts.rb, to /tmp/fc15ffb9-7182-45a8-ae93-05376d86adcc/custom_facts.rbExecuting: chmod u\+x /tmp/fc15ffb9-7182-45a8-ae93-05376d86adcc/custom_facts.rbCompleted analytics submissionCommand returned successfullyExecuting: /opt/puppetlabs/bolt/bin/ruby /tmp/fc15ffb9-7182-45a8-ae93-05376d86adcc/custom_facts.rb...{noformat} After that command is executed I can see the list of facts that bolt will use. Searching for "os.release.major" I saw that it has indeed a wrong value. { color:#e6db74 noformat } { "os" {color}{color : #f8f8f2}: { {color} {color:#66d9ef} "family" {color}{color : #f8f8f2}: {color}{color:#cfcfc2} "RedHat" {color}{color:#f8f8f2} , {color} {color:#66d9ef} "hardware" {color}{color : #f8f8f2}: {color}{color:#cfcfc2} "x86_64" {color}{color:#f8f8f2} , {color} {color:#66d9ef} "selinux" {color}{color : #f8f8f2}: { {color} {color:#66d9ef} "current_mode" {color}{color : #f8f8f2}: {color}{color:#cfcfc2} "enforcing" {color}{color:#f8f8f2} , {color} {color:#66d9ef} "enabled" {color}{color : #f8f8f2}: {color}{color:#ae81ff} true {color}{color:#f8f8f2} , {color} {color:#66d9ef} "enforced" {color}{color : #f8f8f2}: {color}{color:#ae81ff} true {color}{color:#f8f8f2} , {color} {color:#66d9ef} "policy_version" {color}{color : #f8f8f2}: {color}{color:#cfcfc2} "31" {color}{color:#f8f8f2} , {color} {color:#66d9ef} "config_mode" {color}{color : #f8f8f2}: {color}{color:#cfcfc2} "enforcing" {color}{color:#f8f8f2} , {color} {color:#66d9ef} "config_policy" {color}{color : #f8f8f2}: {color}{color:#cfcfc2} "targeted" {color} {color:#f8f8f2 } } , {color} {color:#66d9ef} "name" {color}{color : #f8f8f2}: {color}{color:#cfcfc2} "RedHat" {color}{color:#f8f8f2} , {color} {color:#66d9ef} "architecture" {color}{color : #f8f8f2}: {color}{color:#cfcfc2} "x86_64" {color}{color:#f8f8f2} , {color} {color:#66d9ef} "distro" {color}{color : #f8f8f2}: { {color} {color:#66d9ef} "id" {color}{color : #f8f8f2}: {color}{color:#cfcfc2} "RedHatEnterpriseServer" {color}{color:#f8f8f2} , {color} {color:#66d9ef} "codename" {color}{color : #f8f8f2}: {color}{color:#cfcfc2} "Maipo" {color}{color:#f8f8f2} , {color} {color:#66d9ef} "description" {color}{color : #f8f8f2}: {color}{color:#cfcfc2} "Red Hat Enterprise Linux Server release 7.8 (Maip
Jira (BOLT-1548) Wrong value for fact os.release.major
Title: Message Title
Daniel commented on BOLT-1548
Re: Wrong value for fact os.release.major
I workarounded this issue creating a custom fact on /opt/puppetlabs/facter/facts.d/overwrite_os.json
{
"os": {
"architecture": "x86_64",
"distro": {
"codename": "Maipo",
"description": "Red Hat Enterprise Linux Server release 7.8 (Maipo)",
"id": "RedHatEnterpriseServer",
"release": {
"full": "7.8",
"major": "7",
"minor": "8"
},
"specification": ":core-4.1-amd64:core-4.1-noarch"
},
