Jira (PUP-11217) Replace `Facter.value` with the new Facter Implementation
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-11217 Replace `Facter.value` with the new Facter Implementation Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.412976.1629722586000.119444.1630326360061%40Atlassian.JIRA.
Jira (FACT-3067) Facter API does not resolve custom facts that partial match legacy facts
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3067 Facter API does not resolve custom facts that partial match legacy facts Change By: Gheorghe Popescu Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.413521.1629960225000.117112.1629960360113%40Atlassian.JIRA.
Jira (FACT-3067) Facter API does not resolve custom facts that partial match legacy facts
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-3067
Facter API does not resolve custom facts that partial match legacy facts
Change By:
Gheorghe Popescu
This works on Facter 3.Facter defines a couple of legacy facts using regexes, example networking: https://github.com/puppetlabs/facter/blob/main/lib/facter/facts/macosx/network_interfaces.rb#L6Adding the following custom_fact:{code:ruby}Facter.add('network_nexthop_ip') do setcode do'custom_value' endend{ noformat}*no* further _formatting_ is done here{noformat}{ code}Will result in the fact being resolved on CLI but not when using Facter.value / Facter.fact{noformat}❯ bx facter network_nexthop_ip --custom-dir $custom_dir --debug[2021-08-26 09:41:40.066702 ] INFO Facter - executed with command line: network_nexthop_ip --custom-dir /Users/gheorghe.popescu/Workspace/custom_facts --debug[2021-08-26 09:41:40.066788 ] DEBUG Facter - Facter version: 4.2.4[2021-08-26 09:41:40.068471 ] DEBUG Facter::FactManager - Resolving facts sequentially[2021-08-26 09:41:40.069033 ] DEBUG Facter::FactLoader - Loading all internal facts[2021-08-26 09:41:40.069164 ] DEBUG Facter::FactLoader - Loading custom facts[2021-08-26 09:41:40.077111 ] DEBUG Facter::FactLoader - Loading external facts[2021-08-26 09:41:40.079167 ] DEBUG Facter::QueryParser - List of resolvable facts: [#, #][2021-08-26 09:41:40.079312 ] DEBUG Facter::Core::Execution::Posix - Executing command: ifconfig -a[2021-08-26 09:41:40.092197 ] DEBUG Facter::Core::Execution::Posix - Executing command: ipconfig getoption en0 server_identifier[2021-08-26 09:41:40.100080 ] DEBUG Facter::Core::Execution::Posix - Executing command: ipconfig getoption awdl0 server_identifier[2021-08-26 09:41:40.107701 ] DEBUG Facter::Core::Execution::Posix - Executing command: ipconfig getoption llw0 server_identifier[2021-08-26 09:41:40.118377 ] DEBUG Facter::Core::Execution::Posix - Executing command: route -n get default[2021-08-26 09:41:40.128626 ] DEBUG Facter::Util::Fact - custom fact network_nexthop_ip got resolved from: ["/Users/gheorghe.popescu/Workspace/custom_facts/ipaddress.rb", 25][2021-08-26 09:41:40.129107 ] DEBUG Facter::FactLoader - Loading all internal facts[2021-08-26 09:41:40.130886 ] DEBUG Facter::QueryParser - List of resolvable facts: [#][2021-08-26 09:41:40.131228 ] DEBUG Facter::FactManager - fact "network_lo0" has resolved to: 127.0.0.0[2021-08-26 09:41:40.131252 ] DEBUG Facter::FactManager - fact "network_en0" has resolved to: 192.168.100.0[2021-08-26 09:41:40.131264 ] DEBUG Facter::FactManager - fact "network_nexthop_ip" has resolved to: custom_value[2021-08-26 09:41:40.131390 ] DEBUG Facter::LegacyFactFormatter - Formatting for single user querycustom_value{noformat}{noformat}Facter.valuefroce_dot: false4.2.4D, [2021-08-26T09:43:09.389815 #44494] DEBUG -- : Facter::FactManager - Resolving facts sequentiallyD, [2021-08-26T09:43:09.389872 #44494] DEBUG -- : Facter::FactManager - resolving fact with user_query: network_nexthop_ipD, [2021-08-26T09:43:09.390443 #44494] DEBUG -
Jira (FACT-3067) Facter API does not resolve custom facts that partial match legacy facts
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-3067
Facter API does not resolve custom facts that partial match legacy facts
Change By:
Gheorghe Popescu
This works on Facter 3.Facter defines a couple of legacy facts using regexes, example networking: https://github.com/puppetlabs/facter/blob/main/lib/facter/facts/macosx/network_interfaces.rb#L6Adding the following custom_fact:{code:ruby}Facter.add('network_nexthop_ip') do setcode do'custom_value' endend{noformat}*no* further _formatting_ is done here{noformat}{code}Will result in the fact being resolved on CLI but not when using Facter.value / Facter.fact{noformat}❯ bx facter network_nexthop_ip --custom-dir $custom_dir --debug[2021-08-26 09:41:40.066702 ] INFO Facter - executed with command line: network_nexthop_ip --custom-dir /Users/gheorghe.popescu/Workspace/custom_facts --debug[2021-08-26 09:41:40.066788 ] DEBUG Facter - Facter version: 4.2.4[2021-08-26 09:41:40.068471 ] DEBUG Facter::FactManager - Resolving facts sequentially[2021-08-26 09:41:40.069033 ] DEBUG Facter::FactLoader - Loading all internal facts[2021-08-26 09:41:40.069164 ] DEBUG Facter::FactLoader - Loading custom facts[2021-08-26 09:41:40.077111 ] DEBUG Facter::FactLoader - Loading external facts[2021-08-26 09:41:40.079167 ] DEBUG Facter::QueryParser - List of resolvable facts: [#, #][2021-08-26 09:41:40.079312 ] DEBUG Facter::Core::Execution::Posix - Executing command: ifconfig -a[2021-08-26 09:41:40.092197 ] DEBUG Facter::Core::Execution::Posix - Executing command: ipconfig getoption en0 server_identifier[2021-08-26 09:41:40.100080 ] DEBUG Facter::Core::Execution::Posix - Executing command: ipconfig getoption awdl0 server_identifier[2021-08-26 09:41:40.107701 ] DEBUG Facter::Core::Execution::Posix - Executing command: ipconfig getoption llw0 server_identifier[2021-08-26 09:41:40.118377 ] DEBUG Facter::Core::Execution::Posix - Executing command: route -n get default[2021-08-26 09:41:40.128626 ] DEBUG Facter::Util::Fact - custom fact network_nexthop_ip got resolved from: ["/Users/gheorghe.popescu/Workspace/custom_facts/ipaddress.rb", 25][2021-08-26 09:41:40.129107 ] DEBUG Facter::FactLoader - Loading all internal facts[2021-08-26 09:41:40.130886 ] DEBUG Facter::QueryParser - List of resolvable facts: [#][2021-08-26 09:41:40.131228 ] DEBUG Facter::FactManager - fact "network_lo0" has resolved to: 127.0.0.0[2021-08-26 09:41:40.131252 ] DEBUG Facter::FactManager - fact "network_en0" has resolved to: 192.168.100.0[2021-08-26 09:41:40.131264 ] DEBUG Facter::FactManager - fact "network_nexthop_ip" has resolved to: custom_value[2021-08-26 09:41:40.131390 ] DEBUG Facter::LegacyFactFormatter - Formatting for single user querycustom_value{noformat}{noformat}Facter.valuefroce_dot: false4.2.4D, [2021-08-26T09:43:09.389815 #44494] DEBUG -- : Facter::FactManager - Resolving facts sequentiallyD, [2021-08-26T09:43:09.389872 #44494] DEBUG -- : Facter::FactManager - resolving fact with user_query: network_nexthop_ipD, [2021-08-26T09:43:09.390443 #44494] DEBUG -
Jira (FACT-3067) Facter API does not resolve custom facts that partial match legacy facts
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3067 Facter API does not resolve custom facts that partial match legacy facts Change By: Gheorghe Popescu Component/s: Facter 4 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.413521.1629960225000.117109.1629960300050%40Atlassian.JIRA.
Jira (FACT-3067) Facter API does not resolve custom facts that partial match legacy facts
Title: Message Title
Gheorghe Popescu created an issue
Facter / FACT-3067
Facter API does not resolve custom facts that partial match legacy facts
Issue Type:
Bug
Assignee:
Unassigned
Created:
2021/08/25 11:43 PM
Priority:
Normal
Reporter:
Gheorghe Popescu
Facter defines a couple of legacy facts using regexes, example networking: https://github.com/puppetlabs/facter/blob/main/lib/facter/facts/macosx/network_interfaces.rb#L6 Adding the following custom_fact:
Facter.add('network_nexthop_ip') do
setcode do
'custom_value'
end
end
{noformat}
*no* further _formatting_ is done here
Jira (PUP-11216) Add support for multiple Facter implementations
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-11216 Add support for multiple Facter implementations Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.412975.162972246.116272.1629890940030%40Atlassian.JIRA.
Jira (PUP-11216) Add support for multiple Facter implementations
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-11216 Add support for multiple Facter implementations Change By: Gheorghe Popescu Acceptance Criteria: Puppet allows callers to register Facter implementations, and it has a default implementation that calls Facter API and is registered in the runtimes mechanism Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.412975.162972246.113607.1629722760031%40Atlassian.JIRA.
Jira (PUP-11217) Replace `Facter.value` with the new Facter Implementation
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-11217 Replace `Facter.value` with the new Facter Implementation Change By: Gheorghe Popescu Acceptance Criteria: Puppet does not call Facter API directly but though the runtimes mechanism Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.412976.1629722586000.113606.1629722700738%40Atlassian.JIRA.
Jira (PUP-11217) Replace `Facter.value` with the new Facter Implementation
Title: Message Title Gheorghe Popescu created an issue Puppet / PUP-11217 Replace `Facter.value` with the new Facter Implementation Issue Type: Improvement Assignee: Unassigned Created: 2021/08/23 5:43 AM Priority: Normal Reporter: Gheorghe Popescu We should replace all direct and indirect calls to `Facter.value` with the new mechanism that makes use of runtimes Puppet.runtime[:facter].get(:fact_name) Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11216) Add support for multiple Facter implementations
Title: Message Title Gheorghe Popescu created an issue Puppet / PUP-11216 Add support for multiple Facter implementations Issue Type: Improvement Assignee: Unassigned Created: 2021/08/23 5:41 AM Priority: Normal Reporter: Gheorghe Popescu Allow projects to register a facter implementations, similar to how callers (like puppetserver) register an HTTP client implementation. This will isolate the compiler from the system and will allow easier testing. We need to implement the same mechanism that is used for HttpClient. A default Facter implementation should be added, this will be used in Puppet and it will call the Facter API Eg. facter_impl = FacterImpl.new Puppet.initialize_settings([], true, true, http: ..., facter: facter_impl)
Jira (PUP-11205) implement snyk Code Scanning for puppet
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-11205 implement snyk Code Scanning for puppet Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.411605.1628754363000.113500.1629715260044%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu commented on FACT-3039 Re: Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 If i understand this correctly, the plan for this would be to: 1. add support for multiple Facter implementations in Puppet(Puppet.runtime[:facter]) 2. implement the default Facter implementation(which delegates to Facter API) 3. update Puppet to use Puppet.runtime[:facter].get(:fact_name) internally instead of Facter.value(:fact_name) 4. implement a TestFacterImpl in rspec-puppet-facts which interfaces with FacterDB While(3) resolves the Facter.value usage in Puppet, what are we going to do with modules that are writing their custom facts and are used in manifests? We are now having 2 ways of querying fact values which will put us in the same spot of as_ never going away legacy facts_. As Ewoud said, there is also the complication that rspec-puppet must be able to test with multiple Puppet versions and provide support for controlling the values of custom facts written in modules. Points 1, 2, 3 would be a good general improvement for Puppet interaction with Facter but the transition from Facter.value to Puppet.runtime[:facter] could prove troublesome Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.380977.1608048829000.112873.1629462660079%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu commented on FACT-3039 Re: Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 I think the issue here is caused by direct calls to `Facter.value` which are made in compiler.rb and in the providers. So Puppet calls Facter API directly. As Josh Cooper suggested here, there is the :memory indirector that can be used for facts but this is not for `Facter.value` calls. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.380977.1608048829000.111969.1629374940028%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu commented on FACT-3039 Re: Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 Given that when running tests with rspec-puppet/rspec-puppet-facts/facterdb the system facts should not matter(should not be resolved), I suggest moving on with monkey patching Facter 4 to not call the resolvers in the context of running specs. This will ensure that Facter 4 does not try to resolve facts for the current system when running modules unit tests(eg. platform specific catalog compilation) Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.380977.1608048829000.111914.1629363060103%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3039 Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 Change By: Gheorghe Popescu Attachment: facter4_exec_api.html Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.380977.1608048829000.111883.1629362100248%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu commented on FACT-3039 Re: Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 Running without a dummy Facter::Core::Execution.execute: Thread: 2160, Fiber: 2140 (100.00% ~ 0.016681278008036315) facter4_no_exec.html Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.380977.1608048829000.111859.1629361500099%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3039 Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 Change By: Gheorghe Popescu Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.380977.1608048829000.111858.1629361500047%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3039 Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 Change By: Gheorghe Popescu Attachment: facter4_no_exec.html Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.380977.1608048829000.111857.1629361440037%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title
Gheorghe Popescu commented on FACT-3039
Re: Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
So I did a profiling on calling `Facter.value(:kernel)` on Facter 4 and Facter 2 and Facter 4 is noticeably slower(0.13s vs 0.01s). From the call tree seems that the execution API is slower in Facter 4. Attached are the traces for each call: facter2.html - trace for calling `Facter.value(:kernel) with facter 2 Thread: 1580, Fiber: 1560 (100.00% ~ 0.010857273999135941) facter4.html - trace for calling `Facter.value(:kernel) with facter 4 Thread: 2160, Fiber: 2140 (37.49% ~ 0.13846525101689622) Thread: 2200, Fiber: 2180 (20.90% ~ 0.13846525101689622) Thread: 2240, Fiber: 2220 (20.83% ~ 0.13846525101689622) Thread: 2280, Fiber: 2260 (20.78% ~ 0.13846525101689622) facter4_patched.html - trace for calling `Facter.value(:kernel) with facter 4 without hitting the resolver. Monkey patching the BaseResolver class Thread: 2160, Fiber: 2140 (100.00% ~ 0.01828752097208053)
if defined? Facter::Resolvers::BaseResolver
Facter::Resolvers::BaseResolver.class_eval do
def self.resolve(_fact_name, _options = {}); end
end
end
Having rspec-puppet to monkey patch Facter 4(https://github.com/gimmyxd/rspec-puppet/commit/49a0c2128ff079a97d2322446098f09cdf6185b1), does not seem to improve the full test suite speed when running on gh actions. Locally I managed to get an improvement of around 20% when running a single test file from puppet-nginx module, for a single OS
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3039 Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 Change By: Gheorghe Popescu Attachment: facter4_patched.html Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.380977.1608048829000.110763.1629291840077%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3039 Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 Change By: Gheorghe Popescu Attachment: facter4.html Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.380977.1608048829000.110761.1629291780030%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3039 Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 Change By: Gheorghe Popescu Attachment: facter2.html Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.380977.1608048829000.110760.1629291720032%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Facter / FACT-3039 Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.380977.1608048829000.109209.1629185580033%40Atlassian.JIRA.
Jira (PUP-11196) puppet warns about BOM and US-ASCII encoding
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-11196 puppet warns about BOM and US-ASCII encoding Change By: Gheorghe Popescu Sprint: NW-2021-09-08 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.409781.1628013472000.108254.1629125280106%40Atlassian.JIRA.
Jira (FACT-3063) Facter unable to get processor speed on OS 11 arm64 which causes the resolver to blow up
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3063 Facter unable to get processor speed on OS 11 arm64 which causes the resolver to blow up Change By: Gheorghe Popescu Sprint: NW-2021-09-08 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.409868.1628076333000.108245.1629124620082%40Atlassian.JIRA.
Jira (PUP-11202) managehome=true on Windows fails
Title: Message Title Gheorghe Popescu assigned an issue to Luchian Nemes Puppet / PUP-11202 managehome=true on Windows fails Change By: Gheorghe Popescu Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.410110.1628257084000.108243.1629124560192%40Atlassian.JIRA.
Jira (FACT-3064) Please update Google GCE instance check
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3064 Please update Google GCE instance check Change By: Gheorghe Popescu Labels: help_wanted Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.411136.1628498413000.108215.1629124140045%40Atlassian.JIRA.
Jira (PUP-11204) puppet lookup --facts {filename} fails if filename does not contain a dot
Title: Message Title
Gheorghe Popescu updated an issue
Puppet / PUP-11204
puppet lookup --facts {filename} fails if filename does not contain a dot
Change By:
Gheorghe Popescu
Epic Link:
PUP-11052
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
--
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.411148.1628520098000.108200.1629123780069%40Atlassian.JIRA.
Jira (PUP-11205) implement snyk Code Scanning for puppet-agent component
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-11205 implement snyk Code Scanning for puppet-agent component Change By: Gheorghe Popescu Summary: implement snyk Code Scanning for puppet-agent project component Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.411605.1628754363000.108186.1629123420048%40Atlassian.JIRA.
Jira (PUP-11205) implement snyk Code Scanning for puppet-agent components
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-11205 implement snyk Code Scanning for puppet-agent components Change By: Gheorghe Popescu Summary: implement snyk Code Scanning for puppet-agent component components Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.411605.1628754363000.108187.1629123420092%40Atlassian.JIRA.
Jira (PUP-11165) Add 'scripts' directory to Puppet Module type (backport to Puppet 6)
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-11165 Add 'scripts' directory to Puppet Module type (backport to Puppet 6) Change By: Gheorghe Popescu Fix Version/s: PUP 7.10.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.406441.1625786345000.107730.1629100740036%40Atlassian.JIRA.
Jira (PUP-10539) Environment convergence
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10539 Environment convergence Change By: Gheorghe Popescu Release Notes: Not Needed Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.361774.159139350.106143.1628758020027%40Atlassian.JIRA.
Jira (PUP-11200) Allow loading from scripts mount when loading Task files
Title: Message Title Gheorghe Popescu commented on PUP-11200 Re: Allow loading from scripts mount when loading Task files passed main CI as part of https://github.com/puppetlabs/puppet/commit/8ed2564a3b0978ce0880af904df56d79637c15e8 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.410089.1628201512000.106137.1628757840031%40Atlassian.JIRA.
Jira (PUP-11199) Document exec type's 'onlyif' and 'unless' commands behavior with --noop
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-11199 Document exec type's 'onlyif' and 'unless' commands behavior with --noop Change By: Gheorghe Popescu Fix Version/s: PUP 7.10.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.410026.1628169495000.106125.1628757660136%40Atlassian.JIRA.
Jira (PUP-11201) Refine when the last used environment is used
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-11201 Refine when the last used environment is used Change By: Gheorghe Popescu Fix Version/s: PUP 7.10.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.410096.1628208242000.106126.1628757660180%40Atlassian.JIRA.
Jira (PUP-11165) Add 'scripts' directory to Puppet Module type (backport to Puppet 6)
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-11165 Add 'scripts' directory to Puppet Module type (backport to Puppet 6) Change By: Gheorghe Popescu Fix Version/s: PUP 7.10.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.406441.1625786345000.106124.1628757660078%40Atlassian.JIRA.
Jira (FACT-3043) pacman package provider failing for facter version 4.1.1
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3043 pacman package provider failing for facter version 4.1.1 Change By: Gheorghe Popescu Fix Version/s: FACT 4.2.3 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.399779.1621360795000.106117.1628757420089%40Atlassian.JIRA.
Jira (FACT-3032) Spec integration tests failing when IPv6 not set
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3032 Spec integration tests failing when IPv6 not set Change By: Gheorghe Popescu Fix Version/s: FACT 4.2.3 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.397332.1619595305000.106116.1628757420043%40Atlassian.JIRA.
Jira (FACT-3001) Debug output shows facter gets called thousands of times
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3001 Debug output shows facter gets called thousands of times Change By: Gheorghe Popescu Fix Version/s: FACT 4.2.3 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.393130.1617033494000.106115.1628757360034%40Atlassian.JIRA.
Jira (PUP-11172) undefined method `[]' for nil:NilClass when handling SemanticPuppet::Dependency::UnsatisfiableGraph
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-11172 undefined method `[]' for nil:NilClass when handling SemanticPuppet::Dependency::UnsatisfiableGraph Change By: Gheorghe Popescu Release Notes Summary: `puppet module install` could break in some cases when dependencies could not be resolved. The error cases are now treated and puppet emits an error message in this case. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.407578.1626862586000.96116.1627909380174%40Atlassian.JIRA.
Jira (PUP-11172) undefined method `[]' for nil:NilClass when handling SemanticPuppet::Dependency::UnsatisfiableGraph
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-11172 undefined method `[]' for nil:NilClass when handling SemanticPuppet::Dependency::UnsatisfiableGraph Change By: Gheorghe Popescu Release Notes: Bug Fix Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.407578.1626862586000.96115.1627909320035%40Atlassian.JIRA.
Jira (PUP-11193) SemanticPuppet does not solve nested dependencies
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-11193 SemanticPuppet does not solve nested dependencies Change By: Gheorghe Popescu Acceptance Criteria: SemanticPuppet returns the list of unsatisfied dependencies with all the information about the modules requiring it Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.409162.1627567017000.93931.1627567080033%40Atlassian.JIRA.
Jira (PUP-11193) SemanticPuppet does not solve nested dependencies
Title: Message Title
Gheorghe Popescu created an issue
Puppet / PUP-11193
SemanticPuppet does not solve nested dependencies
Issue Type:
Bug
Assignee:
Unassigned
Created:
2021/07/29 6:56 AM
Priority:
Normal
Reporter:
Gheorghe Popescu
Given the following dependencies list for a module:
"dependencies": [
{
"name": "elastic-elasticsearch",
"version_requirement": "6.4.0"
},
{
"name": "elastic-elastic_stack",
Jira (FACT-3060) AIX producing "Could not resolve mountpoints" with Facter 4
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-3060
AIX producing "Could not resolve mountpoints" with Facter 4
Change By:
Gheorghe Popescu
After agent upgrade to puppet-agent-7.8.0-1.aix7.1.ppc.rpm with facter 4.2, facter is producing "Could not resolve mountpoints" errors. This was not the case when using facter 3.14facter 4 removes anything that contains the word node: https://github.com/puppetlabs/facter/blame/main/lib/facter/resolvers/aix/mountpoints.rb#L22but this is causing failures when we combine mount data with df data(from where node is not removed): https://github.com/puppetlabs/facter/blame/main/lib/facter/resolvers/aix/mountpoints.rb#L37in cfacter we do not skip node: https://github.com/puppetlabs/facter/blob/3.x/lib/src/facts/aix/filesystem_resolver.cc#L55-L62How to reproduce the issue:Add the following data to facter fixtures :{noformat}# spec/fixtures/mount node mountedmounted overvfs dateoptions --- --- -- --- /dev/hd1 /x July 26 19:04 rw,log=/dev/hd3 /dev/hd2 /usr x July 26 19:04 rw,nodev,log=/dev/hd3# spec/fixtures/dfFilesystem512-blocks Used Available Capacity Mounted on/dev/hd1 111 1% //dev/hd2 111 1% /usr{noformat}debug the tests: bundle exec rspec spec/facter/resolvers/aix/mountpoints_spec.rb~* Please see Zendesk Support tab for further comments and attachments.~
Add Comment
Jira (FACT-3060) AIX producing "Could not resolve mountpoints" with Facter 4
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-3060
AIX producing "Could not resolve mountpoints" with Facter 4
Change By:
Gheorghe Popescu
After agent upgrade to puppet-agent-7.8.0-1.aix7.1.ppc.rpm with facter 4.2, facter is producing "Could not resolve mountpoints" errors. This was not the case when using facter 3.14facter 4 removes anything that contains the word node: https://github.com/puppetlabs/facter/blame/main/lib/facter/resolvers/aix/mountpoints.rb#L22but this is causing failures when we combine mount data with df data(from where node is not removed): https://github.com/puppetlabs/facter/blame/main/lib/facter/resolvers/aix/mountpoints.rb#L37in cfacter we do not skip node: https://github.com/puppetlabs/facter/blob/3.x/lib/src/facts/aix/filesystem_resolver.cc#L55-L62How to reproduce the issue:Add the following data to facter fixtures :{noformat}# spec/fixtures/mount node mountedmounted overvfs dateoptions --- --- -- --- /dev/hd1 /x July 26 19:04 rw,log=/dev/hd3 /dev/hd2 /usrx July 26 19:04 rw,nodev,log=/dev/hd3# spec/fixtures/dfFilesystem512-blocks Used Available Capacity Mounted on/dev/hd1 111 1% //dev/hd2 111 1% /usr{noformat}debug the tests: bundle exec rspec spec/facter/resolvers/aix/mountpoints_spec.rb~* Please see Zendesk Support tab for further comments and attachments.~
Add Comment
Jira (FACT-3060) AIX producing "Could not resolve mountpoints" with Facter 4
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-3060
AIX producing "Could not resolve mountpoints" with Facter 4
Change By:
Gheorghe Popescu
After agent upgrade to puppet-agent-7.8.0-1.aix7.1.ppc.rpm with facter 4.2, facter is producing "Could not resolve mountpoints" errors. This was not the case when using facter 3.14 facter 4 removes anything that contains the word node: https://github.com/puppetlabs/facter/blame/main/lib/facter/resolvers/aix/mountpoints.rb#L22but this is causing failures when we combine mount data with df data(from where node is not removed): https://github.com/puppetlabs/facter/blame/main/lib/facter/resolvers/aix/mountpoints.rb#L37in cfacter we do not skip node: https://github.com/puppetlabs/facter/blob/3.x/lib/src/facts/aix/filesystem_resolver.cc#L55-L62How to reproduce the issue:Add the following data to facter fixtures :{noformat}# spec/fixtures/mount node mountedmounted overvfs dateoptions --- --- -- --- /dev/hd1 /x July 26 19:04 rw,log=/dev/hd3 /dev/hd2 /usr x July 26 19:04 rw,nodev,log=/dev/hd3# spec/fixtures/dfFilesystem512-blocks Used Available Capacity Mounted on/dev/hd1 111 1% //dev/hd2 111 1% /usr{noformat}debug the tests: bundle exec rspec spec/facter/resolvers/aix/mountpoints_spec.rb ~* Please see Zendesk Support tab for further comments and attachments.~
Add Comment
Jira (PUP-11058) Detailed exitcode for 503s
Title: Message Title Gheorghe Popescu assigned an issue to Unassigned Puppet / PUP-11058 Detailed exitcode for 503s Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.398736.1620652163000.92741.1627481520754%40Atlassian.JIRA.
Jira (FACT-3059) AIX reporting "odd number of arguments for Hash" with Facter 4
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-3059
AIX reporting "odd number of arguments for Hash" with Facter 4
Change By:
Gheorghe Popescu
After agent upgrade to puppet-agent-7.8.0-1.aix7.1.ppc.rpm with facter 4.2, facter is producing "odd number of arguments for Hash" errors. This was not the case when using facter 3.14The issue is caused by https://github.com/puppetlabs/facter/blob/main/lib/facter/util/aix/info_extractor.rb#L14 which makes the assumption that keys are sparated by multiple spaces, and it will created erroneous data for a line like:{noformat}[1]> line=> "MOUNT POINT:/dev/1 LABEL: /dev/1\n"[2]> line.split(/:\s*|\s{2,}/)=> ["MOUNT POINT", "/dev/1 LABEL", "/dev/1\n"]{noformat}This Array is passed to Hash which raises `odd number of arguments ` because the number of arguments is even odd : https://github.com/puppetlabs/facter/blob/main/lib/facter/util/aix/info_extractor.rb#L19{noformat}Hash[*['a', 'b', 'c']]ArgumentError: odd number of arguments for Hash{noformat}~* Please see Zendesk Support tab for further comments and attachments.~
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (FACT-3059) AIX reporting "odd number of arguments for Hash" with Facter 4
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-3059
AIX reporting "odd number of arguments for Hash" with Facter 4
Change By:
Gheorghe Popescu
After agent upgrade to puppet-agent-7.8.0-1.aix7.1.ppc.rpm with facter 4.2, facter is producing "odd number of arguments for Hash" errors. This was not the case when using facter 3.14 The issue is caused by https://github.com/puppetlabs/facter/blob/main/lib/facter/util/aix/info_extractor.rb#L14 which makes the assumption that keys are sparated by multiple spaces, and it will created erroneous data for a line like:{noformat}[1]> line=> "MOUNT POINT:/dev/1 LABEL: /dev/1\n"[2]> line.split(/:\s*|\s{2,}/)=> ["MOUNT POINT", "/dev/1 LABEL", "/dev/1\n"]{noformat}This Array is passed to Hash which raises `odd number of arguments because the number of arguments is even: https://github.com/puppetlabs/facter/blob/main/lib/facter/util/aix/info_extractor.rb#L19{noformat}Hash[*['a', 'b', 'c']]ArgumentError: odd number of arguments for Hash{noformat} ~* Please see Zendesk Support tab for further comments and attachments.~
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11172) undefined method `[]' for nil:NilClass when handling SemanticPuppet::Dependency::UnsatisfiableGraph
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-11172 undefined method `[]' for nil:NilClass when handling SemanticPuppet::Dependency::UnsatisfiableGraph Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.407578.1626862586000.92501.1627469400041%40Atlassian.JIRA.
Jira (PUP-11058) Detailed exitcode for 503s
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-11058 Detailed exitcode for 503s Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.398736.1620652163000.92421.1627463040046%40Atlassian.JIRA.
Jira (PUP-10308) Puppet.lookup(:current_environment) is wrong if environment changes during convergence
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10308 Puppet.lookup(:current_environment) is wrong if environment changes during convergence Change By: Gheorghe Popescu Release Notes: Bug Fix Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.347236.1582308671000.89893.1627282740109%40Atlassian.JIRA.
Jira (PUP-10308) Puppet.lookup(:current_environment) is wrong if environment changes during convergence
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-10308 Puppet.lookup(:current_environment) is wrong if environment changes during convergence Change By: Gheorghe Popescu Release Notes Summary: Fixed a bug where an old environment could be used if the environment has changed due to pluginsync. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.347236.1582308671000.89892.1627282740050%40Atlassian.JIRA.
Jira (FACT-3001) Debug output shows facter gets called thousands of times
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3001 Debug output shows facter gets called thousands of times Change By: Gheorghe Popescu Release Notes: Enhancement Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.393130.1617033494000.87285.1626933420039%40Atlassian.JIRA.
Jira (PUP-11172) undefined method `[]' for nil:NilClass when handling SemanticPuppet::Dependency::UnsatisfiableGraph
Title: Message Title Gheorghe Popescu commented on PUP-11172 Re: undefined method `[]' for nil:NilClass when handling SemanticPuppet::Dependency::UnsatisfiableGraph Is there a way to get puppet to dump the dependency graph and/or to find out which of my dependencies is broken? This is what we've tried to do with the semantic_puppet changes, make it print the unsatisfiable dependencies. Since we have the list of dependencies that breaks I think we can work on improving the dependencies lookup. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.407578.1626862586000.87284.162693332%40Atlassian.JIRA.
Jira (PUP-11172) undefined method `[]' for nil:NilClass when handling SemanticPuppet::Dependency::UnsatisfiableGraph
Title: Message Title Gheorghe Popescu commented on PUP-11172 Re: undefined method `[]' for nil:NilClass when handling SemanticPuppet::Dependency::UnsatisfiableGraph This might be related to the semantic_puppet changes. It breaks with semnatic_puppet 1.0.4 and 1.0.3 but has a dependency resolution with semantic_puppet 1.0.2 I've created a dummy module with the same dependencies and this is the result: ❯ /opt/puppetlabs/puppet/bin/gem list semantic_puppet semantic_puppet (1.0.2) ❯ puppet module install /test-test_sp-0.1.0.tar.gz --debug --trace ... Info: Resolving dependencies ... Error: Could not install module 'test-test_sp' (v0.1.0) The requested version cannot satisfy all dependencies Use `puppet module install 'test-test_sp' --ignore-dependencies` to install only this modul
Jira (PUP-11168) Add RHEL9 support for services
Title: Message Title Gheorghe Popescu commented on PUP-11168 Re: Add RHEL9 support for services merged in 6.x at https://github.com/puppetlabs/puppet/commit/fd8a0ed4535005c3332ae3cd8a975cfc715d2287 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.406565.1626118192000.83904.1626674940044%40Atlassian.JIRA.
Jira (FACT-3043) pacman package provider failing for facter version 4.1.1
Title: Message Title Gheorghe Popescu commented on FACT-3043 Re: pacman package provider failing for facter version 4.1.1 merged in facter#main https://github.com/puppetlabs/facter/commit/f4094d9624d0984d861656e7e205a978f86fb84d Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.399779.1621360795000.82351.1626352860031%40Atlassian.JIRA.
Jira (FACT-3001) Debug output shows facter gets called thousands of times
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Facter / FACT-3001 Debug output shows facter gets called thousands of times Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.393130.1617033494000.81117.1626267660032%40Atlassian.JIRA.
Jira (FACT-3043) pacman package provider failing for facter version 4.1.1
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Facter / FACT-3043 pacman package provider failing for facter version 4.1.1 Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.399779.1621360795000.81069.1626260460028%40Atlassian.JIRA.
Jira (FACT-3032) Spec integration tests failing when IPv6 not set
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Facter / FACT-3032 Spec integration tests failing when IPv6 not set Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.397332.1619595305000.81037.1626257340033%40Atlassian.JIRA.
Jira (FACT-3055) facter ldom_domainrole_io showing no output
Title: Message Title Gheorghe Popescu commented on FACT-3055 Re: facter ldom_domainrole_io showing no output Hello, did you try `facter ldom.control.io` ? Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.405353.1625165519000.72438.1625222880038%40Atlassian.JIRA.
Jira (PUP-11129) Cached environment may not be deleted if the directory is removed
Title: Message Title Gheorghe Popescu commented on PUP-11129 Re: Cached environment may not be deleted if the directory is removed https://github.com/puppetlabs/puppet/pull/8663/files ❯ ls ~/.puppetlabs/etc/code/environments/ production 2.7.2 ❯ bx ruby envs.rb Listed test53724, production environments Deleted test53724 environment Listed production environments Add Comment
Jira (PUP-11129) Cached environment may not be deleted if the directory is removed
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-11129 Cached environment may not be deleted if the directory is removed Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.405015.162492624.69849.1625055780035%40Atlassian.JIRA.
Jira (FACT-3050) EC2 resolver failing with ruby 2.3.8p459 when token is nil
Title: Message Title Gheorghe Popescu assigned an issue to Dorin Pleava Facter / FACT-3050 EC2 resolver failing with ruby 2.3.8p459 when token is nil Change By: Gheorghe Popescu Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.402595.1623144533000.51872.1623223380042%40Atlassian.JIRA.
Jira (PUP-11069) [Ruby 3] Handle sorted_set removal in semantic_puppet gem
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-11069 [Ruby 3] Handle sorted_set removal in semantic_puppet gem Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.399744.1621342573000.44065.1622460780030%40Atlassian.JIRA.
Jira (PUP-11069) [Ruby 3] Handle sorted_set removal in semantic_puppet gem
Title: Message Title Gheorghe Popescu commented on PUP-11069 Re: [Ruby 3] Handle sorted_set removal in semantic_puppet gem https://github.com/puppetlabs/semantic_puppet/pull/38 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.399744.1621342573000.44043.1622449680055%40Atlassian.JIRA.
Jira (PUP-11076) Remove sorted_set usage
Title: Message Title Gheorghe Popescu commented on PUP-11076 Re: Remove sorted_set usage https://github.com/puppetlabs/puppet/pull/8613 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.401270.1622439562000.44042.1622449680034%40Atlassian.JIRA.
Jira (PUP-11076) Remove sorted_set usage
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-11076 Remove sorted_set usage Change By: Gheorghe Popescu Story Points: 1 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.401270.1622439562000.44000.1622443560030%40Atlassian.JIRA.
Jira (PUP-11076) Remove sorted_set usage
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-11076 Remove sorted_set usage Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.401270.1622439562000.43999.1622439900098%40Atlassian.JIRA.
Jira (PUP-11076) Remove sorted_set usage
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-11076 Remove sorted_set usage Change By: Gheorghe Popescu Epic Link: PUP- 10957 11071 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.401270.1622439562000.43998.1622439900049%40Atlassian.JIRA.
Jira (PUP-11076) Remove sorted_set usage
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-11076 Remove sorted_set usage Change By: Gheorghe Popescu Epic Link: PUP-10957 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.401270.1622439562000.43997.1622439840044%40Atlassian.JIRA.
Jira (PUP-11076) Remove sorted_set usage
Title: Message Title Gheorghe Popescu created an issue Puppet / PUP-11076 Remove sorted_set usage Issue Type: Improvement Assignee: Unassigned Created: 2021/05/30 10:39 PM Priority: Normal Reporter: Gheorghe Popescu Ruby 3 has removed sorted_set from the core and exposes it as an external gem. In puppet, we use it to store the versions of a package. This can be safely replaced by an Array. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (FACT-3046) Facter 4 CLI does not accept concatenated short flags
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3046 Facter 4 CLI does not accept concatenated short flags Change By: Gheorghe Popescu Acceptance Criteria: Combinations of short flags should work, eg -jp, -jdAt least all the ones combinations that worked on Facter 3 should work on Facter 4 also. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.400395.1621841877000.39368.1621856880103%40Atlassian.JIRA.
Jira (FACT-3046) Facter 4 CLI does not accept concatenated short flags
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3046 Facter 4 CLI does not accept concatenated short flags Change By: Gheorghe Popescu Acceptance Criteria: Combinations of short flags should work, eg -jp, -jd At least all the ones that worked on Facter 3 should work on Facter 4 also. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.400395.1621841877000.39290.1621845600029%40Atlassian.JIRA.
Jira (FACT-3046) Facter 4 CLI does not accept concatenated short flags
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-3046
Facter 4 CLI does not accept concatenated short flags
Change By:
Gheorghe Popescu
Trying to run `facter -jp` or `facter -dv` does not work, resulting in an error:{noformat}[2021-05-24 10:34:46.955480 ] ERROR Facter::OptionsValidator - unrecognised option '-p'{noformat} Some of the combinations works, for example `facter -jd` Previously this worked in Facter 3At the first glance seems that options defined with [class_option|https://github.com/puppetlabs/facter/blob/main/lib/facter/framework/cli/cli.rb#L40] can be combined, but the ones defined [with a specific mapping|https://github.com/puppetlabs/facter/blob/main/lib/facter/framework/cli/cli.rb#L159-L160] error out.
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
--
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+
Jira (FACT-3046) Facter 4 CLI does not accept concatenated short flags
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-3046
Facter 4 CLI does not accept concatenated short flags
Change By:
Gheorghe Popescu
Trying to run `facter -jp` or `facter -dv` does not work, resulting in an error:{noformat}[2021-05-24 10:34:46.955480 ] ERROR Facter::OptionsValidator - unrecognised option '-p'{noformat}Some of the combinations works, for example `facter -jd` Previously this worked in Facter 3 At the first glance seems that options defined with [class_option|https://github.com/puppetlabs/facter/blob/main/lib/facter/framework/cli/cli.rb#L40] can be combined, but the ones defined [with a specific mapping|https://github.com/puppetlabs/facter/blob/main/lib/facter/framework/cli/cli.rb#L159-L160] error out.
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
--
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+
Jira (FACT-3046) Facter 4 CLI does not accept concatenated short flags
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-3046
Facter 4 CLI does not accept concatenated short flags
Change By:
Gheorghe Popescu
Trying to run `facter -jp` or `facter -dv` does not work, resulting in an error:{noformat}[2021-05-24 10:34:46.955480 ] ERROR Facter::OptionsValidator - unrecognised option '-p'{noformat}Previously this worked in Facter 3At the first glance seems that options defined with [class_option|https://github.com/puppetlabs/facter/blob/main/lib/facter/framework/cli/cli.rb#L40] can be combined, but the ones defined [with a specific mapping error out. |https://github.com/puppetlabs/facter/blob/main/lib/facter/framework/cli/cli.rb#L159-L160] error out.
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
--
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 d
Jira (FACT-3046) Facter 4 CLI does not accept concatenated short flags
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-3046
Facter 4 CLI does not accept concatenated short flags
Change By:
Gheorghe Popescu
Trying to run `facter -jp` or `facter -dv` does not work, resulting in an error:{noformat}[2021-05-24 10:34:46.955480 ] ERROR Facter::OptionsValidator - unrecognised option '-p'{noformat}Previously with this worked in Facter 3At the first glance seems that options defined with [class_option|https://github.com/puppetlabs/facter/blob/main/lib/facter/framework/cli/cli.rb#L40] can be combined, but the ones defined [with a specific mapping error out.|https://github.com/puppetlabs/facter/blob/main/lib/facter/framework/cli/cli.rb#L159-L160]
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
--
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 discussio
Jira (FACT-3046) Facter 4 CLI does not accept concatenated short flags
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3046 Facter 4 CLI does not accept concatenated short flags Change By: Gheorghe Popescu Summary: Facter 4 CLI doe does not accept concatenated short flags Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.400395.1621841877000.39277.1621845060036%40Atlassian.JIRA.
Jira (FACT-3046) Facter 4 CLI doe not accept concatenated short flags
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-3046
Facter 4 CLI doe not accept concatenated short flags
Change By:
Gheorghe Popescu
Trying to run `facter -jp` or `facter -dv` does not work, resulting in an error:{noformat}[2021-05-24 10:34:46.955480 ] ERROR Facter::OptionsValidator - unrecognised option '-p'{noformat}Previously with worked in Facter 3At the first glance seems that options defined with [class_option|https://github.com/puppetlabs/facter/blob/main/lib/facter/framework/cli/cli.rb#L40 ] can be combined, but the ones defined [with a specific mapping error out.|https://github.com/puppetlabs/facter/blob/main/lib/facter/framework/cli/cli.rb#L159-L160]
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
--
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 th
Jira (FACT-3046) Facter 4 CLI doe not accept concatenated short flags
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-3046
Facter 4 CLI doe not accept concatenated short flags
Change By:
Gheorghe Popescu
Trying to run `facter -jp` or `facter -dv` does not work, resulting in an error:{noformat}[2021-05-24 10:34:46.955480 ] ERROR Facter::OptionsValidator - unrecognised option '-p'{noformat}Previously with worked in Facter 3At the first glance seems that options defined with ` [class_option|https://github.com/puppetlabs/facter/blob/main/lib/facter/framework/cli/cli.rb#L40 ` can be combined, but the ones defined [with a specific mapping error out.|https://github.com/puppetlabs/facter/blob/main/lib/facter/framework/cli/cli.rb#L159-L160]
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
--
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
Jira (FACT-3046) Facter 4 CLI doe not accept concatenated short flags
Title: Message Title
Gheorghe Popescu updated an issue
Facter / FACT-3046
Facter 4 CLI doe not accept concatenated short flags
Change By:
Gheorghe Popescu
Trying to run `facter -jp` or `facter -dv` does not work, resulting in an error:{noformat}[2021-05-24 10:34:46.955480 ] ERROR Facter::OptionsValidator - unrecognised option '-p'{noformat}Previously with worked in Facter 3At the first glance seems that options defined with `[class_option|https://github.com/puppetlabs/facter/blob/main/lib/facter/framework/cli/cli.rb#L40` can be combined, but the ones defined [with a specific mapping error out.|https://github.com/puppetlabs/facter/blob/main/lib/facter/framework/cli/cli.rb#L159-L160]
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
--
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 t
Jira (FACT-3046) Facter 4 CLI doe not accept concatenated short flags
Title: Message Title Gheorghe Popescu created an issue Facter / FACT-3046 Facter 4 CLI doe not accept concatenated short flags Issue Type: Bug Assignee: Unassigned Created: 2021/05/24 12:37 AM Priority: Normal Reporter: Gheorghe Popescu Trying to run `facter -jp` or `facter -dv` not work, resulting in an error: [2021-05-24 10:34:46.955480 ] ERROR Facter::OptionsValidator - unrecognised option '-p' Previously with worked in Facter 3 At the first glance seems that options defined with `[class_option|https://github.com/puppetlabs/facter/blob/main/lib/facter/framework/cli/cli.rb#L40` can be combined, but the ones defined with a specific mapping error out. Add Comment
Jira (FACT-3042) Facter should retrieve EC2 metadata using IMDSv2 without requring user configuration
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Facter / FACT-3042 Facter should retrieve EC2 metadata using IMDSv2 without requring user configuration Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.399711.1621283832000.37260.1621506660043%40Atlassian.JIRA.
Jira (FACT-3043) pacman package provider failing for facter version 4.1.1
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3043 pacman package provider failing for facter version 4.1.1 Change By: Gheorghe Popescu Labels: community Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.399779.1621360795000.36116.1621407120039%40Atlassian.JIRA.
Jira (FACT-3043) pacman package provider failing for facter version 4.1.1
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3043 pacman package provider failing for facter version 4.1.1 Change By: Gheorghe Popescu Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.399779.1621360795000.36115.1621407060098%40Atlassian.JIRA.
Jira (FACT-3043) pacman package provider failing for facter version 4.1.1
Title: Message Title Gheorghe Popescu moved an issue Facter / FACT-3043 pacman package provider failing for facter version 4.1.1 Change By: Gheorghe Popescu Component/s: Types and Providers Key: PUP FACT - 11070 3043 Affects Version/s: PUP 7.6.0 Affects Version/s: FACT 4.1.1 Project: Puppet Facter Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you a
Jira (PUP-11070) pacman package provider failing for facter version 4.1.1
Title: Message Title Gheorghe Popescu commented on PUP-11070 Re: pacman package provider failing for facter version 4.1.1 Hi Jim Richardson this seems to be a Facter issues because the value of the facts changed, I'll move it to the Facter project. Thanks for reporting Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.399779.1621360795000.36109.1621406760025%40Atlassian.JIRA.
Jira (PUP-11070) pacman package provider failing for facter version 4.1.1
Title: Message Title
Gheorghe Popescu updated an issue
Puppet / PUP-11070
pacman package provider failing for facter version 4.1.1
Change By:
Gheorghe Popescu
*Puppet Version: 7.6.1* *Puppet Server Version:* *OS Name/Version: Arch, Manjaro*Between facter version 3.14.16 and 4.1.1 the operatingsystem fact change value for Archlinux and Manjarolinux systems. I will paste below the old, and new versions, and a patch I applied that resolved my issue. { { code} $ facter --version3.14.16$ facter operatingsystemArchlinux$ facter --version4.1.1manjaro$ facter operatingsystemArchmanjaro$ facter --version4.1.1$ facter operatingsystemManjaro$ diff -uN gems/puppet-7.6.1/lib/puppet/provider/package/pacman.rb.original gems/puppet-7.6.1/lib/puppet/provider/package/pacman.rb--- gems/2.6.0/gems/puppet-7.6.1/lib/puppet/provider/package/pacman.rb.original 2021-05-18 13:42:53.605213957 -0400+++ gems/2.6.0/gems/puppet-7.6.1/lib/puppet/provider/package/pacman.rb 2021-05-18 13:44:11.515267826 -0400@@ -17,8 +17,8 @@ # Yaourt is a common AUR helper which, if installed, we can use to query the AUR commands :yaourt => "/usr/bin/yaourt" if yaourt? - confine :operatingsystem => [:archlinux, :manjarolinux]- defaultfor :operatingsystem => [:archlinux, :manjarolinux]+ confine :operatingsystem => [:archlinux, :manjarolinux, :arch, :manjaro]+ defaultfor :operatingsystem => [:archlinux, :manjarolinux, :arch, :manjaro] has_feature :install_options has_feature :uninstall_options has_feature :upgradeable {code } } *Desired Behavior:**Support new fact operatingsystem values for Archlinux family**Actual Behavior:**Fails to provide pacman support with new values.*
Add Comment
Jira (FACT-3027) Loosen the Ruby dependency to allow install on Ruby 3
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3027 Loosen the Ruby dependency to allow install on Ruby 3 Change By: Gheorghe Popescu Release Notes: Enhancement Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.396686.1619079094000.34971.1621342740104%40Atlassian.JIRA.
Jira (FACT-3027) Loosen the Ruby dependency to allow install on Ruby 3
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3027 Loosen the Ruby dependency to allow install on Ruby 3 Change By: Gheorghe Popescu Release Notes Summary: Allow facter gem to be installed on ruby 3 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.396686.1619079094000.34970.1621342740043%40Atlassian.JIRA.
Jira (FACT-2938) Ship facter 4 nightly gems
Title: Message Title Gheorghe Popescu commented on FACT-2938 Re: Ship facter 4 nightly gems nightly gems available at: http://nightlies.puppet.com/downloads/gems/facter-nightly/ Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.34801.1621321860155%40Atlassian.JIRA.
Jira (FACT-3040) undefined method `each_line' for nil:NilClass
Title: Message Title Gheorghe Popescu commented on FACT-3040 Re: undefined method `each_line' for nil:NilClass merged at https://github.com/puppetlabs/facter/commit/83ecb26ef2de5b3f7005ee88968fafa684020791 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.399650.1621235043000.34792.1621320840031%40Atlassian.JIRA.
Jira (FACT-3040) undefined method `each_line' for nil:NilClass
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Facter / FACT-3040 undefined method `each_line' for nil:NilClass Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.399650.1621235043000.34021.1621259340069%40Atlassian.JIRA.
Jira (FACT-3040) undefined method `each_line' for nil:NilClass
Title: Message Title
Gheorghe Popescu commented on FACT-3040
Re: undefined method `each_line' for nil:NilClass
Hi Jens, indeed this is a bug in Facter 4 that cannot correctly expand multi-line commands. As seen in your example:
"dpkg-query --showformat='${PACKAGE} ${VERSION}\n' --show | egrep '(^samba |^samba-winbind )'"
I've created https://github.com/puppetlabs/facter/pull/2385 to address this
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
--
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.399650.1621235043000.34013.1621258920129%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gheorghe Popescu commented on FACT-3039 Re: Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 So this looks like a Facter bug to me. I would think the core fact wouldn't be resolved if its weight is less than an already resolved custom fact The complication here is that Facter 4 implementation follows Facter 3, but modules unit tests were never run with Facter 3, and rspec-puppet was developed around Facter 2. Maybe this is an improvement that we can do but needs to be extensively tested. Running ` facter --custom-dir /tmp/facts ipaddress` on Facter 3 will end up resolving the whole networking fact 2021-05-14 08:28:46.824626 DEBUG puppetlabs.facter - resolving networking facts. 2021-05-14 08:28:46.824754 DEBUG puppetlabs.facter - using the FQDN returned by gethostname 2021-05-14 08:28:46.825142 DEBUG leatherman.execution:93 - executing command: /sbin/route -n get default 2021-05-14 08:28:46.829662 DEBUG leatherman.execution:93 - executing command: /usr/sbin/ipconfig getoption 2021-05-14 08:28:46.885004 DEBUG puppetlabs.facter - fact "dhcp_servers" has resolved to ... 127.0.0.1 The ip related commands are triggered when puppet's compiler tries to add server facts https://github.com/puppetlabs/puppet/blob/93c86d6dc8e9a0d84032e46b1d4c632df5254c00/lib/puppet/indirector/catalog/compiler.rb#L418. Recently changed `Facter.value` on Facter 4 to behave like Facter 3 in order to avoid issues like: https://t
Jira (FACT-3038) Unify spec folder structure
Title: Message Title Gheorghe Popescu created an issue Facter / FACT-3038 Unify spec folder structure Issue Type: Task Assignee: Unassigned Created: 2021/05/13 12:12 AM Priority: Normal Reporter: Gheorghe Popescu Currently facter has `spec` and `spec_integration` directories for unit and integration tests. Each folder has a `spec_helper.rb` which duplicates the common rspec config. We could unify this if we restructure the folders as: facter └── spec ├── spec_helper.rb # common config ├── integration │ └── spec_helper.rb # integration specific config └── unit
Jira (FACT-3006) Centralize and document fact matching and filtering
Title: Message Title Gheorghe Popescu updated an issue Facter / FACT-3006 Centralize and document fact matching and filtering Change By: Gheorghe Popescu Release Notes Summary: Improves the overall mechanism of fact filtering and matching. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.394894.1618225336000.32307.1620886020031%40Atlassian.JIRA.
