Jira (FACT-3063) Facter unable to get processor speed on OS 11 arm64 which causes the resolver to blow up
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Facter / FACT-3063 Facter unable to get processor speed on OS 11 arm64 which causes the resolver to blow up Change By: Dorin Pleava 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.409868.1628076333000.110667.1629280200206%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 Ciprian Badescu 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: Ciprian Badescu Story Points: 2 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.110486.1629274440045%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 Ciprian Badescu 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: Ciprian Badescu Sprint: NW-2021- 09- 08 -25 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.110487.1629274440104%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 (FACT-3063) Facter unable to get processor speed on OS 11 arm64 which causes the resolver to blow up
Title: Message Title
Gabriel Nagy 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:
Gabriel Nagy
Facter queries the following items on macOS using sysctl:{code:java}ITEMS = { logical_count: 'hw.logicalcpu_max', physical_count: 'hw.physicalcpu_max', brand: 'machdep.cpu.brand_string', speed: 'hw.cpufrequency_max', cores_per_socket: 'machdep.cpu.core_count', threads_per_core: 'machdep.cpu.thread_count' }.freeze {code}The outputs get passed like this to {{build_fact_list}}:{code} def build_fact_list(processors_data)build_logical_count(processors_data[0])build_physical_count(processors_data[1])build_models(processors_data[2])build_speed(processors_data[3])build_cores_per_socket(processors_data[4])build_threads_per_core(processors_data[5], processors_data[4]) end{code}The problem surfaces when {{processors_data}} is missing one of the outputs from {{ITEMS}} and methods end up being called with {{nil}}.In our case {{hw.cpufrequency_max}} is empty so the entire {{processors_data}} output is shifted and one element short.We need to ensure the resolver works even if not all sysctl queries resolve; and fix the processor speed fact (if possible). Resolver in question: https://github.com/puppetlabs/facter/blob/main/lib/facter/resolvers/macosx/processor.rb (nit: the filename should be processors not processor)
Add Comment
Jira (FACT-3063) Facter unable to get processor speed on OS 11 arm64 which causes the resolver to blow up
Title: Message Title
Gabriel Nagy created an issue
Facter / FACT-3063
Facter unable to get processor speed on OS 11 arm64 which causes the resolver to blow up
Issue Type:
Bug
Affects Versions:
FACT 4.2.2
Assignee:
Unassigned
Created:
2021/08/04 4:25 AM
Priority:
Normal
Reporter:
Gabriel Nagy
Facter queries the following items on macOS using sysctl:
ITEMS = { logical_count: 'hw.logicalcpu_max',
physical_count: 'hw.physicalcpu_max',
brand: 'machdep.cpu.brand_string',
speed: 'hw.cpufrequency_max',
cores_per_socket: 'machdep.cpu.core_count',
