Jira (FACT-2923) Domain on Windows should be retrieved priority from registry
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2923 Domain on Windows should be retrieved priority from registry Change By: Mihai Buzgau Team: Ghost Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.383584.1611067536000.119142.1611128940044%40Atlassian.JIRA.
Jira (FACT-2923) Domain on Windows should be retrieved priority from registry
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2923 Domain on Windows should be retrieved priority from registry Change By: Mihai Buzgau Sprint: NW - 2021-02-03 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.383584.1611067536000.119143.1611128940061%40Atlassian.JIRA.
Jira (PUP-10850) Puppet facts show doesn't have an option to opt out of legacy facts
Title: Message Title Oana Tanasoiu commented on PUP-10850 Re: Puppet facts show doesn't have an option to opt out of legacy facts Hi Josh Cooper, We decided that is better to restore the behaviour as it was initially made. By default puppet facts show doesn't display legacy facts and the application has an opt-in mechanism for puppet facts through --show-legacy flag. 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.382858.1610379246000.119141.1611128160092%40Atlassian.JIRA.
Jira (PUP-10837) Send release announcement (Puppet Platform 7.2.0)
Title: Message Title Morgan Rhodes assigned an issue to Jacklyn Kinsler Puppet / PUP-10837 Send release announcement (Puppet Platform 7.2.0) Change By: Morgan Rhodes Assignee: Morgan Rhodes Jacklyn Kinsler 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.381195.1608148467000.119039.1611106620030%40Atlassian.JIRA.
Jira (PUP-10769) Send release announcement (Puppet Platform 6.20.0)
Title: Message Title Morgan Rhodes assigned an issue to Jacklyn Kinsler Puppet / PUP-10769 Send release announcement (Puppet Platform 6.20.0) Change By: Morgan Rhodes Assignee: Morgan Rhodes Jacklyn Kinsler 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.376695.1604093647000.119033.1611106440038%40Atlassian.JIRA.
Jira (PUP-10850) Puppet facts show doesn't have an option to opt out of legacy facts
Title: Message Title Josh Cooper commented on PUP-10850 Re: Puppet facts show doesn't have an option to opt out of legacy facts Hi Oana Tanasoiu this doesn't seem to be working as expected. Using puppet 7.3.0, the --no-legacy option is rejected: $ git rev-parse HEAD 3d4df020ea74ca5695e03229fa1279adf0dda3fa $ bx puppet facts show --no-legacy | jq . Error: Could not parse application options: invalid option: --no-legacy It looks like https://github.com/puppetlabs/puppet/pull/8475 was merged first in https://github.com/puppetlabs/puppet/commit/49918bd5cc17a93bba14d2b9a94b44848fdb7b4d which added --no-legacy, but it accidentally removed --show-legacy. The change to --show-legacy broke other applications that call puppet facts show. So https://github.com/puppetlabs/puppet/pull/8478 restored --show-legacy and that was merged in https://github.com/puppetlabs/puppet/commit/a600c40f32cfbcf77d58ae19f62ff5710a7fe940. Using that version --show-legacy and --no-legacy are both accepted, but the latter doesn't omit legacy facts: $ bx puppet facts show | jq .virtual "physical" $ bx puppet facts show --no-legacy | jq .virtual "physical" Then https://github.com/puppetlabs/puppet/pull/8482 was merged, which removed the
Jira (FACT-2918) FACTER_ environmental facts overrides don't work with external facts
Title: Message Title Kenneth Pepiton commented on FACT-2918 Re: FACTER_ environmental facts overrides don't work with external facts There are two major problems with this response: 1) This was previously working and is no longer working 2) The exact use case is in the example. The need to override the fact values while testing the agent allows for an alternative for testing. I am very sadly disappointed in this type of response 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.118548.1611085440107%40Atlassian.JIRA.
Jira (FACT-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Tom Parker updated an issue Facter / FACT-2924 Facter fails "closed" if the facter.conf file is invalid Change By: Tom Parker With facter 4 shipped with puppet 7.1 is if the facter.conf file is invalid facter fails to load at all which prevents all subsequent puppet runs. This means that instead of being able to fix the problem with a puppet run the administrator has to login to any affected server and fix the file by hand. Would it be possible to fail "open" if the file is invalid? Log an error and run with all defaults? This would at least allow puppet to fix the problem on a subsequent run. 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-2924) Facter fails "closed" if the facter.conf file is invalid
Title: Message Title Tom Parker created an issue Facter / FACT-2924 Facter fails "closed" if the facter.conf file is invalid Issue Type: Bug Assignee: Unassigned Created: 2021/01/19 11:03 AM Priority: Normal Reporter: Tom Parker With facter 4 shipped with puppet 7.1 is the facter.conf file is invalid facter fails to load at all which prevents all subsequent puppet runs. This means that instead of being able to fix the problem with a puppet run the administrator has to login to any affected server and fix the file by hand. Would it be possible to fail "open" if the file is invalid? Log an error and run with all defaults? This would at least allow puppet to fix the problem on a subsequent run. Add Comment
Jira (PUP-10855) Need to inject loaders when retrieving a catalog via Puppet::Resource::Catalog
Title: Message Title Nacho Barrientos commented on PUP-10855 Re: Need to inject loaders when retrieving a catalog via Puppet::Resource::Catalog Thanks for confirming the loaders bit and for the hint about the catalog retrieval. 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.383328.1610703917000.118120.1611075840184%40Atlassian.JIRA.
Jira (PUP-10857) User resource with forcelocal uses getent for groups
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10857 User resource with forcelocal uses getent for groups Change By: Mihai Buzgau Sprint: NW - 2021-02-03 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.383586.1611070494000.117992.1611073920028%40Atlassian.JIRA.
Jira (PUP-10855) Need to inject loaders when retrieving a catalog via Puppet::Resource::Catalog
Title: Message Title Josh Cooper commented on PUP-10855 Re: Need to inject loaders when retrieving a catalog via Puppet::Resource::Catalog Since this is expected behavior, I'm going to close this. Feel free to reach out in #puppet-dev in slack if you have questions. 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.383328.1610703917000.117986.1611073740575%40Atlassian.JIRA.
Jira (PUP-10853) When blocking legacy facts in puppet7, puppet agent run fails to fetch 'operatingsystem' fact
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10853 When blocking legacy facts in puppet7, puppet agent run fails to fetch 'operatingsystem' fact Change By: Mihai Buzgau Sprint: NW - 2021-02-03 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.117932.1611072180030%40Atlassian.JIRA.
Jira (FACT-2922) Add --timing to puppet facts show
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2922 Add --timing to puppet facts show Change By: Mihai Buzgau Sprint: NW - 2021-02-03 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.383413.1610735312000.117929.1611072000348%40Atlassian.JIRA.
Jira (FACT-2922) Add --timing to puppet facts show
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2922 Add --timing to puppet facts show Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.383413.1610735312000.117928.1611072000302%40Atlassian.JIRA.
Jira (FACT-2921) LinuxMint Tessa not recognized, destroys services
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2921 LinuxMint Tessa not recognized, destroys services Change By: Mihai Buzgau Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.383388.1610724788000.117923.1611071940128%40Atlassian.JIRA.
Jira (FACT-2921) LinuxMint Tessa not recognized, destroys services
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2921 LinuxMint Tessa not recognized, destroys services Change By: Mihai Buzgau Sprint: NW - 2021-02-03 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.383388.1610724788000.117920.1611071880417%40Atlassian.JIRA.
Jira (PUP-10856) Slower puppet agent run after agent upgrade to version 6
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10856 Slower puppet agent run after agent upgrade to version 6 Change By: Mihai Buzgau Sprint: NW - 2021-02-03 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.383327.1610697413000.117896.1611071520030%40Atlassian.JIRA.
Jira (PUP-10854) apt provider does not work with local packages
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10854 apt provider does not work with local packages Change By: Mihai Buzgau Sprint: ready for triage NW - 2021-02-03 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.383202.1610630264000.117893.1611071460041%40Atlassian.JIRA.
Jira (PUP-10843) Module tool should check for Forge modules compatibility with running versions of Puppet and Facter
Title: Message Title Josh Cooper commented on PUP-10843 Re: Module tool should check for Forge modules compatibility with running versions of Puppet and Facter provide the user useful feedback if they attempt to install a module that's incompatible with their environment I'm not sure how this would work in cases where the agent OS isn't the same as the server OS, especially as we only have a few supported server platforms. For example, installing the puppetlabs-powershell module for Windows hosts on a RedHat puppetserver. 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.21269.1387189431000.117894.1611071460088%40Atlassian.JIRA.
Jira (FACT-2918) FACTER_ environmental facts overrides don't work with external facts
Title: Message Title Nick Walker commented on FACT-2918 Re: FACTER_ environmental facts overrides don't work with external facts While this is inconsistent behavior... it's unclear what use case makes this a problem over just setting an external fact in a file. The recommendation is just to set the external fact in a file to get it to show in the puppet run. We don't intend to fix this as when running from the puppet daemon setting facts from environment variables is likely not an expected use case. 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.117883.1611071280252%40Atlassian.JIRA.
Jira (FACT-2882) Facter 4.0.x on Windows does not return the domain when set in the registry
Title: Message Title Valters Jansons commented on FACT-2882 Re: Facter 4.0.x on Windows does not return the domain when set in the registry Oana Tanasoiu, thank you. I filled the ticket details for you and anyone else stumbling upon it there, to detail the case. 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.379598.1606874598000.117878.1611071160072%40Atlassian.JIRA.
Jira (FACT-2923) Domain on Windows should be retrieved priority from registry
Title: Message Title Valters Jansons updated an issue Facter / FACT-2923 Domain on Windows should be retrieved priority from registry Change By: Valters Jansons Component/s: Facter 4 Affects Version/s: FACT 4.0.48 Facter 4.0.48 (in [Pull Request 2245|https://github.com/puppetlabs/facter/pull/2245]) resolved a regression in gem-based Facter 4.0.x that did not check for domain name in registry on Windows machines (filed as FACT-2882).This resolution however prioritizes network interface domain names in favor of the registry information. Puppet 6 and Facter 3 prioritized the registry entries, so this is a regression (or at least, a notable change in behavior).This is important for domain-joined machines, which store their domain name information in the registry. They may have a network interface with a different domain name received over DHCP, which may be hard to remove depending on the networking circumstances. For these machines where both network adapters have a domain name, and the registry has a domain name, if there is a mismatch, the argument is that the registry is a more safe option to default to. Add Comment
Jira (PUP-10857) User resource with forcelocal uses getent for groups
Title: Message Title zendesk.jira updated an issue Puppet / PUP-10857 User resource with forcelocal uses getent for groups Change By: zendesk.jira Labels: jira_escalated Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.383586.1611070494000.117839.1611070560231%40Atlassian.JIRA.
Jira (PUP-10857) User resource with forcelocal uses getent for groups
Title: Message Title zendesk.jira updated an issue Puppet / PUP-10857 User resource with forcelocal uses getent for groups Change By: zendesk.jira Zendesk Ticket Count: 1 Zendesk Ticket IDs: 42710 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.383586.1611070494000.117838.1611070560187%40Atlassian.JIRA.
Jira (PUP-10857) User resource with forcelocal uses getent for groups
Title: Message Title Jarret Lavallee created an issue Puppet / PUP-10857 User resource with forcelocal uses getent for groups Issue Type: Improvement Affects Versions: PUP 6.19.1 Assignee: Unassigned Components: Types and Providers Created: 2021/01/19 7:34 AM Priority: Normal Reporter: Jarret Lavallee *Description* When using the useradd provider with the user resource with forcelocal => true, the groups are still pulled from gentent. This causes LDAP/NIS groups to be detected instead of just the local groups. *Desired Behavior* The forcelocal => true parameter should force all options to be local. With the parameter set, the user is looked up from /etc/passwd. The groups should be looked up locally as well. *Actual Behavior* The forcelocal => true results in the user being looked up locally, but the groups are looked up through getgrent *Additional Notes* It falls back to using https://github.com/puppetlabs/puppet/blob/main/lib/puppet/util/posix.rb#L14-L33 from https://github.com/puppetlabs/puppet/blob/main/lib/puppet/provider/nameservice.rb#L235-L237 as it is not implemented in https://github.com/puppetlabs/puppet/blob/main/lib/puppet/provider/user/useradd.rb
Jira (FACT-2882) Facter 4.0.x on Windows does not return the domain when set in the registry
Title: Message Title Oana Tanasoiu commented on FACT-2882 Re: Facter 4.0.x on Windows does not return the domain when set in the registry Valters Jansons you are right. I opened a ticket for this https://tickets.puppetlabs.com/browse/FACT-2923 . 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.379598.1606874598000.117792.1611067620167%40Atlassian.JIRA.
Jira (FACT-2923) Domain on Windows should be retrieved priority from registry
Title: Message Title Oana Tanasoiu created an issue Facter / FACT-2923 Domain on Windows should be retrieved priority from registry Issue Type: Bug Assignee: Oana Tanasoiu Created: 2021/01/19 6:45 AM Priority: Normal Reporter: 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
Jira (FACT-2882) Facter 4.0.x on Windows does not return the domain when set in the registry
Title: Message Title Valters Jansons commented on FACT-2882 Re: Facter 4.0.x on Windows does not return the domain when set in the registry Oana Tanasoiu, doesn't this then introduce a kind of a regression compared to Puppet 6 with Facter 3? Shortly, in Puppet 6 it prioritized the user-configured (registry) domain name in favor of the network interface domain. Why this matters is that the registry domain key comes from actions such as joining the computer to a domain. In combination of us having various computers where they have a different domain name coming in from DHCP, that we cannot easily remove as of now, the fix provided will result in that regression blocking us from upgrading, unless I am misreading this. 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.379598.1606874598000.117744.1611061920084%40Atlassian.JIRA.
Jira (FACT-2918) FACTER_ environmental facts overrides don't work with external facts
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2918 FACTER_ environmental facts overrides don't work with external facts Change By: Mihai Buzgau Sprint: NW - 2021-02-03 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.117687.1611054180035%40Atlassian.JIRA.
