Jira (PUP-8539) Hiera trusted fact lookup
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8539 Hiera trusted fact lookup Change By: Josh Cooper Epic Link: PUP-6870 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.220490.1509835991000.154317.1614629580141%40Atlassian.JIRA.
Jira (PUP-8539) Hiera trusted fact lookup
Title: Message Title
Josh Cooper commented on PUP-8539
Re: Hiera trusted fact lookup
It doesn't appear interpolation of trusted data is working ... Note the missing hostname in .../nodes/.yaml when looking up lookup_options and the value of foo: Using hiera.yaml:
---
version: 5
defaults:
datadir: "data"
hierarchy:
- name: "Yaml backend"
data_hash: yaml_data
paths:
- "nodes/%{trusted.certname}.yaml"
- "common.yaml"
Jira (PDB-5042) Add option to execute queries with EXPLAIN ANALYZE to PuppetDBServer TK query method
Title: Message Title Zachary Kent commented on PDB-5042 Re: Add option to execute queries with EXPLAIN ANALYZE to PuppetDBServer TK query method Sorry, just saw your comment. For now we should see if we can return the result using the streaming that regular queries use. If we have the EXPLAIN output format set to JSON we might be able to stream it back to the caller without needing changes. If that's the case having a tests which looks at the explain result and asserts something about the explain format is sufficient. If we require changes to the streaming to account for the EXPLAIN ANALYZE output we can document the errors here and either attempt to address them or create a new ticket. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.388356.161402472.154310.1614629400191%40Atlassian.JIRA.
Jira (PUP-9692) hiera explain should redact values converted to Sensitive in --debug mode
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-9692
hiera explain should redact values converted to Sensitive in --debug mode
Change By:
Josh Cooper
Environment:
Problem 1:When puppet agent is run with --debug option, passwords get logged in plain-text, although the passwords are stored encrypted in the yaml.Example:2019-05-03 15:58:36 -0700 Puppet (debug): Lookup of 'my_con_pwd' Searching for "my_con_pwd" Global Data Provider (hiera configuration version 3) Using configuration "/home/tstuser/puppet/hiera.yaml" Hierarchy entry "eyaml" Path "/home/tstuser/puppet/production/data/defaults.yaml" Original path: "defaults" No such key: "my_con_pwd" Path "/home/tstuser/puppet/production/data/my_prod_config.yaml" Original path: "my_prod_config." Found key: "my_con_pwd" value: "MyT3stP"The password is not redacted even if lookup_options is added for this data, with convert_to: Sensitive --The lookup_options is set in common.yaml like:lookup_options: "^*my_con_pwd": convert_to: - "Sensitive"Puppet seems to detect that this data is sensitive, because it displays the following message after the lookup:Applying convert_to lookup_option with arguments [Sensitive]But the value is not redacted, as shown in the log snippet.Problem 2:If lookup_option is configured as shown above but this data is interpolated for another setting in a list, like:my_env_list: db_settings: db_pwd: "%\{hiera('my_con_pwd')}"then the following error occurs:2019-05-03 16:11:26 -0700 Puppet (err): Evaluation Error: Error while evaluating a Function Call, Lookup of key failed: The convert_to lookup_option for key 'my_con_pwd' raised error: undefined method `call_function' for #Please let me know if there is any other way to redact passwords when --debug is used. Although this occurs only when --debug is passed, it is not acceptable security practice.
Add Comment
Jira (PUP-9692) hiera explain should redact values converted to Sensitive in --debug mode
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-9692
hiera explain should redact values converted to Sensitive in --debug mode
Change By:
Josh Cooper
When using hiera's convert_to Sensitive, the explain output that is turned on by --debug will include the clear text looked up value as the explainer traces the lookup. Later this value is converted to Sensitive.The desire is that such values would be redacted in the log. *Original Text*Problem 1:When puppet agent is run with --debug option, passwords get logged in plain-text, although the passwords are stored encrypted in the yaml.Example:2019-05-03 15:58:36 -0700 Puppet (debug): Lookup of 'my_con_pwd' Searching for "my_con_pwd" Global Data Provider (hiera configuration version 3) Using configuration "/home/tstuser/puppet/hiera.yaml" Hierarchy entry "eyaml" Path "/home/tstuser/puppet/production/data/defaults.yaml" Original path: "defaults" No such key: "my_con_pwd" Path "/home/tstuser/puppet/production/data/my_prod_config.yaml" Original path: "my_prod_config." Found key: "my_con_pwd" value: "MyT3stP"The password is not redacted even if lookup_options is added for this data, with convert_to: Sensitive --The lookup_options is set in common.yaml like:lookup_options: "^*my_con_pwd": convert_to: - "Sensitive"Puppet seems to detect that this data is sensitive, because it displays the following message after the lookup:Applying convert_to lookup_option with arguments [Sensitive]But the value is not redacted, as shown in the log snippet.Problem 2:If lookup_option is configured as shown above but this data is interpolated for another setting in a list, like:my_env_list: db_settings: db_pwd: "%\{hiera('my_con_pwd')}"then the following error occurs:2019-05-03 16:11:26 -0700 Puppet (err): Evaluation Error: Error while evaluating a Function Call, Lookup of key failed: The convert_to lookup_option for key 'my_con_pwd' raised error: undefined method `call_function' for #Please let me know if there is any other way to redact passwords when --debug is used. Although this occurs only when --debug is passed, it is not acceptable security practice.
Add Comment
Jira (PUP-10940) 'puppet facts diff' logs error when apt module is installed
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10940 'puppet facts diff' logs error when apt module is installed Change By: Josh Cooper Fix Version/s: PUP 6.22.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.388736.1614177116000.154254.1614628440037%40Atlassian.JIRA.
Jira (PUP-10888) Add "puppet ssl show" command
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10888 Add "puppet ssl show" command Change By: Josh Cooper Fix Version/s: PUP 7.5.0 Fix Version/s: PUP 6.22.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.386463.1612550241000.154252.1614628380151%40Atlassian.JIRA.
Jira (PUP-10898) Get fully qualified current domain user name
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10898 Get fully qualified current domain user name Change By: Josh Cooper Fix Version/s: PUP 6.22.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387116.1613055296000.154251.1614628380108%40Atlassian.JIRA.
Jira (PUP-10853) When blocking legacy facts in puppet7, puppet agent run fails to fetch 'operatingsystem' fact
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10853 When blocking legacy facts in puppet7, puppet agent run fails to fetch 'operatingsystem' fact Change By: Josh Cooper Fix Version/s: PUP 7.5.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.383136.1610563179000.154253.1614628380196%40Atlassian.JIRA.
Jira (PUP-10899) Retrieve SID for users under 'APPLICATION PACKAGE AUTHORITY'
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10899 Retrieve SID for users under 'APPLICATION PACKAGE AUTHORITY' Change By: Josh Cooper Fix Version/s: PUP 7.5.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387120.1613057573000.154247.1614628320060%40Atlassian.JIRA.
Jira (PUP-10899) Retrieve SID for users under 'APPLICATION PACKAGE AUTHORITY'
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10899 Retrieve SID for users under 'APPLICATION PACKAGE AUTHORITY' Change By: Josh Cooper Fix Version/s: PUP 6.22.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387120.1613057573000.154249.1614628320151%40Atlassian.JIRA.
Jira (PUP-10898) Get fully qualified current domain user name
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10898 Get fully qualified current domain user name Change By: Josh Cooper Fix Version/s: PUP 7.5.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387116.1613055296000.154248.1614628320105%40Atlassian.JIRA.
Jira (PUP-10929) Syntax error in previously valid puppet code due to removal of application orchestration keywords
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10929 Syntax error in previously valid puppet code due to removal of application orchestration keywords Change By: Josh Cooper Fix Version/s: PUP 7.5.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.388276.1614006941000.154245.1614628260458%40Atlassian.JIRA.
Jira (PUP-10940) 'puppet facts diff' logs error when apt module is installed
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10940 'puppet facts diff' logs error when apt module is installed Change By: Josh Cooper Fix Version/s: PUP 7.5.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.388736.1614177116000.154246.1614628260504%40Atlassian.JIRA.
Jira (PDB-4998) Update PE console fact filtering to prevent timeouts
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4998 Update PE console fact filtering to prevent timeouts Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.382202.1609881088000.154217.1614627600041%40Atlassian.JIRA.
Jira (PUP-10929) Syntax error in previously valid puppet code due to removal of application orchestration keywords
Title: Message Title Henrik Lindberg commented on PUP-10929 Re: Syntax error in previously valid puppet code due to removal of application orchestration keywords Josh Cooper The benefit of keeping them reserved is that you may want to use them in the future for something other than the now removed application orchestration and it takes a major release to get there plus a lot of pain for users if they again would be put to use if they had been free to use for a while. You are right about the options. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.388276.1614006941000.154108.1614622080320%40Atlassian.JIRA.
Jira (PUP-10929) Syntax error in previously valid puppet code due to removal of application orchestration keywords
Title: Message Title Josh Cooper commented on PUP-10929 Re: Syntax error in previously valid puppet code due to removal of application orchestration keywords Henrik Lindberg What's the benefit to keeping those keywords reserved? It's not like someone can turn application orchestration back on. It sounds like our options are: 1. Remove site, etc keywords from the reserved list, OR 2. Update the grammar to accept the reserved keywords and regenerate the eparser. See af9b8e0894c2d606e81671fb133d4ef73d9ed7ef and de9c2b3b01ae7202ef441da0dbc41108b8ca013a. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.388276.1614006941000.154014.1614620040035%40Atlassian.JIRA.
Jira (PUP-10944) Enum.new
Title: Message Title Nodøn created an issue Puppet / PUP-10944 Enum.new Issue Type: New Feature Assignee: Unassigned Components: Type System Created: 2021/03/01 8:28 AM Priority: Normal Reporter: Nodøn helindbe and I had a chat in the slack today: https://puppetcommunity.slack.com/archives/C0W298S9G/p1614611196389300 The result of it is, that it would be nice to be able to `Enum.new`: Boolean function parameter: Enum['apple', 'banana'](false) -> 'apple' Integer function parameter: Enum['apple', 'banana', 'orange'](2) -> 'orange' Add Comment
Jira (FACT-2951) Facter 3 bad network when connected to a VPN
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network when connected to a VPN Change By: Dorin Pleava Attachment: image-2021-03-01-16-21-03-365.png Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389260.1614594854000.153815.1614608520049%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network when connected to a VPN
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network when connected to a VPN Change By: Dorin Pleava On OSX(could be on other platforms as-well), when connected to a VPN, Facter 3 shows network incorrect.Facter 3 uses `route -n get default` to get the primary interface(utun for VPN interfaces), and then runs `ipconfig getoption server_identifier` to try to get the dhcp server. For some reason when running ipconfig getoption on interfaces that are used for VPN connection nothing is outputted.Facter 4 relies on `ifconfig` command and it works as expected. The bug can be recreated without a VPN, by using VirtualBox: # Install VirtualBox # In VirtualBox, File -> Host Network Manager -> create a vboxnet0 adapter using 255.255.255.0 as IPv4 Network Mask !image-2021-03-01-16- 03 20 - 50 42 - 857 413 .png|width= 263 222 ,height= 240 201 !3. Edit/Create a virtual machine, go to machine settings -> Network, and make sure one Adapter is `Host-Only Adapter` that uses your vboxnet0.4. Start the VM, and locally, run puppet facts diff.!image-2021-03-01-16- 14 21 - 18 03 - 644 365 .png|width= 361 285 ,height= 188 149 !I think facter 3 cannot read the vboxnet0 netmask using `ipconfig getoption vboxnet0 server_identifier` so it cannot calculate the network. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2951) Facter 3 bad network when connected to a VPN
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network when connected to a VPN Change By: Dorin Pleava Attachment: image-2021-03-01-16-20-42-413.png Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389260.1614594854000.153814.1614608460090%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network when connected to a VPN
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network when connected to a VPN Change By: Dorin Pleava On OSX(could be on other platforms as-well), when connected to a VPN, Facter 3 shows network incorrect.Facter 3 uses `route -n get default` to get the primary interface(utun for VPN interfaces), and then runs `ipconfig getoption server_identifier` to try to get the dhcp server. For some reason when running ipconfig getoption on interfaces that are used for VPN connection nothing is outputted.Facter 4 relies on `ifconfig` command and it works as expected. The bug can be recreated without a VPN, by using VirtualBox: # Install VirtualBox # In VirtualBox, File -> Host Network Manager -> create a vboxnet0 adapter using 255.255.255.0 as IPv4 Network Mask !image-2021-03-01-16-03-50-857.png|width=263,height=240!3. Edit/Create a virtual machine, go to machine settings -> Network, and make sure one Adapter is `Host-Only Adapter` that uses your vboxnet0.4. Start the VM, and locally, run puppet facts diff.!image-2021-03-01-16-14-18-644.png|width=361,height=188!I think facter 3 cannot read the vboxnet0 netmask using `ipconfig getoption vboxnet0 server_identifier` so it cannot calculate the network. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2951) Facter 3 bad network when connected to a VPN
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network when connected to a VPN Change By: Dorin Pleava On OSX(could be on other platforms as-well), when connected to a VPN, Facter 3 shows network incorrect.Facter 3 uses `route -n get default` to get the primary interface(utun for VPN interfaces), and then runs `ipconfig getoption server_identifier` to try to get the dhcp server. For some reason when running ipconfig getoption on interfaces that are used for VPN connection nothing is outputted.Facter 4 relies on `ifconfig` command and it works as expected. The bug can be recreated without a VPN, by using VirtualBox: # Install VirtualBox # In VirtualBox, File -> Host Network Manager -> create a vboxnet0 adapter using 255.255.255.0 as IPv4 Network Mask !image-2021-03-01-16-03-50-857.png|width=263,height=240!3. Edit/Create a virtual machine, go to machine settings -> Network, and make sure one Adapter is `Host-Only Adapter` that uses your vboxnet0.4. Start the VM, and locally, run puppet facts diff.!image-2021-03-01-16-14-18-644.png|width=361,height=188!I think facter 3 cannot read the vboxnet0 netmask using `ipconfig getoption vboxnet0 server_identifier` so it cannot calculate the network. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2943) Fix os.name detection of AlmaLinux
Title: Message Title Christoph Schug commented on FACT-2943 Re: Fix os.name detection of AlmaLinux Vadym Chepkov, Facter 4 is fine, apparently it uses a different logic than Facter 3. Tested with Facter version 4.0.51 as provided by the puppet-agent-7.4.1-1.el8 RPM package. It's just Facter 3 which needed the fix, thanks for the merge! Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387803.1613568551000.153791.1614604500044%40Atlassian.JIRA.
Jira (PDB-5042) Add option to execute queries with EXPLAIN ANALYZE to PuppetDBServer TK query method
Title: Message Title Oana Tanasoiu assigned an issue to Unassigned PuppetDB / PDB-5042 Add option to execute queries with EXPLAIN ANALYZE to PuppetDBServer TK query method Change By: Oana Tanasoiu Assignee: Oana Tanasoiu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.388356.161402472.153765.1614599400049%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network when connected to a VPN
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network when connected to a VPN Change By: Dorin Pleava Acceptance Criteria: When connected to a VPN, running `facter network` with facter 3, i get a different network than running the same command with facter 4. I assume facter 3 output is incorrect as `facter networking.ip` matches the `facter network`. `facter network should show the correct network` Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389260.1614594854000.153747.1614596340030%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network when connected to a VPN
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network when connected to a VPN Change By: Dorin Pleava Acceptance Criteria: When connected to a VPN, running `facter network` with facter 3, i get a different network than running the same command with facter 4. I assume facter 3 output is incorrect as `facter networking.ip` matches the `facter network`. Affects Version/s: FACT 3.14.1 On OSX(could be on other platforms as-well), when connected to a VPN, Facter 3 shows network incorrect.Facter 3 uses `route -n get default` to get the primary interface(utun for VPN interfaces), and then runs `ipconfig getoption server_identifier` to try to get the dhcp server. For some reason when running ipconfig getoption on interfaces that are used for VPN connection nothing is outputted.Facter 4 relies on `ifconfig` command and it works as expected. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2951) Facter 3 bad network when connected to a VPN
Title: Message Title Dorin Pleava created an issue Facter / FACT-2951 Facter 3 bad network when connected to a VPN Issue Type: Bug Assignee: Unassigned Created: 2021/03/01 2:34 AM Priority: Normal Reporter: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit
Jira (FACT-2940) puppet facts diff shows inconsistent networking values on macOS
Title: Message Title Dorin Pleava commented on FACT-2940 Re: puppet facts diff shows inconsistent networking values on macOS I managed to reproduce but only when connected to a VPN. Facter 4 seems to work correctly as it relies on the `ifconfig` output. Facter 3 uses `route -n get default` to get the primary interface, and then runs `ipconfig getoption utun2 server_identifier` to try to get the dhcp server. For some reason when running ipconfig getoption on interfaces that are used for VPN connection nothing is outputted. Created https://tickets.puppetlabs.com/browse/FACT-2951 to keep track of the issue. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387708.1613500315000.153724.1614594900115%40Atlassian.JIRA.
Jira (FACT-2944) During Puppet 7 upgrade from Puppet 6, Puppet Server create another certname
Title: Message Title Bogdan Irimie assigned an issue to Oana Tanasoiu Facter / FACT-2944 During Puppet 7 upgrade from Puppet 6, Puppet Server create another certname Change By: Bogdan Irimie Assignee: Oana Tanasoiu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387583.1613309929000.153710.1614591060117%40Atlassian.JIRA.
Jira (FACT-2944) During Puppet 7 upgrade from Puppet 6, Puppet Server create another certname
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2944 During Puppet 7 upgrade from Puppet 6, Puppet Server create another certname Change By: Bogdan Irimie Sprint: NW ghost - 2021- 10. 03 -17 .2021 Team: Night's Watch Ghost Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387583.1613309929000.153709.1614591060058%40Atlassian.JIRA.
Jira (FACT-2944) During Puppet 7 upgrade from Puppet 6, Puppet Server create another certname
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2944 During Puppet 7 upgrade from Puppet 6, Puppet Server create another certname Change By: Bogdan Irimie Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387583.1613309929000.153708.1614590940036%40Atlassian.JIRA.
Jira (FACT-2950) Root of structured core facts cannot be overriden by a custom fact
Title: Message Title
Bogdan Irimie updated an issue
Facter / FACT-2950
Root of structured core facts cannot be overriden by a custom fact
Change By:
Bogdan Irimie
Facter represents structured facts as a list of path paths e.g.{code}os => { architecture => "x86_64", family => "Darwin", ... release => {full => "20.3.0",major => "20",minor => "3" }}{code}will be represented as{code}os.architectureos.familyos.release.fullos.release.majoros.release.minor{code}"os" is never represented as a fact name.When we create a custom fact "os", we don't override the list of facts, we just create a new fact and add it to that list{code}osos.architectureos.familyos.release.fullos.release.majoros.release.minor{code}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
