Jira (FACT-2937) 'puppet facts show' logs error when stdlib is installed
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-2937
'puppet facts show' logs error when stdlib is installed
Change By:
Gheorghe Popescu
When running `puppet facts show` and puppetlabs-stdlib is installed, the following error message is shown:{noformat}Error: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClassError: Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClassError: Facter: error while resolving custom facts in /etc/puppetlabs/code/modules/stdlib/lib/facter/service_provider.rb Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass{noformat}- puppet facts show calls `Facter.resolve` which sets show_legacy to false- when resolving facts, Facter also load modules facts(stdlib)- stdlib has a fact that creates a dummy provider: https://github.com/puppetlabs/puppetlabs-stdlib/blob/main/lib/facter/service_provider.rb- when Facter loads that fact, it calls Puppet to initalize the provider, Puppet tries to see what specific provider is suitable, and when it gets to `init.rb` it calls Facter back, with `operatingsystem`- because `Facter::Options[:show_legacy]` is false, Facter.value(:operatingsystem) returns `nil`, which breaks the call of `downcase`: https://github.com/puppetlabs/puppet/blob/main/lib/puppet/provider/service/init.rb#L24This happens because `Facter::Options` is globally set for the entire run.Note that the command is working, and running ` " puppet facts show #{fact} ` " does not log any error
Add Comment
Jira (FACT-2937) 'puppet facts show' logs error when stdlib is installed
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-2937
'puppet facts show' logs error when stdlib is installed
Change By:
Gheorghe Popescu
When running `puppet facts show` and puppetlabs-stdlib is installed, the following error message is shown:{noformat}Error: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClassError: Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClassError: Facter: error while resolving custom facts in /etc/puppetlabs/code/modules/stdlib/lib/facter/service_provider.rb Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass{noformat}- puppet facts show calls `Facter.resolve` which sets show_legacy to false- when resolving facts, Facter also load modules facts(stdlib)- stdlib has a fact that creates a dummy provider: https://github.com/puppetlabs/puppetlabs-stdlib/blob/main/lib/facter/service_provider.rb- when Facter loads that fact, it calls Puppet to initalize the provider, Puppet tries to see what specific provider is suitable, and when it gets to `init.rb` it calls Facter back, with `operatingsystem`- because `Facter::Options[:show_legacy]` is false, Facter.value(:operatingsystem) returns `nil`, which breaks the call of `downcase`: https://github.com/puppetlabs/puppet/blob/main/lib/puppet/provider/service/init.rb#L24This happens because `Facter::Options` is globally set for the entire run.Note that the command is working, and running "puppet facts show # {fact}" does not log any error
Add Comment
Jira (FACT-2937) 'puppet facts show' logs error when stdlib is installed
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-2937
'puppet facts show' logs error when stdlib is installed
Change By:
Gheorghe Popescu
When running `puppet facts show` and puppetlabs-stdlib is installed, the following error message is shown:{noformat}Error: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClassError: Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClassError: Facter: error while resolving custom facts in /etc/puppetlabs/code/modules/stdlib/lib/facter/service_provider.rb Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass{noformat}- puppet facts show calls `Facter.resolve` which sets show_legacy to false- when resolving facts, Facter also load modules facts(stdlib)- stdlib has a fact that creates a dummy provider: https://github.com/puppetlabs/puppetlabs-stdlib/blob/main/lib/facter/service_provider.rb- when Facter loads that fact, it calls Puppet to initalize the provider, Puppet tries to see what specific provider is suitable, and when it gets to `init.rb` it calls Facter back, with `operatingsystem`- because `Facter::Options[:show_legacy]` is false, Facter.value(:operatingsystem) returns `nil`, which breaks the call of `downcase`: https://github.com/puppetlabs/puppet/blob/main/lib/puppet/provider/service/init.rb#L24This happens because `Facter::Options` is globally set for the entire run.Note that the command is working, and running "puppet facts show { fact } " does not log any error
Add Comment
Jira (FACT-2937) 'puppet facts show' logs error when stdlib is installed
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-2937
'puppet facts show' logs error when stdlib is installed
Change By:
Gheorghe Popescu
When running `puppet facts show` and puppetlabs-stdlib is installed, the following error message is shown:{noformat}Error: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClassError: Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClassError: Facter: error while resolving custom facts in /etc/puppetlabs/code/modules/stdlib/lib/facter/service_provider.rb Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass{noformat}- puppet facts show calls `Facter.resolve` which sets show_legacy to false- when resolving facts, Facter also load modules facts(stdlib)- stdlib has a fact that creates a dummy provider: https://github.com/puppetlabs/puppetlabs-stdlib/blob/main/lib/facter/service_provider.rb- when Facter loads that fact, it calls Puppet to initalize the provider, Puppet tries to see what specific provider is suitable, and when it gets to `init.rb` it calls Facter back, with `operatingsystem`- because `Facter::Options[:show_legacy]` is false, Facter.value(:operatingsystem) returns `nil`, which breaks the call of `downcase`: https://github.com/puppetlabs/puppet/blob/main/lib/puppet/provider/service/init.rb#L24This happens because `Facter::Options` is globally set for the entire run. Note that the command is working, and running `puppet facts show #{fact}` does not log any error
Add Comment
Jira (FACT-2937) 'puppet facts show' logs error when stdlib is installed
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2937 'puppet facts show' logs error when stdlib is installed Change By: Gheorghe Popescu Summary: Puppet 'puppet facts show ' logs error when stdlib is installed 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.386159.1612446678000.134084.1612505160134%40Atlassian.JIRA.
Jira (FACT-2938) Ship facter 4 nightly gems
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2938 Ship facter 4 nightly gems Change By: Gheorghe Popescu https://tickets.puppetlabs.com/browse/PA-2987 covered shipping of puppet as a nightly gem. The functionality should be extended to also handle Facter 4What we need to do: - adapt Facter 4 project to use the `nightly_gem` task for packaging(usually this means changes to ext/build_defaults), this will need also an ext/project_data file, similar to puppet: https://github.com/puppetlabs/puppet/blob/main/ext/project_data.yaml - create a jenkins job similar to the one that runs in puppet-agent#main acceptance suite. This job can run on daily cadence (or triggered in puppet-agent#main) and ship Facter 4 nightly gems that can be promoted used into puppet-agent #6.x https://github.com/puppetlabs/ci-job-configs/pull/6474/files 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
Jira (PUP-10887) Retry bulk pluginsync curl operations if they fail with CURLE_PARTIAL_FILE
Title: Message Title Garrett Guillotte updated an issue Puppet / PUP-10887 Retry bulk pluginsync curl operations if they fail with CURLE_PARTIAL_FILE Thanks, Josh Cooper! I've reset the Team field to Installer and Management. Change By: Garrett Guillotte Team: Night's Watch Installer and Management 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.386238.1612477989000.134060.1612491360068%40Atlassian.JIRA.
Jira (FACT-2939) Restore facter --puppet functionality to Facter 4
Title: Message Title
Josh Cooper updated an issue
Facter / FACT-2939
Restore facter --puppet functionality to Facter 4
Change By:
Josh Cooper
Historically, the {{ \ - \ -puppet}} and {{-p}} flags were offered by the Facter CLI to enable loading and reporting custom facts that had been downloaded from a Puppet Server by the Puppet Agent. But, the output of {{facter \ --puppet}} does not include values added by the {{puppet agent}} to facts submitted with catalog requests and can produce incorrect output when fact resolution is sensitive to the Puppet Environment as a compiler scope is not initialized. These issues led to the {{ \ --puppet}} flag being deprecated in favor of the {{puppet facts show}} CLI in Puppet 7 and Facter 4.However, the {{ \ --puppet}} flag has a very long history in Facter, having been added in 2008. This history has created a large diaspora of {{facter \ --puppet}} usage in scripts that are not sensitive to the issues fixed by {{puppet facts show}} because they are invoked on agent systems that don't host multiple environments or request fact values that are created by the context of a {{puppet agent}} run.In order to smooth upgrades to Puppet 7 by avoiding a search-and-replace operation to locate existing uses of {{facter \ --puppet}}, this ticket is a request to restore the functionality of the flag in Facter 4.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2939) Restore facter --puppet functionality to Facter 4
Title: Message Title
Charlie Sharpsteen updated an issue
Facter / FACT-2939
Restore facter --puppet functionality to Facter 4
Change By:
Charlie Sharpsteen
Historically, the {{--puppet}} and {{-p}} flags were offered by the Facter CLI to enable loading and reporting custom facts that had been downloaded from a Puppet Server by the Puppet Agent. But, the output of {{facter --puppet}} does not include values added by the {{puppet agent}} to facts submitted with catalog requests and can produce incorrect output when fact resolution is sensitive to the Puppet Environment as a compiler scope is not initialized. These issues led to the {{--puppet}} flag being deprecated in favor of the {{puppet facts show}} CLI in Puppet 7 and Facter 4.However, the {{--puppet}} flag has a very long history in Facter, having been added in 2008. This history has created a large diaspora of {{facter --puppet}} usage in scripts that are not sensitive to the issues fixed by {{puppet facts show}} because they are invoked on agent systems that don't host multiple environments or request fact values that are created by the context of a {{puppet agent}} run.In order to smooth upgrades to Puppet 7 by avoiding a search-and-replace operation to locate existing uses of {{facter --puppet}}, this ticket is a request to restore the functionality of the flag in Facter 4.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2939) Restore facter --puppet functionality to Facter 4
Title: Message Title Charlie Sharpsteen created an issue Facter / FACT-2939 Restore facter --puppet functionality to Facter 4 Issue Type: Improvement Affects Versions: FACT 4.0.50 Assignee: Unassigned Created: 2021/02/04 3:21 PM Priority: Major Reporter: Charlie Sharpsteen Historically, the -puppet and -p flags were offered by the Facter CLI to enable loading and reporting custom facts that had been downloaded from a Puppet Server by the Puppet Agent. But, the output of facter --puppet does not include values added by the puppet agent to facts submitted with catalog requests and can produce incorrect output when fact resolution is sensitive to the Puppet Environment as a compiler scope is not initialized. These issues led to the -puppet flag being deprecated in favor of the puppet facts show CLI in Puppet 7 and Facter 4. However, the --puppet flag has a very long history in Facter, having been added in 2008. This history has created a large diaspora of facter --puppet usage in scripts that are not sensitive to the issues fixed by puppet facts show because they are invoked on agent systems that don't host multiple environments or request fact values that are by the context of a puppet agent run. In order to smooth upgrades to Puppet 7 by avoiding a search-and-replace operation to locate existing uses of facter --puppet, this ticket is a request to restore the functionality of the flag in Facter 4.
Jira (PUP-10887) Retry bulk pluginsync curl operations if they fail with CURLE_PARTIAL_FILE
Title: Message Title
Garrett Guillotte updated an issue
Puppet / PUP-10887
Retry bulk pluginsync curl operations if they fail with CURLE_PARTIAL_FILE
Change By:
Garrett Guillotte
*Problem statement*Bulk pluginsync operations can unexpectedly fail due to transient issues outside of Puppet's control, such as network failures. This can result in messages such as:{code:java}2021-02-04T10:51:02.967+13:00 E: 'curl --tlsv1 -k -o /tmp/tmp.LLHDefu2lQ -L --write-out %{http_code} -s https://pe.example.com:8140/packages/bulk_pluginsync.tar.gz ' failed (exit_code: 18) {code}Where curl exit code 18 is:{quote}CURLE_PARTIAL_FILE (18)A file transfer was shorter or larger than expected. This happens when the server first reports an expected transfer size, and then delivers data that doesn't match the previously given size.{quote}*Steps to reproduce*During bulk pluginsync's curl transfer, externally halt/disconnect/sever network traffic to the recipient.ORDuring bulk pluginsync's curl transfer, fill local storage to capacity on the recipient.*Expected behavior*The curl transfer is re-tried at least once, to automatically rule out transient disruptions.*Observed behavior*The curl transfer fails, causing installation bulk pluginsync to fail.*User impact*Many Puppet nodes are automatically provisioned and destroyed on failure. If bulk pluginsync fails during provisioning, it cannot be retried manually. This can cause automated node provisioning workflows to fail without recourse due to an unhandled transient issue external to Puppet, such as network instability. These can have no recourse, especially if the nodes are provisioned in cloud providers whose networks the user cannot manage.Retrying the failuire can also help confirm whether the issue is not related to networking, since E_PARTIAL_FILE can occur when local storage is full, and also when the response is larger than expected. In both instances, it should also consistently fail upon retry, ruling out transient network effects.
Add Comment
Jira (PUP-10887) Retry bulk pluginsync curl operations if they fail with CURLE_PARTIAL_FILE
Title: Message Title
Garrett Guillotte updated an issue
Puppet / PUP-10887
Retry bulk pluginsync curl operations if they fail with CURLE_PARTIAL_FILE
Change By:
Garrett Guillotte
*Problem statement*Bulk pluginsync operations can unexpectedly fail due to transient issues outside of Puppet's control, such as network failures. This can result in messages such as:{code:java} 2021-02-04T10:51:02.967+13:00 E: 'curl --tlsv1 -k -o /tmp/tmp.LLHDefu2lQ -L --write-out %{http_code} -s https://pe.example.com:8140/packages/bulk_pluginsync.tar.gz ' failed (exit_code: 18) {code}Where curl exit code 18 is:{quote}CURLE_PARTIAL_FILE (18)A file transfer was shorter or larger than expected. This happens when the server first reports an expected transfer size, and then delivers data that doesn't match the previously given size.{quote}*Steps to reproduce*During bulk pluginsync's curl transfer, externally halt networking during a bulk pluginsync /disconnect/sever network traffic to the recipient .ORDuring bulk pluginsync's curl transfer, fill local storage to capacity on the recipient .*Expected behavior*The curl transfer is re-tried at least once, to automatically rule out transient disruptions.*Observed behavior*The curl transfer fails, causing installation to fail.*User impact*Many Puppet nodes are automatically provisioned and destroyed on failure. If bulk pluginsync fails during provisioning, it cannot be retried manually. This can cause automated node provisioning workflows to fail without recourse due to an unhandled transient issue external to Puppet, such as network instability. These can have no recourse, especially if the nodes are provisioned in cloud providers whose networks the user cannot manage.Retrying the failuire can also help confirm whether the issue is not related to networking, since E_PARTIAL_FILE can occur when local storage is full, and also when the response is larger than expected. In both instances, it should also consistently fail upon retry, ruling out transient network effects.
Add Comment
Jira (PUP-10887) Retry bulk pluginsync curl operations if they fail with CURLE_PARTIAL_FILE
Title: Message Title zendesk.jira updated an issue Puppet / PUP-10887 Retry bulk pluginsync curl operations if they fail with CURLE_PARTIAL_FILE Change By: zendesk.jira Labels: jira_escalated 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.386238.1612477989000.133873.1612478100083%40Atlassian.JIRA.
Jira (PUP-10887) Retry bulk pluginsync curl operations if they fail with CURLE_PARTIAL_FILE
Title: Message Title zendesk.jira updated an issue Puppet / PUP-10887 Retry bulk pluginsync curl operations if they fail with CURLE_PARTIAL_FILE Change By: zendesk.jira Zendesk Ticket Count: 1 Zendesk Ticket IDs: 43034 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.386238.1612477989000.133872.1612478100040%40Atlassian.JIRA.
Jira (PUP-10887) Retry bulk pluginsync curl operations if they fail with CURLE_PARTIAL_FILE
Title: Message Title Garrett Guillotte moved an issue Puppet / PUP-10887 Retry bulk pluginsync curl operations if they fail with CURLE_PARTIAL_FILE Change By: Garrett Guillotte Key: PE PUP - 31089 10887 Project: Puppet Enterprise [Internal] 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.386238.1612477989000.133870.1612478040051%40Atlassian.JIRA.
Jira (PUP-10887) Retry bulk pluginsync curl operations if they fail with CURLE_PARTIAL_FILE
Title: Message Title Garrett Guillotte updated an issue Puppet / PUP-10887 Retry bulk pluginsync curl operations if they fail with CURLE_PARTIAL_FILE Change By: Garrett Guillotte Method Found: Customer Feedback Issue Type: Bug Improvement 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.386238.1612477989000.133871.1612478040095%40Atlassian.JIRA.
Jira (PUP-10861) puppet facts show --value-only should not display a quoted value
Title: Message Title Josh Cooper commented on PUP-10861 Re: puppet facts show --value-only should not display a quoted value Passed CI in 97ca00bcb9 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.385148.1611768949000.133632.1612466760249%40Atlassian.JIRA.
Jira (PUP-10861) puppet facts show --value-only should not display a quoted value
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10861
puppet facts show --value-only should not display a quoted value
Change By:
Josh Cooper
Release Notes:
Bug Fix
Release Notes Summary:
The command "puppet facts show --value-only " emitted the value as a JSON string, which included quotes around the value, such as {{"RedHat"}}. It now emits just the value.
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.385148.1611768949000.133626.1612466700075%40Atlassian.JIRA.
Jira (FACT-2938) Ship facter 4 nightly gems
Title: Message Title Josh Cooper updated an issue Facter / FACT-2938 Ship facter 4 nightly gems Change By: Josh Cooper Summary: Shit Ship facter 4 nightly gems 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.386160.1612447345000.133586.1612465320046%40Atlassian.JIRA.
Jira (FACT-1847) Implement "cloud" fact Azure identification for Windows platform
Title: Message Title Josh Cooper updated an issue Facter / FACT-1847 Implement "cloud" fact Azure identification for Windows platform Change By: Josh Cooper Team: Platform OS Night's Watch 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.247441.1524674206000.133572.1612464720082%40Atlassian.JIRA.
Jira (PUP-10093) Add a rewrap(Any, Callable) function to make using Sensitive easier
Title: Message Title Reid Vandewiele commented on PUP-10093 Re: Add a rewrap(Any, Callable) function to make using Sensitive easier I'm curious to see an example of what a user would have to do to get benefit from this. I.e. a user story, and a Puppet manifest or code snippet demonstrating how rewrap() helps. 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.328237.157026849.133439.1612460940135%40Atlassian.JIRA.
Jira (PUP-10863) Invalid parser function breaks catalog compilation in all environments
Title: Message Title Matt Fields commented on PUP-10863 Re: Invalid parser function breaks catalog compilation in all environments If it was an issue in the Puppet 5 server as well, I'd just write it off as a quirk of Puppet; however, this is something that affects Puppet 6 and not Puppet 5, so it seems like a bug that should be fixed to me. If it just affected the environment the bad code was executed in, then "fix your code" is acceptable, but since it affects everything on the server until it is restarted, I feel that this should be fixed in the server process. 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.385428.1611958192000.133348.1612457760027%40Atlassian.JIRA.
Jira (FACT-2938) Shit facter 4 nightly gems
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2938 Shit facter 4 nightly gems Change By: Gheorghe Popescu https://tickets.puppetlabs.com/browse/PA-2987 covered shipping of puppet as a nightly gem. The functionality should be extended to also handle Facter 4What we need to do: - adapt Facter 4 project to use the `nightly_gem` task for packaging(usually this means changes to ext/build_defaults), this will need also an ext/project_data file, similar to puppet: https://github.com/puppetlabs/puppet/blob/main/ext/project_data.yaml - create a jenkins job similar to the one that runs in puppet-agent#main acceptance suite. This job can run on daily cadence and ship Facter 4 nightly gems that can be promoted into puppet-agent https://github.com/puppetlabs/ci-job-configs/pull/6474/files - 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
Jira (FACT-2938) Shit facter 4 nightly gems
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-2938 Shit facter 4 nightly gems Change By: Gheorghe Popescu https://tickets.puppetlabs.com/browse/PA-2987 covered shipping of puppet as a nightly gem. The functionality should be extended to also handle Facter 4What we need to do: - adapt Facter 4 project to use the `nightly_gem` task for packaging(usually this means changes to ext/build_defaults), this will need also an ext/project_data file, similar to puppet: https://github.com/puppetlabs/puppet/blob/main/ext/project_data.yaml - create a jenkins job similar to the one that is part of runs in puppet-agent#main acceptance and ships a Facter 4 nightly gem(TBD: where?): suite. https://github.com/puppetlabs/ci-job-configs/pull/6474/files - 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
Jira (FACT-2938) Shit facter 4 nightly gems
Title: Message Title Gheorghe Popescu created an issue Facter / FACT-2938 Shit facter 4 nightly gems Issue Type: Task Assignee: Unassigned Created: 2021/02/04 6:02 AM Priority: Normal Reporter: Gheorghe Popescu https://tickets.puppetlabs.com/browse/PA-2987 covered shipping of puppet as a nightly gem. The functionality should be extended to also handle Facter 4 What we need to do: adapt Facter 4 project to use the `nightly_gem` task for packaging(usually this means changes to ext/build_defaults), this will need also an ext/project_data file, similar to puppet: https://github.com/puppetlabs/puppet/blob/main/ext/project_data.yaml create a jenkins job that is part of puppet-agent#main acceptance and ships a Facter 4 nightly gem(TBD: where?): https://github.com/puppetlabs/ci-job-configs/pull/6474/files - Add Comment
Jira (FACT-2937) Puppet facts show logs error when stdlib is installed
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-2937
Puppet facts show logs error when stdlib is installed
Change By:
Gheorghe Popescu
When running `puppet facts show` and puppetlabs-stdlib is installed, the following error message is shown:{noformat}Error: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClassError: Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClassError: Facter: error while resolving custom facts in /etc/puppetlabs/code/modules/stdlib/lib/facter/service_provider.rb Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass{noformat}- puppet facts show calls `Facter.resolve` which sets show_legacy to fals false - when resolving facts, Facter also load modules facts(stdlib)- stdlib has a fact that creates a dummy provider: https://github.com/puppetlabs/puppetlabs-stdlib/blob/main/lib/facter/service_provider.rb- when Facter loads that fact, it calls Puppet to initalize the provider, Puppet tries to see what specific provider is suitable, and when it gets to `init.rb` it calls Facter back, with `operatingsystem`- because `Facter::Options[:show_legacy]` is false, Facter.value(:operatingsystem) returns `nil`, which breaks the call of `downcase`: https://github.com/puppetlabs/puppet/blob/main/lib/puppet/provider/service/init.rb#L24This happens because `Facter::Options` is globally set for the entire run.
Add Comment
Jira (FACT-2937) Puppet facts show logs error when stdlib is installed
Title: Message Title Gheorghe Popescu created an issue Facter / FACT-2937 Puppet facts show logs error when stdlib is installed Issue Type: Bug Assignee: Unassigned Created: 2021/02/04 5:51 AM Priority: Normal Reporter: Gheorghe Popescu When running `puppet facts show` and puppetlabs-stdlib is installed, the following error message is shown: Error: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass Error: Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass Error: Facter: error while resolving custom facts in /etc/puppetlabs/code/modules/stdlib/lib/facter/service_provider.rb Could not autoload puppet/provider/service/bsd: Could not autoload puppet/provider/service/init: undefined method `downcase' for nil:NilClass puppet facts show calls `Facter.resolve` which sets show_legacy to fals when resolving facts, Facter also load modules facts(stdlib)
Jira (PDB-4934) PuppetDB does not support username@hostname auth for Azure PostgreSQL
Title: Message Title Bogdan Irimie commented on PDB-4934 Re: PuppetDB does not support username@hostname auth for Azure PostgreSQL Rob Browning and Zachary Kent suggested adding two new users: `connection-username ` and `connection-migrator-username`. The users will be used to establish new connections to the database (in the case of Azure, the pattern is `user@domain`). By implementing this we will make a clear distinction between the user that is used to connect to the database (in our case `connection-username` and `connection-migrator-username`) and the user that is used in queries (in our case `username` and `migrator-username`). If the `connection-migrator-username` is not specified in the database config, it will default to `migrator-username`, which in turn default to `username`. https://github.com/puppetlabs/puppetdb/blob/6.x/src/puppetlabs/puppetdb/config.clj#L393-L399 If the `connection-username` is not specified in the database config, it will default to `username`. Example of test: https://github.com/puppetlabs/puppetdb/commit/b489b38ff1484774ea08185db084f9670ee9fac4 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.375238.1603127441000.133066.1612437420098%40Atlassian.JIRA.
Jira (PUP-10884) 'puppet facts show' gives conversion error on 6.x agent
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-10884 'puppet facts show' gives conversion error on 6.x agent Change By: Gheorghe Popescu Assignee: Gheorghe Popescu 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.385667.1612200398000.133060.161243729%40Atlassian.JIRA.
Jira (FACT-2936) Facter::Core::Exectuion set $? test is failing on OSX and Solaris
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Facter / FACT-2936 Facter::Core::Exectuion set $? test is failing on OSX and Solaris Change By: Dorin Pleava Assignee: Dorin Pleava 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.386034.1612379676000.133058.1612436580044%40Atlassian.JIRA.
Jira (FACT-2878) Networking fact improvements for Aix
Title: Message Title Sebastian Miclea updated an issue Facter / FACT-2878 Networking fact improvements for Aix Change By: Sebastian Miclea Release Notes: Bug Fix Release Notes Summary: Updated AIX networking resolver to use FFI to detect networking interfaces and IPs. Before this fix, VLANs and secondary IPs were not displayed. 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.379328.1606498722000.133053.1612435920028%40Atlassian.JIRA.
Jira (FACT-2934) Facter::Core::Execution does not set status variables in Facter 4
Title: Message Title Oana Tanasoiu updated an issue Facter / FACT-2934 Facter::Core::Execution does not set status variables in Facter 4 Change By: Oana Tanasoiu Release Notes: Bug Fix Release Notes Summary: Description of the problem: The exec and execute methods of the Facter::Core::Execution module are commonly used to execute external processes in custom facts. In Facter 4, these methods no longer set the global Ruby variables $CHILD_STATUS or $? because Open3 is used and it consumes the exit status of the child process.Description of the fix: Reimplement Open3.popen3 to not use Process.detach but Process.wait instead. 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
Jira (FACT-2813) Show backtrace in CI for acceptance test errors
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-2813 Show backtrace in CI for acceptance test errors Change By: Ciprian Badescu Fix Version/s: FACT 4.0.50 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.372970.1600961477000.133023.1612435260036%40Atlassian.JIRA.
Jira (FACT-2934) Facter::Core::Execution does not set status variables in Facter 4
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-2934 Facter::Core::Execution does not set status variables in Facter 4 Change By: Ciprian Badescu Fix Version/s: FACT 4.0.50 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.385912.1612301794000.133022.1612435200037%40Atlassian.JIRA.
Jira (FACT-2917) Blocking `legacy` facts slows down facter
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-2917 Blocking `legacy` facts slows down facter Change By: Ciprian Badescu Fix Version/s: FACT 4.0.50 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.383065.1610551174000.133020.1612435140051%40Atlassian.JIRA.
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-2924 Facter fails "closed" if the facter.conf file is invalid Change By: Ciprian Badescu Fix Version/s: FACT 4.0.50 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.383703.1611082995000.133021.1612435140098%40Atlassian.JIRA.
Jira (FACT-2861) Acceptance test for partial cache invalidation
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-2861 Acceptance test for partial cache invalidation Change By: Ciprian Badescu Fix Version/s: FACT 4.0.50 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.378477.160552265.133019.1612435080143%40Atlassian.JIRA.
Jira (FACT-2857) Acceptance test for cache with user query
Title: Message Title Ciprian Badescu updated an issue Facter / FACT-2857 Acceptance test for cache with user query Change By: Ciprian Badescu Fix Version/s: FACT 4.0.50 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.378287.1605280544000.133018.1612435080099%40Atlassian.JIRA.
Jira (PUP-10861) puppet facts show --value-only should not display a quoted value
Title: Message Title Ciprian Badescu commented on PUP-10861 Re: puppet facts show --value-only should not display a quoted value @josh, please add release notes when you have some spare time 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.385148.1611768949000.133014.1612434840022%40Atlassian.JIRA.
Jira (PUP-10853) When blocking legacy facts in puppet7, puppet agent run fails to fetch 'operatingsystem' fact
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-10853 When blocking legacy facts in puppet7, puppet agent run fails to fetch 'operatingsystem' fact Change By: Ciprian Badescu Fix Version/s: PUP 7.4.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.383136.1610563179000.133013.1612434780103%40Atlassian.JIRA.
Jira (PUP-10858) Add --timing to puppet facts show
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-10858 Add --timing to puppet facts show Change By: Ciprian Badescu Fix Version/s: PUP 7.4.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.383413.1610735312000.133011.1612434720233%40Atlassian.JIRA.
Jira (PUP-10863) Invalid parser function breaks catalog compilation in all environments
Title: Message Title
Henrik Lindberg commented on PUP-10863
Re: Invalid parser function breaks catalog compilation in all environments
It is probably going wrong in the logic that validates the old 3x functions when they are loaded. The borked function in question is overly verbose and uses constructs that the validation parsing was not designed to handle. If the "borked" was written on the form shown below, it should load (did not try though).
module Puppet::Parser::Functions newfunction( :bork, :type => :rvalue, :doc => 'B0rks the puppetserver' ) do |args| return true end end {ruby} I realize that the issue is really "loading completely borked function implementation should not have effect on subsequent compilations where the borked function is unused" - and not "I cannot load this function". As a side note - In general the recommendation is to not use the legacy (3.x) style for function implementations. Also note that it is close to impossible to ward off all possible cases of "loading bad logic in Ruby" due to Ruby's super flexible nature. The 3.x function loading is susceptible to a wider range of mistakes than the 4.x API and that is why the Ruby source is parsed and analyzed before being passed on to actually loading it. The 3.x API was invented long before the Ruby syntax was invented that is used in the borked function, so here is also a question about how much energy should be spent on fixing modern style mistakes made in this antique context. - - - In other words - fix the borked function.
Add Comment
This message was sent by Atlassian Jira
Jira (FACT-2936) Facter::Core::Exectuion set $? test is failing on OSX and Solaris
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2936 Facter::Core::Exectuion set $? test is failing on OSX and Solaris Change By: Mihai Buzgau Story Points: 1 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.386034.1612379676000.132938.1612431480121%40Atlassian.JIRA.
Jira (FACT-2936) Facter::Core::Exectuion set $? test is failing on OSX and Solaris
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2936 Facter::Core::Exectuion set $? test is failing on OSX and Solaris Change By: Mihai Buzgau Sprint: NW - 2021-02-17 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.386034.1612379676000.132940.1612431480207%40Atlassian.JIRA.
Jira (FACT-2936) Facter::Core::Exectuion set $? test is failing on OSX and Solaris
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2936 Facter::Core::Exectuion set $? test is failing on OSX and Solaris Change By: Mihai Buzgau Team: Night's Watch 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.386034.1612379676000.132939.1612431480163%40Atlassian.JIRA.
Jira (FACT-2933) Move Facter 3.x pipeline to GithubActions
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2933 Move Facter 3.x pipeline to GithubActions Change By: Mihai Buzgau Story Points: 5 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.385784.1612269528000.132933.161243146%40Atlassian.JIRA.
Jira (FACT-2933) Move Facter 3.x pipeline to GithubActions
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2933 Move Facter 3.x pipeline to GithubActions Change By: Mihai Buzgau Sprint: NW - 2021-02-17 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.385784.1612269528000.132934.1612431000105%40Atlassian.JIRA.
Jira (FACT-2933) Move Facter 3.x pipeline to GithubActions
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2933 Move Facter 3.x pipeline to GithubActions Change By: Mihai Buzgau Summary: Fix Appveyor Move Facter 3.x pipeline to GithubActions 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.385784.1612269528000.132932.1612430400039%40Atlassian.JIRA.
