Jira (PUP-11370) Move to windows-latest github runner
Title: Message Title Dorin Pleava commented on PUP-11370 Re: Move to windows-latest github runner Facter 3.x PR: https://github.com/puppetlabs/facter/pull/2471 Facter main PR: https://github.com/puppetlabs/facter/pull/2472 sshkeys_core PR: https://github.com/puppetlabs/puppetlabs-sshkeys_core/pull/56 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.425267.1638289614000.17708.1641910680034%40Atlassian.JIRA.
Jira (PUP-11332) Puppet user and service resources are slow on OSX
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-11332 Puppet user and service resources are slow on OSX Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.422283.1636054773000.11550.1641296340091%40Atlassian.JIRA.
Jira (FACT-3099) Caching UTF8 values results in "\\xCC" from ASCII-8BIT to UTF-8
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Facter / FACT-3099 Caching UTF8 values results in "\\xCC" from ASCII-8BIT to UTF-8 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.424265.1637249217000.20608.1638801840065%40Atlassian.JIRA.
Jira (FACT-3099) Caching UTF8 values results in "\\xCC" from ASCII-8BIT to UTF-8
Title: Message Title Dorin Pleava commented on FACT-3099 Re: Caching UTF8 values results in "\\xCC" from ASCII-8BIT to UTF-8 Managed to reproduce this with a configured ec2 instance that had ec2_userdata set to some UTF-8 values. I did not reproduce this with a custom fact that returns UTF-8 data. Also this ""xCC" from ASCII-8BIT to UTF-8" happens when outputting combination if ASCII and UTF-8 facts. $ facter ec2_userdata - [ vdb, /build1, "xfs", "nofail̦", "0", "0" ] $ facter uptime 0:49 hours $ facter uptime ec2_userdata Traceback (most recent call last): 13: from /opt/puppetlabs/puppet/bin/facter:10:in `' 12: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/cli/cli_launcher.rb:23:in `start' 11: from /opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/thor-1.1.0/lib/thor/base.rb:485:in `start' 10: from /opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/thor-1.1.0/lib/thor.rb:392:in `dispatch' 9: from /opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/thor-1.1.0/lib/thor/invocation.rb:127:in `invoke_command'
Jira (PUP-11352) ToDataSerializer which loses track of the current path
Title: Message Title Dorin Pleava assigned an issue to Unassigned Puppet / PUP-11352 ToDataSerializer which loses track of the current path 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.423439.1636986377000.10490.1637245800070%40Atlassian.JIRA.
Jira (PUP-11352) ToDataSerializer which loses track of the current path
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-11352 ToDataSerializer which loses track of the current path 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.423439.1636986377000.9259.1637150100038%40Atlassian.JIRA.
Jira (PUP-4045) Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket
Title: Message Title Dorin Pleava assigned an issue to Unassigned Puppet / PUP-4045 Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket 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.69478.1424944721000.8216.1637061180033%40Atlassian.JIRA.
Jira (PUP-4045) Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-4045 Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket 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.69478.1424944721000.8121.1637056860176%40Atlassian.JIRA.
Jira (PUP-8220) Verify trusted facts are overridden consistently
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-8220 Verify trusted facts are overridden consistently Change By: Dorin Pleava Release Notes: Bug Fix Release Notes Summary: When using puppet lookup with --facts, if the facts file overrides any ofhostname, domain, fqdn, clientcert, then it must override all of them. 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.224769.1512033958000.6979.1636984200040%40Atlassian.JIRA.
Jira (FACT-3079) Caching not working for some custom facts
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Facter / FACT-3079 Caching not working for some custom facts 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.418624.1633530707000.169107.1635945420049%40Atlassian.JIRA.
Jira (PUP-8220) Verify trusted facts are overridden consistently
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-8220 Verify trusted facts are overridden consistently 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.224769.1512033958000.161224.1634897820039%40Atlassian.JIRA.
Jira (PUP-11235) versioncmp() thinks 11.0 is greater than 11
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-11235 versioncmp() thinks 11.0 is greater than 11 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.413995.1630486051000.142455.1632935460032%40Atlassian.JIRA.
Jira (FACT-3073) Inconsistencies to set Facter::Core::Execution.execute timeout
Title: Message Title Dorin Pleava updated an issue Facter / FACT-3073 Inconsistencies to set Facter::Core::Execution.execute timeout Change By: Dorin Pleava Fix Version/s: FACT 4.2.5 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.415028.1631164898000.140703.1632816360032%40Atlassian.JIRA.
Jira (PUP-11232) freeze string in the prime candidates files
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-11232 freeze string in the prime candidates files Change By: Dorin Pleava Fix Version/s: PUP 6.25.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.413213.1629801903000.139930.1632747300033%40Atlassian.JIRA.
Jira (PUP-11205) implement snyk Code Scanning for puppet
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-11205 implement snyk Code Scanning for puppet Change By: Dorin Pleava Fix Version/s: PUP 6.25.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.411605.1628754363000.139929.1632747240095%40Atlassian.JIRA.
Jira (PUP-11201) Refine when the last used environment is used
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-11201 Refine when the last used environment is used Change By: Dorin Pleava Fix Version/s: PUP 6.25.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.139928.1632747240049%40Atlassian.JIRA.
Jira (PUP-11199) Document exec type's 'onlyif' and 'unless' commands behavior with --noop
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-11199 Document exec type's 'onlyif' and 'unless' commands behavior with --noop Change By: Dorin Pleava Fix Version/s: PUP 6.25.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.139927.1632747180087%40Atlassian.JIRA.
Jira (PUP-10897) List "manages local users and groups" (forcelocal) provider support as "with libuser"
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-10897 List "manages local users and groups" (forcelocal) provider support as "with libuser" Change By: Dorin Pleava Fix Version/s: PUP 6.25.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.387112.1613051573000.139926.1632747180066%40Atlassian.JIRA.
Jira (PUP-11208) Puppet fails to install packages on Solaris if another pkg install is running
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-11208 Puppet fails to install packages on Solaris if another pkg install is running 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.412673.1629371858000.136424.1632309840040%40Atlassian.JIRA.
Jira (FACT-3047) Add option to show HTTP debug logs in Facter 4
Title: Message Title Dorin Pleava updated an issue Facter / FACT-3047 Add option to show HTTP debug logs in Facter 4 Change By: Dorin Pleava Release Notes: New Feature Release Notes Summary: --http_debug option was added to Facter 4 cli to show HTTP debug logs. 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.400559.1621927319000.133457.1632125220029%40Atlassian.JIRA.
Jira (FACT-3047) Add option to show HTTP debug logs in Facter 4
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Facter / FACT-3047 Add option to show HTTP debug logs in Facter 4 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.400559.1621927319000.125419.1631109660035%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 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 (PUP-11170) User resource unable to remove user's home directory when set to absent in AIX
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-11170 User resource unable to remove user's home directory when set to absent in AIX 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.407149.1626453193000.94817.1627640040032%40Atlassian.JIRA.
Jira (PUP-11191) Remove Symbols “leaking” into serialized data
Title: Message Title Dorin Pleava created an issue Puppet / PUP-11191 Remove Symbols “leaking” into serialized data Issue Type: Bug Assignee: Unassigned Created: 2021/07/28 12:38 AM Priority: Normal Reporter: Dorin Pleava Symbols “leaking” into serialized data has been a long standing problem so pops serialization tries to be strict about what it will write out (only valid Data). The transaction logic should not serialize property values like :present as symbols. This is a pre-requisite for switching all of puppet’s data files to JSON in the future. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-10820) Binary, Sensitive, etc deferred results can corrupt the transaction store
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-10820 Binary, Sensitive, etc deferred results can corrupt the transaction store 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.380578.1607562201000.81021.1626255900056%40Atlassian.JIRA.
Jira (PUP-6802) Agent cannot compile catalog if it specifies an non-existent environment in puppet.conf even when the classifier is controlling environment
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-6802 Agent cannot compile catalog if it specifies an non-existent environment in puppet.conf even when the classifier is controlling environment Change By: Dorin Pleava Release Notes: Bug Fix Release Notes Summary: When an agent runs with a environment that does not exist on the server,puppet will fail.Now in case it cannot get the facts or catalog for the specifiedenvironment, it will fallback to the environment configured in thenew default_agent_environment puppet setting. 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.155674.1475855919000.80874.1626246960031%40Atlassian.JIRA.
Jira (PUP-6802) Agent cannot compile catalog if it specifies an non-existent environment in puppet.conf even when the classifier is controlling environment
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-6802 Agent cannot compile catalog if it specifies an non-existent environment in puppet.conf even when the classifier is controlling environment 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.155674.1475855919000.73398.1625476020039%40Atlassian.JIRA.
Jira (PUP-11137) Puppet cannot query non-ASCII users
Title: Message Title
Dorin Pleava created an issue
Puppet / PUP-11137
Puppet cannot query non-ASCII users
Issue Type:
Bug
Assignee:
Unassigned
Created:
2021/06/30 6:05 AM
Priority:
Normal
Reporter:
Dorin Pleava
On Debian 10(might be also other platforms affected) when querying a user that contains non-ASCII characters in its name, puppet errors out as seen below:
root@fell-scattergun:~# puppet --version
6.23.0
root@fell-scattergun:~# cat manifest.pp
user { 'Gérard':
ensure => present,
Jira (PUP-3317) Extend Package Source to include HTTP Urls (Windows)
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-3317 Extend Package Source to include HTTP Urls (Windows) 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.51963.1411137406000.57881.1623846480033%40Atlassian.JIRA.
Jira (FACT-3046) Facter 4 CLI does not accept concatenated short flags
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Facter / FACT-3046 Facter 4 CLI does not accept concatenated short flags 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.400395.1621841877000.45749.1622641440040%40Atlassian.JIRA.
Jira (FACT-3044) Add --version to --help output
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Facter / FACT-3044 Add --version to --help output 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.400018.1621535586000.44030.1622446920034%40Atlassian.JIRA.
Jira (FACT-2928) Error: Facter: statvfs() function failed: No such file or directory
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2928 Error: Facter: statvfs() function failed: No such file or directory Change By: Dorin Pleava Release Notes: Bug Fix Release Notes Summary: When a mountpoint file cannot be read, or is missing, it will throwan error, but will not specify what mountpoint/file has failed.Now, the error will show what file is caused the error. 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.385230.1611827086000.29663.162072337%40Atlassian.JIRA.
Jira (FACT-2928) Error: Facter: statvfs() function failed: No such file or directory
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Facter / FACT-2928 Error: Facter: statvfs() function failed: No such file or directory 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.385230.1611827086000.17077.1619178840036%40Atlassian.JIRA.
Jira (PUP-10844) Agent failures with server_list when one puppetserver fails
Title: Message Title Dorin Pleava commented on PUP-10844 Re: Agent failures with server_list when one puppetserver fails I think now I understand what the issue was: When puppet processes server_list and tries to find a functional server, it go through each server, and if it cannot connect it throws an error, but it still moves on to the next server in server_list. Now it only throws a warning for each server it cannot connect to, and if no server from server_list is functional, then it throws an error. [root@twin-federalism puppet]# puppet config print server_list full-maturation.delivery.puppetlabs.net,crash-leapfrog.delivery.puppetlabs.net [root@twin-federalism puppet]# puppet agent -t Warning: Unable to connect to server from server_list setting: Request to https://full-maturation.delivery.puppetlabs.net:8140/status/v1/simple/server failed after 0.002 seconds: Failed to open TCP connection to full-maturation.delivery.puppetlabs.net:8140 (Connection refused - connect(2) for "full-maturation.delivery.puppetlabs.net" port 8140) Trying with next server from server_list. Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts Info: Caching catalog for twin-federalism.delivery.puppetlabs.net Info: Applying configuration version '1618915174'
Jira (FACT-2960) Facter.conf doesn't accept in ttls singular form of time measure words
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2960 Facter.conf doesn't accept in ttls singular form of time measure words Change By: Dorin Pleava Fix Version/s: FACT 4.0.52 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.390508.1615369213000.164736.1615536960047%40Atlassian.JIRA.
Jira (FACT-2962) Facter 4 should accept the same time units in ttls (config file field) as Facter 3
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2962 Facter 4 should accept the same time units in ttls (config file field) as Facter 3 Change By: Dorin Pleava Fix Version/s: FACT 4.0.52 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.390510.1615373937000.164735.1615536900054%40Atlassian.JIRA.
Jira (FACT-2947) On SmartOS Facter tries to load an incompatible libsocket.so from a hardcoded path using ffi
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2947 On SmartOS Facter tries to load an incompatible libsocket.so from a hardcoded path using ffi Change By: Dorin Pleava Release Notes Summary: Description of the bug: Facter tries to load an incompatible (32-bit) libsocket.so from a hardcoded path using ffi and fails to retrieve networking facts.Description of the fix: The library name is preferred instead of the hardcoded absolute path and networking facts can be retrieved on SmartOS. Contributed by smokris. 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.388734.1614175924000.161919.1615368720032%40Atlassian.JIRA.
Jira (FACT-2134) Facter should distinguish between CentOS 8 and CentOS 8 Stream
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2134 Facter should distinguish between CentOS 8 and CentOS 8 Stream Change By: Dorin Pleava Fix Version/s: FACT 4.0.52 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.336204.1574351826000.160752.1615296120028%40Atlassian.JIRA.
Jira (FACT-2936) Facter::Core::Exectuion set $? test is failing on OSX and Solaris
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2936 Facter::Core::Exectuion set $? test is failing on OSX and Solaris Change By: Dorin Pleava Fix Version/s: FACT 4.0.52 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.386034.1612379676000.160747.1615294140029%40Atlassian.JIRA.
Jira (FACT-2926) Ensure all methods have rubydocs
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2926 Ensure all methods have rubydocs Change By: Dorin Pleava Fix Version/s: FACT 4.0.52 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.385100.1611738907000.160746.1615294080108%40Atlassian.JIRA.
Jira (FACT-2915) Break the linux networking resolver into multiple classes
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2915 Break the linux networking resolver into multiple classes Change By: Dorin Pleava Fix Version/s: FACT 4.0.52 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.383060.1610543877000.160745.1615294080051%40Atlassian.JIRA.
Jira (FACT-2952) Facter 4 reports lsbmajdistrelease on Ubuntu differently than facter 3
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2952 Facter 4 reports lsbmajdistrelease on Ubuntu differently than facter 3 Change By: Dorin Pleava Fix Version/s: FACT 4.0.52 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.389552.161471215.159413.1615213620039%40Atlassian.JIRA.
Jira (FACT-2950) Root of structured core facts cannot be overriden by a custom fact
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2950 Root of structured core facts cannot be overriden by a custom fact Change By: Dorin Pleava Fix Version/s: FACT 4.0.52 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.389257.1614583384000.159324.1615210080140%40Atlassian.JIRA.
Jira (FACT-1383) Azure Instance Metadata
Title: Message Title Dorin Pleava updated an issue Facter / FACT-1383 Azure Instance Metadata Change By: Dorin Pleava Fix Version/s: FACT 4.0.52 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.125281.1459963292000.159318.1615209420033%40Atlassian.JIRA.
Jira (PUP-10943) Windows package provider continues to read DisplayVersion key after embedded NULL
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-10943 Windows package provider continues to read DisplayVersion key after embedded NULL Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.388985.1614292739000.156008.1614777840283%40Atlassian.JIRA.
Jira (FACT-2952) Facter 4 reports lsbmajdistrelease on Ubuntu differently than facter 3
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Facter / FACT-2952 Facter 4 reports lsbmajdistrelease on Ubuntu differently than facter 3 Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389552.161471215.156006.1614777840194%40Atlassian.JIRA.
Jira (FACT-2952) Facter 4 reports lsbmajdistrelease on Ubuntu differently than facter 3
Title: Message Title Dorin Pleava assigned an issue to Unassigned Facter / FACT-2952 Facter 4 reports lsbmajdistrelease on Ubuntu differently than facter 3 Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389552.161471215.156007.1614777840239%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN network interfaces
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network for VirtualBox or VPN network interfaces Change By: Dorin Pleava Acceptance Criteria: When connected to a VPN, running `facter network networking.interfaces ` with facter 3, i I get a different network on VirtualBox interfaces than running the same command with facter 4. I assume facter 3 output is incorrect as `facter networking. interfaces.vboxnet0. ip` matches the `facter networking.interfaces.vboxnet0. network`. `facter networking.interfaces.vboxnet0. 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.154683.1614673860041%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN network interfaces
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network for VirtualBox or VPN network interfaces Change By: Dorin Pleava On OSX(could be on other platforms as-well), when connected to a VPN, Facter 3 shows network incorrect. This can also be reprFacter 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-20-42-413.png|width=222,height=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-21-03-365.png|width=285,height=149!I think facter 3 cannot read the vboxnet0 netmask using `ipconfig getoption vboxnet0 server_identifier` so it cannot calculate the network. Also, when connected to a VPN, Facter 3 shows network incorrect.Facter 3 gets the network informations form here [https://github.com/puppetlabs/facter/blob/3.x/lib/src/facts/bsd/networking_resolver.cc#L29] but the netmask data for VPN interfaces and VirtualBox comes empty.Facter 4 relies on `ifconfig` command and it works as expected. Add Comment
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN network interfaces
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network for VirtualBox or VPN network interfaces Change By: Dorin Pleava Summary: Facter 3 bad network for VirtualBox or VPN network interfaces 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.154681.1614673080100%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN interfaces
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network for VirtualBox or VPN interfaces Change By: Dorin Pleava Summary: Facter 3 bad network forVirtualBox or VPN interfaces 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.154679.1614672840080%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network for
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network for Change By: Dorin Pleava Summary: Facter 3 bad network when connected to a VPN for 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.154678.1614672840056%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN interfaces
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network for VirtualBox or VPN interfaces Change By: Dorin Pleava On OSX(could be on other platforms as-well), when connected to a VPN, Facter 3 shows network incorrect. This can also be repr 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-20-42-413.png|width=222,height=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-21-03-365.png|width=285,height=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 for VirtualBox or VPN network interfaces
Title: Message Title Dorin Pleava commented on FACT-2951 Re: Facter 3 bad network for VirtualBox or VPN network interfaces Claire Cadman I think this issue can be marked as a known issue for the moment. 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.154685.1614674520024%40Atlassian.JIRA.
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN network interfaces
Title: Message Title
Dorin Pleava updated an issue
Facter / FACT-2951
Facter 3 bad network for VirtualBox or VPN network interfaces
Change By:
Dorin Pleava
When running `facter networking.interfaces` with facter 3, I get a different network on VirtualBox interfaces than running the same command with facter 4. This bug requires the following configuration in 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-20-42-413.png|width=222,height=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-21-03-365.png|width=285,height=149!This bug also reproduces when connected to a VPN, and comparing network interfaces used for VPN connection (utun0, utun1 ...).I think facter 3 gets the network informations form [https://github.com/puppetlabs/facter/blob/3.x/lib/src/facts/bsd/networking_resolver.cc#L29] but the netmask data for VPN interfaces and VirtualBox are empty. Facter 4 relies on `ifconfig` command and it works as expected. {code:java} % puppet facts diff | jq{ "network_vboxnet0": { "new_value": "192.168.99.0", "old_value": "192.168.99.1" }, "networking.interfaces.vboxnet0.bindings.0.network": { "new_value": "192.168.99.0", "old_value": "192.168.99.1" }, "networking.interfaces.vboxnet0.network": { "new_value": "192.168.99.0", "old_value": "192.168.99.1"}{code}
Add Comment
Jira (FACT-2951) Facter 3 bad network for VirtualBox or VPN network interfaces
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2951 Facter 3 bad network for VirtualBox or VPN network interfaces Change By: Dorin Pleava The bug can be recreated without a VPN When running `facter networking.interfaces` with facter 3 , by using I get a different network on VirtualBox interfaces than running the same command with facter 4. This bug requires the following configuration in 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-20-42-413.png|width=222,height=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-21-03-365.png|width=285,height=149! I think facter 3 cannot read the vboxnet0 netmask using `ipconfig getoption vboxnet0 server_identifier` so it cannot calculate the network.Also, This bug also reproduces when connected to a VPN, Facter 3 shows and comparing network incorrect interfaces used for VPN connection (utun0, utun1 . ..). Facter I think facter 3 gets the network informations form here [https://github.com/puppetlabs/facter/blob/3.x/lib/src/facts/bsd/networking_resolver.cc#L29] but the netmask data for VPN interfaces and VirtualBox comes are empty. Facter 4 relies on `ifconfig` command and it works as expected. Add Comment This message was sent by
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-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-2940) puppet facts diff shows inconsistent networking values on macOS
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Facter / FACT-2940 puppet facts diff shows inconsistent networking values on macOS Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387708.1613500315000.149030.1614067680030%40Atlassian.JIRA.
Jira (FACT-2936) Facter::Core::Exectuion set $? test is failing on OSX and Solaris
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Facter / FACT-2936 Facter::Core::Exectuion set $? test is failing on OSX and Solaris Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.386034.1612379676000.133058.1612436580044%40Atlassian.JIRA.
Jira (FACT-2918) FACTER_ environmental facts overrides don't work with external facts
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2918 FACTER_ environmental facts overrides don't work with external facts Change By: Dorin Pleava Release Notes: Bug Fix Release Notes Summary: When running puppet facts, environment facts were overwrittenby external facts.Now the flow was set to default facts -> external facts -> environment facts 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.383195.1610609261000.131797.1612357320283%40Atlassian.JIRA.
Jira (FACT-2918) FACTER_ environmental facts overrides don't work with external facts
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Facter / FACT-2918 FACTER_ environmental facts overrides don't work with external facts Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.383195.1610609261000.127117.1611820620040%40Atlassian.JIRA.
Jira (PUP-10844) Agent failures with server_list when one puppetserver fails
Title: Message Title Dorin Pleava commented on PUP-10844 Re: Agent failures with server_list when one puppetserver fails After some digging around on versions 5.5 21, 6.13.0, 6.14.0 and the newly released 6.20.0, only 6.14.0 did some things different. On 6.14.0, when a server failed midrun, the current running part would fail (like Retrieving pluginfacts, or Retrieving facts) and the code would continue to the next part(Retrieving locales) where it would check again for an available server, choosing the next functional server from server_list. I think this is not the intended functionality, as it could cause some sort of mix between catalogs from different servers. [root@blue-bumper ~]# puppet --version 6.14.0 [root@blue-bumper ~]# puppet agent -t --debug ... Debug: Creating new connection for https://past-medication.delivery.puppetlabs.net:8140 Debug: Starting connection for https://past-medication.delivery.puppetlabs.net:8140 Error: Could not retrieve catalog from remote server: Request to https://past-medication.delivery.puppetlabs.net:8140/puppet/v3/catalog/blue-bumper.delivery.puppetlabs.net?environment=production failed after 0.001 seconds: Failed to open TCP connection to past-medication.delivery.puppetlabs.net:8140 (Connection refused - connect(2) for "past-medication.delivery.puppetlabs.net" port 8140) Wrapped exception: Failed to open TCP connection to past-medication.delivery.puppetlabs.net:8140 (Connection refused - connect(2) for "past-medication.delivery.puppetlabs.net" port 8140)
Jira (PUP-10844) Agent failures with server_list when one puppetserver fails
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-10844 Agent failures with server_list when one puppetserver fails Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.381638.1608653215000.111680.1610376300184%40Atlassian.JIRA.
Jira (PUP-10815) When upgrading to Puppet 7, the Puppet-Agent module should check if there are diffs between facters
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-10815 When upgrading to Puppet 7, the Puppet-Agent module should check if there are diffs between facters Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.380233.1607442379000.108818.1609935900064%40Atlassian.JIRA.
Jira (PUP-10773) Add a server alias for routes.yaml
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-10773 Add a server alias for routes.yaml Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.376905.1604419718000.90532.1606994400036%40Atlassian.JIRA.
Jira (PUP-10247) Support ruby 2.7
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-10247 Support ruby 2.7 Change By: Dorin Pleava Release Notes: New Feature Not Needed Release Notes Summary: Puppet 7 supports version Ruby 2.7, which was released in December 2019 and it brings new features and performance improvements. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342962.1579675679000.72624.1604568720027%40Atlassian.JIRA.
Jira (PUP-10247) Support ruby 2.7
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-10247 Support ruby 2.7 Change By: Dorin Pleava Release Notes: New Feature Release Notes Summary: Puppet 7 supports version Ruby 2.7, which was released in December 2019 and it brings new features and performance improvements. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.342962.1579675679000.72623.1604568660037%40Atlassian.JIRA.
Jira (PUP-9262) Remove fine grained file and environment timeouts
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-9262 Remove fine grained file and environment timeouts Change By: Dorin Pleava Fix Version/s: PUP 7.0.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.282027.1540333474000.72611.1604567760035%40Atlassian.JIRA.
Jira (PUP-10597) Remove deprecated held from apt provider
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-10597 Remove deprecated held from apt provider Change By: Dorin Pleava Fix Version/s: PUP 7.0.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.366877.1595415005000.72610.1604567280085%40Atlassian.JIRA.
Jira (PUP-10590) Remove win32-process gem dependency from packaging
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-10590 Remove win32-process gem dependency from packaging Change By: Dorin Pleava Fix Version/s: PUP 7.0.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.366765.1595340784000.72603.1604567100027%40Atlassian.JIRA.
Jira (PUP-10488) Remove deprecated method from Puppet::Provider::NameService
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-10488 Remove deprecated method from Puppet::Provider::NameService Change By: Dorin Pleava Fix Version/s: PUP 7.0.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.357606.1588681832000.72594.1604566680215%40Atlassian.JIRA.
Jira (PUP-10489) Remove deprecated method from DirectoryService
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-10489 Remove deprecated method from DirectoryService Change By: Dorin Pleava Fix Version/s: PUP 7.0.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.357608.1588683093000.72596.1604566680303%40Atlassian.JIRA.
Jira (PUP-10487) Remove deprecated methods from TypeCalculator
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-10487 Remove deprecated methods from TypeCalculator Change By: Dorin Pleava Fix Version/s: PUP 7.0.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.357605.1588681679000.72590.1604566620140%40Atlassian.JIRA.
Jira (PUP-10486) Remove deprecated Enumeration type
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-10486 Remove deprecated Enumeration type Change By: Dorin Pleava Fix Version/s: PUP 7.0.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.357604.1588681414000.72587.1604566560027%40Atlassian.JIRA.
Jira (PUP-10712) Provide a JSON terminus for node and report
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-10712 Provide a JSON terminus for node and report Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374770.1602599183000.55414.1602675720030%40Atlassian.JIRA.
Jira (PUP-10669) Create "server" section and add alias
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-10669 Create "server" section and add alias Change By: Dorin Pleava Release Notes: New Feature Release Notes Summary: As master section is replaced with server section, for nowmaster section is still allowed in puppet.conf, but whenadding/updating a setting from the master section, the actionwill be done on the server section instead, and the setting from [master]will be removed. 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.372040.1600212479000.55261.1602659640028%40Atlassian.JIRA.
Jira (PUP-10710) Disable setting invalid sections in puppet.conf
Title: Message Title Dorin Pleava created an issue Puppet / PUP-10710 Disable setting invalid sections in puppet.conf Issue Type: Bug Affects Versions: PUP 6.18.0 Assignee: Unassigned Created: 2020/10/08 3:10 AM Priority: Normal Reporter: Dorin Pleava Puppet Version: 6.18.0 Puppet Server Version: N/A OS Name/Version: RedHat 8 Puppet does not reject setting an invalid section in puppet.conf via the set command. As the invalid section will be written into puppet.conf, the next time puppet.conf gets parsed, an error will be shown. root@unlikely-beggar ~# puppet config set random213 --section random4212 root@unlikely-beggar ~# cat /etc/puppetlabs/puppet/puppet.conf [random4212] random213 = root@unlikely-beggar ~# puppet config print server Error: Could not parse /etc/puppetlabs/puppet/puppet.conf: Illegal section 'random4212' in config file at (file: /etc/puppetlabs/puppet/puppet.conf, line: 1). The only valid puppet.conf sections are: [main, master, agent, user, server]. Please use the directory environments feature to specify environments. (See https://puppet.com/docs/puppet/latest/environments_about.html) puppet Desired Behavior: Do not allow setting of invalid sections in puppet.conf Actual Behavior: Setting of invalid sections in puppet.conf works only on the first try
Jira (PUP-10669) Create "server" section and add alias
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-10669 Create "server" section and add alias Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.372040.1600212479000.48605.1601906820028%40Atlassian.JIRA.
Jira (PUP-8682) Allow disabling settings catalog
Title: Message Title Dorin Pleava assigned an issue to Unassigned Puppet / PUP-8682 Allow disabling settings catalog Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.248061.1525111785000.45065.1601364840032%40Atlassian.JIRA.
Jira (PUP-8682) Allow disabling settings catalog
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-8682 Allow disabling settings catalog Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.248061.1525111785000.43104.1601037600026%40Atlassian.JIRA.
Jira (PUP-10658) Puppet service ps parsing using too loose regex
Title: Message Title
Dorin Pleava commented on PUP-10658
Re: Puppet service ps parsing using too loose regex
Hi Tim Meusel, Indeed the regex seems a bit loose, but changing the ensure regex to have an exact match may have breaking changes. I recommend using the pattern attribute, where you can place an exact regex to match the 'ps -ef' result, like: service { 'bird': ensure => 'running', enable => true, hasstatus => false, pattern => '*bird/s*' }
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.371182.1599213891000.37089.1600256700053%40Atlassian.JIRA.
Jira (PUP-10658) Puppet service ps parsing using too loose regex
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-10658 Puppet service ps parsing using too loose regex Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371182.1599213891000.36086.1600160340032%40Atlassian.JIRA.
Jira (FACT-2688) Investigate promotion of Facter 4 in puppet-agent
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2688 Investigate promotion of Facter 4 in puppet-agent Change By: Dorin Pleava Fix Version/s: FACT 3.14.13 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.364431.1593503092000.19021.1597843980026%40Atlassian.JIRA.
Jira (FACT-2738) Write acceptance test that compares Facter 3 and Facter 4 output
Title: Message Title Dorin Pleava updated an issue Facter / FACT-2738 Write acceptance test that compares Facter 3 and Facter 4 output Change By: Dorin Pleava Fix Version/s: FACT 3.14.13 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.368321.1596632393000.19020.1597843860133%40Atlassian.JIRA.
Jira (PUP-7446) Remove win32-service gem dependency from packaging
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-7446 Remove win32-service gem dependency from packaging Change By: Dorin Pleava Fix Version/s: PUP 6.18.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.185591.149201969.19017.1597843020026%40Atlassian.JIRA.
Jira (PUP-10590) Remove win32-process gem dependency from packaging
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-10590 Remove win32-process gem dependency from packaging Change By: Dorin Pleava Fix Version/s: PUP 6.18.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.366765.1595340784000.19016.1597842960038%40Atlassian.JIRA.
Jira (PUP-6631) Apt package provider does not mark managed packages as manual
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-6631 Apt package provider does not mark managed packages as manual Change By: Dorin Pleava Fix Version/s: PUP 6.18.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.147758.1471514773000.18986.1597841820139%40Atlassian.JIRA.
Jira (PUP-2608) An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory.
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-2608 An error is logged during an agent run if the puppetmaster does not have at least one /lib dir in its modules directory. Change By: Dorin Pleava Fix Version/s: PUP 6.18.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.35962.1400279607000.18983.1597841520028%40Atlassian.JIRA.
Jira (PUP-10615) Add facts and vars back to PAL ScriptCompiler scope
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-10615 Add facts and vars back to PAL ScriptCompiler scope Change By: Dorin Pleava Fix Version/s: PUP 6.18.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.368742.1597093035000.18982.1597841460125%40Atlassian.JIRA.
Jira (PUP-10600) Allow running puppet commands via AWS Session Manager on Windows Server 2019
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-10600 Allow running puppet commands via AWS Session Manager on Windows Server 2019 Change By: Dorin Pleava Fix Version/s: PUP 6.18.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.367242.1595613997000.18979.1597841400035%40Atlassian.JIRA.
Jira (PUP-10587) Add plan_hierarchy key to hiera config
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-10587 Add plan_hierarchy key to hiera config Change By: Dorin Pleava Fix Version/s: PUP 6.18.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.366423.1594943799000.18977.1597841100050%40Atlassian.JIRA.
Jira (PUP-10599) Puppet lookup on remote nodes should skip loading local external facts
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-10599 Puppet lookup on remote nodes should skip loading local external facts Change By: Dorin Pleava Fix Version/s: PUP 6.18.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.367118.1595504611000.18978.1597841100101%40Atlassian.JIRA.
