Jira (PUP-11375) Cannot ensure user absent and purge its ssh keys in same manifest
Title: Message Title
Luchian Nemes created an issue
Puppet / PUP-11375
Cannot ensure user absent and purge its ssh keys in same manifest
Issue Type:
Bug
Assignee:
Unassigned
Created:
2021/12/09 6:44 AM
Priority:
Normal
Reporter:
Luchian Nemes
How to reproduce:
➜ cat create_user.pp
user {'luchi':
ensure => present,
managehome => true,
purge_ssh_keys => true
}
➜ cat add_ssh_key.pp
Jira (PUP-11320) Regression on user resource
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-11320 Regression on user resource Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: This release moves the `ssh_authorized_key` resources creation moment at the end of the user type flow, after all user properties and parameters were resolved to avoid order dependency errors. 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.419684.1634300951000.20117.1638779640039%40Atlassian.JIRA.
Jira (PUP-4045) Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-4045 Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: This release allows Puppet to retrieve attributes for `fifo` and `socket` files and manage them when given manifest has a `file` resource which is recursing over a given path. 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.20098.1638779400195%40Atlassian.JIRA.
Jira (PUP-4045) Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-4045 Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.69478.1424944721000.9335.1637156520190%40Atlassian.JIRA.
Jira (PUP-1460) Puppet hangs trying to replace a FIFO
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-1460 Puppet hangs trying to replace a FIFO Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.23952.1389949607000.8207.1637060280040%40Atlassian.JIRA.
Jira (PUP-11320) Regression on user resource
Title: Message Title Luchian Nemes commented on PUP-11320 Re: Regression on user resource Franck Jouvanceau could you please detail the use case in the original manifest that surfaced this error to better understand the end goal? 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.419684.1634300951000.1011.1636383120038%40Atlassian.JIRA.
Jira (PUP-11320) Regression on user resource
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-11320 Regression on user resource Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.419684.1634300951000.168992.1635934440097%40Atlassian.JIRA.
Jira (PUP-11204) puppet lookup --facts {filename} fails if filename does not contain a dot
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-11204
puppet lookup --facts {filename} fails if filename does not contain a dot
Change By:
Luchian Nemes
Release Notes:
Bug Fix
Release Notes Summary:
Before this release, `puppet lookup --facts {filename}` failed early when the filename given did not contain a dot. This fix removes the early extensions check and adds a fallback instead — tries both formats (JSON then YAML) to read the given facts file when its path doesn't end with any of the expected extensions (yaml/yml/json). Otherwise, it follows previous implementation and respects given extension.
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
Jira (FACT-3068) Facter timezone utf8 problem
Title: Message Title Luchian Nemes updated an issue Facter / FACT-3068 Facter timezone utf8 problem Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: This release adds a new `timezone` resolver specific to Windows which checks the system codepage and uses it for encoding the timezone fact to avoid unwanted characters on non-English OS. 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.413598.1630064252000.166792.1635772680063%40Atlassian.JIRA.
Jira (FACT-3074) '--log-level none' throws exception
Title: Message Title Luchian Nemes updated an issue Facter / FACT-3074 '--log-level none' throws exception Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: Before this release, Facter 4 did not accept `none` as a log level even though it was supported as per `--help` output. This fix aligns the behaviour with Facter 3 by accepting `none` as log level. 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.415852.1631779051000.166790.1635772560050%40Atlassian.JIRA.
Jira (FACT-3074) '--log-level none' throws exception
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Facter / FACT-3074 '--log-level none' throws exception Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.415852.1631779051000.159256.1634723460076%40Atlassian.JIRA.
Jira (PUP-11319) Updated puppet gem and rspec-puppet Failures
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-11319 Updated puppet gem and rspec-puppet Failures Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: This release moves the `DEFAULT_TIMEOUT` constant from `lib/puppet/util/windows/service.rb` to `lib/puppet/util/windows.rb` in an non-OS specifically guarded code area. This avoids `uninitialized constant` errors when compiling catalogs on non-Windows operating systems. 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.419463.1634134581000.156138.1634295240044%40Atlassian.JIRA.
Jira (PUP-11319) Updated puppet gem and rspec-puppet Failures
Title: Message Title Luchian Nemes moved an issue Puppet / PUP-11319 Updated puppet gem and rspec-puppet Failures Change By: Luchian Nemes Key: PA PUP - 4082 11319 Affects Version/s: puppet-agent 7.12.0 Affects Version/s: PUP 7.12.0 Project: Puppet Agent 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
Jira (PUP-11204) puppet lookup --facts {filename} fails if filename does not contain a dot
Title: Message Title
Luchian Nemes assigned an issue to Luchian Nemes
Puppet / PUP-11204
puppet lookup --facts {filename} fails if filename does not contain a dot
Change By:
Luchian Nemes
Assignee:
Luchian Nemes
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.411148.1628520098000.148148.1633511280029%40Atlassian.JIRA.
Jira (FACT-3068) Facter timezone utf8 problem
Title: Message Title Luchian Nemes updated an issue Facter / FACT-3068 Facter timezone utf8 problem Change By: Luchian Nemes Attachment: image-2021-10-01-16-49-51-786.png Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.413598.1630064252000.144848.1633096200033%40Atlassian.JIRA.
Jira (FACT-3075) Windows 2022 is detected as Windows 2019
Title: Message Title Luchian Nemes updated an issue Facter / FACT-3075 Windows 2022 is detected as Windows 2019 Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: This fix allows the `os.release.full` and `os.release.major` to correctly detect Windows 2022 and output `2022` instead of `2019` as before. 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.416781.1632314698000.144635.1633076520032%40Atlassian.JIRA.
Jira (FACT-3058) Add DisplayVersion fact for Windows machines
Title: Message Title Luchian Nemes updated an issue Facter / FACT-3058 Add DisplayVersion fact for Windows machines Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: The original source of information for the `os.windows.release_id` fact hasn't been updated for a while and this release fixes it by querying the right (new) registry key when it's available. This also adds a new fact called `os.windows.display_version` which in the next major release of Facter will replace `os.windows.release_id`. 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.408768.1627470358000.144626.1633076280036%40Atlassian.JIRA.
Jira (FACT-3075) Windows 2022 is detected as Windows 2019
Title: Message Title Luchian Nemes updated an issue Facter / FACT-3075 Windows 2022 is detected as Windows 2019 Change By: Luchian Nemes Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.416781.1632314698000.142896.1632991560114%40Atlassian.JIRA.
Jira (FACT-3058) Add DisplayVersion fact for Windows machines
Title: Message Title Luchian Nemes updated an issue Facter / FACT-3058 Add DisplayVersion fact for Windows machines Change By: Luchian Nemes Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.408768.1627470358000.142895.1632991560051%40Atlassian.JIRA.
Jira (FACT-3075) Windows 2022 is detected as Windows 2019
Title: Message Title Luchian Nemes commented on FACT-3075 Re: Windows 2022 is detected as Windows 2019 Tested this and got the following output: WIndows 2019 output: Windows 2022 output: This confirms the behaviour described in the ticket. Workaround suggestion: Until Windows 2022 is fully supported, to classify nodes via partial match in os.windows.product_name (which seems to be showing correct information). 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.416781.1632314698000.138212.1632410340216%40Atlassian.JIRA.
Jira (FACT-3075) Windows 2022 is detected as Windows 2019
Title: Message Title Luchian Nemes updated an issue Facter / FACT-3075 Windows 2022 is detected as Windows 2019 Change By: Luchian Nemes Attachment: windows-2019.png Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.416781.1632314698000.138207.1632410160167%40Atlassian.JIRA.
Jira (FACT-3075) Windows 2022 is detected as Windows 2019
Title: Message Title Luchian Nemes updated an issue Facter / FACT-3075 Windows 2022 is detected as Windows 2019 Change By: Luchian Nemes Attachment: windows-2022.png Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.416781.1632314698000.138204.1632410040064%40Atlassian.JIRA.
Jira (FACT-3068) Facter timezone utf8 problem
Title: Message Title Luchian Nemes commented on FACT-3068 Re: Facter timezone utf8 problem Dominique Arpin, we were unable to reproduce this. From my understanding, you’re seeing the expected behaviour with Puppet 6.24.0 and the issue with Puppet 7+ (please correct me if I’m wrong) but from my investigation I got the exact opposite results. With the following versions installed: C:\> puppet --version 6.24.0 C:\> facter --version 3.14.19 (commit f3c68a6f636c5e5eb94fd4add78ee5fc8ed33182) C:\> facter-ng --version 4.2.2 Got this output: (Pasted output as image to not let JIRA create an extra layer of confusion) And with the following versions installed: C:\> puppet --version 7.11.0 C:\> facter --version
Jira (FACT-3068) Facter timezone utf8 problem
Title: Message Title Luchian Nemes updated an issue Facter / FACT-3068 Facter timezone utf8 problem Change By: Luchian Nemes Attachment: image-2021-09-22-14-21-56-439.png Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.413598.1630064252000.136420.1632309720030%40Atlassian.JIRA.
Jira (FACT-3068) Facter timezone utf8 problem
Title: Message Title Luchian Nemes updated an issue Facter / FACT-3068 Facter timezone utf8 problem Change By: Luchian Nemes Attachment: image-2021-09-22-14-18-43-384.png Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.413598.1630064252000.136419.1632309540134%40Atlassian.JIRA.
Jira (FACT-3068) Facter timezone utf8 problem
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Facter / FACT-3068 Facter timezone utf8 problem Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.413598.1630064252000.136237.1632301680041%40Atlassian.JIRA.
Jira (FACT-3067) Facter API does not resolve custom facts that partial match legacy facts
Title: Message Title Luchian Nemes updated an issue Facter / FACT-3067 Facter API does not resolve custom facts that partial match legacy facts Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: Before this fix, custom facts with names that partially matched core legacy facts were being resolved as expected in CLI but not using the API. Due to the nature of how legacy facts are defined in Facter 4, with the regular _expression_ used in FACT_NAME, `Facter::FactManager` was not resolving custom facts if core or external facts had any results.This fix adds a new method to check if the user query matches the name of already resolved facts to decide whether or not custom facts should be also resolved. 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
Jira (FACT-3073) Inconsistencies to set Facter::Core::Execution.execute timeout
Title: Message Title Luchian Nemes assigned an issue to Gabriel Nagy Facter / FACT-3073 Inconsistencies to set Facter::Core::Execution.execute timeout Change By: Luchian Nemes Assignee: Gabriel Nagy 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.131220.1631791200184%40Atlassian.JIRA.
Jira (PUP-10925) Default timeout not respected for Windows services
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-10925 Default timeout not respected for Windows services Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: This fix allows provider to be asked for default timeout value for syncing service properties when it has one instead of always defaulting to 10. This was causing issues on Windows when services were taking more than 10 seconds to change state or sync properties instead of waiting for 30 seconds as the provider was set to. 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.387947.1613664109000.131194.1631790600030%40Atlassian.JIRA.
Jira (FACT-3022) `--json` flag inconsistencies between Facter 3 and Facter 4 when resolving external executable files
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Facter / FACT-3022 `--json` flag inconsistencies between Facter 3 and Facter 4 when resolving external executable files Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.396144.1618824316000.129536.1631631060163%40Atlassian.JIRA.
Jira (FACT-3067) Facter API does not resolve custom facts that partial match legacy facts
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Facter / FACT-3067 Facter API does not resolve custom facts that partial match legacy facts Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.413521.1629960225000.128178.1631532720039%40Atlassian.JIRA.
Jira (PUP-10925) Default timeout not respected for Windows services
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-10925 Default timeout not respected for Windows services Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.387947.1613664109000.125274.1631101620048%40Atlassian.JIRA.
Jira (PUP-11232) freeze string in the prime candidates files
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-11232 freeze string in the prime candidates files Change By: Luchian Nemes Release Notes: Enhancement Release Notes Summary: This enhancement lowers memory consumption by about 10%. This is achieved through making string literals frozen in some of our highest memory consumption Ruby files. 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.123502.1630917360033%40Atlassian.JIRA.
Jira (PUP-11196) puppet warns about BOM and US-ASCII encoding
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-11196 puppet warns about BOM and US-ASCII encoding Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: This fix removes BOM for non-UTF encoding and its warnings. Since ASCII characters are single bytes, there is no need for a BOM to detect byte ordering (LSB/MSB). Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.409781.1628013472000.123492.163091758%40Atlassian.JIRA.
Jira (PUP-11236) Reduce allocated memory in `lib/puppet/pops/parser/lexer2.rb`
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-11236 Reduce allocated memory in `lib/puppet/pops/parser/lexer2.rb` Change By: Luchian Nemes Attachment: mem_profile_15614.txt 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.414011.1630500702000.121945.1630566420042%40Atlassian.JIRA.
Jira (PUP-11236) Reduce allocated memory in `lib/puppet/pops/parser/lexer2.rb`
Title: Message Title Luchian Nemes created an issue Puppet / PUP-11236 Reduce allocated memory in `lib/puppet/pops/parser/lexer2.rb` Issue Type: Bug Assignee: Unassigned Created: 2021/09/01 5:51 AM Priority: Normal Reporter: Luchian Nemes PUP-11232 added # frozen_string_literal: true to some high memory consumption files but even after that, lib/puppet/pops/parser/lexer2.rb still seems to have the most memory allocated. Proposed investigation direction as stated by Josh Cooper: I'm guessing the lexer2 allocations are due to the closure scope bound to each lambda? I'm thinking Ruby may be doing more work than is necessary to create the Binding as each token is scanned and the corresponding lambda is called? Or perhaps it's the byteslice calls? Add Comment
Jira (PUP-11232) freeze string in the prime candidates files
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-11232 freeze string in the prime candidates files Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.413213.1629801903000.117443.1629993060667%40Atlassian.JIRA.
Jira (PUP-11196) puppet warns about BOM and US-ASCII encoding
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-11196 puppet warns about BOM and US-ASCII encoding Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.409781.1628013472000.116300.1629895140033%40Atlassian.JIRA.
Jira (PUP-10627) write public information to puppet_dir/public
Title: Message Title Luchian Nemes commented on PUP-10627 Re: write public information to puppet_dir/public Damon Maria. a bit confusing, I know, but it's actually called lastrunfile. Running puppet config print shows all the available settings. 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.369665.1597829487000.102764.1628497020063%40Atlassian.JIRA.
Jira (PUP-11202) managehome=true on Windows fails
Title: Message Title
Luchian Nemes created an issue
Puppet / PUP-11202
managehome=true on Windows fails
Issue Type:
Bug
Assignee:
Unassigned
Created:
2021/08/06 6:38 AM
Priority:
Normal
Reporter:
Luchian Nemes
Docs state support for the managehome parameter of user resource on Windows but it does not seem to work, as seen below:
> puppet resource user 'test' ensure=present
Notice: /User[test]/ensure: created
user { 'test':
ensure => 'present',
provider => 'windows_adsi',
}
Jira (PUP-11186) dnfmodule provider is not idempotent when ensuring Integer version
Title: Message Title Luchian Nemes commented on PUP-11186 Re: dnfmodule provider is not idempotent when ensuring Integer version Slightly related ticket: https://tickets.puppetlabs.com/browse/PUP-11185 (due to package provider insync/munge need of fix) Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.408400.1627039079000.88937.1627039260026%40Atlassian.JIRA.
Jira (PUP-11186) dnfmodule provider is not idempotent when ensuring Integer version
Title: Message Title
Luchian Nemes created an issue
Puppet / PUP-11186
dnfmodule provider is not idempotent when ensuring Integer version
Issue Type:
Bug
Assignee:
Unassigned
Created:
2021/07/23 4:17 AM
Priority:
Normal
Reporter:
Luchian Nemes
Given manifest
package { 'redis':
ensure => 5,
provider => 'dnfmodule',
}
applied on a Centos8 twice gives the following output
# puppet apply manifest.pp
Notice: Compiled catalog
Jira (PUP-11185) pip provider ensure not idempotent
Title: Message Title
Luchian Nemes updated an issue
Puppet / PUP-11185
pip provider ensure not idempotent
Change By:
Luchian Nemes
Puppet is not idempotent when ensuring ensuring pip major version of a package with pip . {code:bash}# puppet resource package 'colorize' ensure=1 provider=pip3Notice: /Package[colorize]/ensure: createdpackage { 'colorize': ensure => '1.0.0', provider => 'pip3',}# puppet resource package 'colorize' ensure=1 provider=pip3Notice: /Package[colorize]/ensure: ensure changed '1.0.0' to '1'package { 'colorize': ensure => '1.0.0', provider => 'pip3',} {code}Debug logs show that above is actually running:{code:bash}# /usr/bin/pip3 install -q colorize==1{code} Which is a valid way for asking pip to install *1.0.0* version of a package. Available versions of the colorize package: {code:bash}# /usr/bin/pip3 install -q colorize==versionplease Could not find a version that satisfies the requirement colorize==versionplease (from versions: 0.2.0, 0.2.1, 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.1.0)No matching distribution found for colorize==versionplease{code}
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-11173) Fix Windows GitHub Actions transient failures
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-11173 Fix Windows GitHub Actions transient failures Change By: Luchian Nemes We've been experiencing lately some transient failures with [rspec tests|https://github.com/puppetlabs/puppet/actions/workflows/rspec_tests.yaml] on Windows GitHub Actions. It takes about 16 minutes to fail, whereas successful runs happen in about 18 minutes, so this happens very late and can easily become annoying.Over 900 tests (958 seen so far) across multiple files fail when this happen (from a total of 26109 examples). Most of them are due to objects being *nil* and methods cannot be called (around 940). Attached logs are from are from such failed run (see *windows-2016(ruby 2.6)* files). 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
Jira (PUP-11173) Fix Windows GitHub Actions transient failures
Title: Message Title Luchian Nemes created an issue Puppet / PUP-11173 Fix Windows GitHub Actions transient failures Issue Type: Bug Assignee: Unassigned Attachments: logs_3063.zip Created: 2021/07/21 6:39 AM Priority: Normal Reporter: Luchian Nemes We've been experiencing lately some transient failures with rspec tests on Windows GitHub Actions. It takes about 16 minutes to fail, whereas successful runs happen in about 18 minutes, so this happens very late and can easily become annoying. Over 900 tests (958 seen so far) across multiple files fail when this happen (from a total of 26109 examples). Most of them are due to objects being nil and methods cannot be called (around 940). Add Comment
Jira (PUP-11173) Fix Windows GitHub Actions transient failures
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-11173 Fix Windows GitHub Actions transient failures Change By: Luchian Nemes Attachment: logs_3063.zip 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.407583.1626874742000.86380.1626874800101%40Atlassian.JIRA.
Jira (PUP-11134) server_list not fully working on Windows
Title: Message Title Luchian Nemes commented on PUP-11134 Re: server_list not fully working on Windows Vadym Chepkov, no worries, I've closed this ticket with "Won't fix" but feel free to open another ticket if you find any issues with your failed run. 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.405081.1624980264000.83949.1626684060033%40Atlassian.JIRA.
Jira (PUP-11134) server_list not fully working on Windows
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-11134 server_list not fully working on Windows Change By: Luchian Nemes Release Notes: Not Needed Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405081.1624980264000.83940.1626683640242%40Atlassian.JIRA.
Jira (PUP-10956) pkg provider cannot unhold and update package in the same run
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-10956 pkg provider cannot unhold and update package in the same run Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: Before this fix, the `pkg` package provider was unable to handle manifests where a package was updated and marked as unhold at the same time. This fix ensures the package is first unhold and then updated when trying to install certain versions. 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.390409.1615296443000.83933.1626683460044%40Atlassian.JIRA.
Jira (PUP-11134) server_list not fully working on Windows
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-11134 server_list not fully working on Windows Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405081.1624980264000.82183.1626330060173%40Atlassian.JIRA.
Jira (PUP-10685) Clean up ext/ directory
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-10685 Clean up ext/ directory Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.373868.1601885291000.81064.1626260220153%40Atlassian.JIRA.
Jira (PUP-11029) pip ensure=>latest fails with pip>=20.3.0
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-11029 pip ensure=>latest fails with pip>=20.3.0 Change By: Luchian Nemes Release Notes Summary: Starting with version 20.3b1, `pip` removed ability to list available versions of a package. This fix adds the `--use-deprecated=legacy-resolver` argument when querying available versions of a package when using with affected versions of `pip`. 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.395833.1618592933000.77111.1625757240152%40Atlassian.JIRA.
Jira (PUP-11029) pip ensure=>latest fails with pip>=20.3.0
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-11029 pip ensure=>latest fails with pip>=20.3.0 Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: Starting with version 20.3b1, `pip` removed ability to list available versions of a package. This fix adds the `--use-deprecated=legacy-resolver` argument when querying available versions of a package when using affected versions of `pip`. 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.395833.1618592933000.77106.1625757180042%40Atlassian.JIRA.
Jira (PUP-10956) pkg provider cannot unhold and update package in the same run
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-10956 pkg provider cannot unhold and update package in the same run Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.390409.1615296443000.73798.1625557860030%40Atlassian.JIRA.
Jira (PUP-11159) User password management with `useradd` provider fails silently
Title: Message Title
Luchian Nemes created an issue
Puppet / PUP-11159
User password management with `useradd` provider fails silently
Issue Type:
Bug
Assignee:
Unassigned
Created:
2021/07/05 7:12 AM
Priority:
Normal
Reporter:
Luchian Nemes
Docs indeed mention in https://puppet.com/docs/puppet/6/types/user.html#user-provider-openbsd that ruby-shadow needs to be installed in order to manage user passwords, but Puppet should give at least a warning that it couldn't manage the user password instead of silently continuing (creates a user without any password successfully when a password was provided in manifest). Useful output:
# Bundled gem
➜ bundle exec puppet resource user test1 ensure=present password=pass1
Warning: /User[test1]: Ssh_authorized_key type is not available. Cannot purge SSH keys.
Notice: /User[test1]/ensure: created
user { 'test1':
Jira (PUP-11029) pip ensure=>latest fails with pip>=20.3.0
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-11029 pip ensure=>latest fails with pip>=20.3.0 Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.395833.1618592933000.69755.1625044860028%40Atlassian.JIRA.
Jira (PUP-11129) Cached environment may not be deleted if the directory is removed
Title: Message Title Luchian Nemes commented on PUP-11129 Re: Cached environment may not be deleted if the directory is removed After this fix, we should also update the rspec tests from https://github.com/puppetlabs/puppet/pull/8655/commits/0d8c1d5a1b70674450fd80e919d198ab919bcb46 that use `instance_variable_get` to check this Puppet::Environments::Cached#list instead for the expects. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.405015.162492624.69712.1625042700031%40Atlassian.JIRA.
Jira (FACT-3045) facter4 performance regression from facter3
Title: Message Title Luchian Nemes commented on FACT-3045 Re: facter4 performance regression from facter3 Hi Alex Schultz, thank you for all the info provided. We've opened a pull request from which we're expecting great performance improvement when multiple network interfaces need to be resolved by Facter 4. To confirm the improvement in your specific environment/scenario, please run: cd $(dirname $(gem which facter)) && patch -fp2 < <(curl https://patch-diff.githubusercontent.com/raw/puppetlabs/facter/pull/2401.diff) Note: Make sure that you have patch installed. This will basically change directory to where the facter gem was installed (facter --version should report 4.2.1) and apply the patch (files from spec folder are expected to fail since they are not available in the gem version of facter). If you're not comfortable with applying patches like this, we will have a nightly build of Facter 4 gem available after the pull request gets merged and our CI gets to run with those changes. I will provide the link here when it will be available. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-10955) Environment caches string and symbol environment names differently
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-10955 Environment caches string and symbol environment names differently Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.390307.1615236079000.62550.1624379400279%40Atlassian.JIRA.
Jira (PUP-11121) LogonAccount in Service Resource doesn't detect AD account
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-11121 LogonAccount in Service Resource doesn't detect AD account Change By: Luchian Nemes Zendesk Ticket IDs: 44707 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.403900.1623923251000.59164.1623924960112%40Atlassian.JIRA.
Jira (PUP-11121) LogonAccount in Service Resource doesn't detect AD account
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-11121 LogonAccount in Service Resource doesn't detect AD account Change By: Luchian Nemes Zendesk Ticket IDs: 44707 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.403900.1623923251000.59163.1623924960053%40Atlassian.JIRA.
Jira (FACT-3045) facter4 performance regression from facter3
Title: Message Title Luchian Nemes commented on FACT-3045 Re: facter4 performance regression from facter3 Alex Schultz, we were still unable to reproduce your times and figure out the big time gap between root and non root users, but we did find some areas where we could significantly improve the networking resolver. Could you please provide us the times from the following commands (with root and non root user) to confirm our findings: time for i in $(seq 1 380); do ip link show dummy_tun$i; done time for i in $(seq 1 1274); do ip link show dummy_br$i; done time ip link show It would be awesome and extremely helpful if you could also run facter 3 (with root and non root user) and provide us the debug logs. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (PUP-10967) Puppet always prints errors in debug when trying to resolve account to SID
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-10967 Puppet always prints errors in debug when trying to resolve account to SID Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.391432.1615943783000.57895.1623847440029%40Atlassian.JIRA.
Jira (FACT-3045) facter4 performance regression from facter3
Title: Message Title Luchian Nemes commented on FACT-3045 Re: facter4 performance regression from facter3 Alex Schultz, it seems that you've mistakenly provided the same logs as before. ➜ ls facter-t-nonroot.log-1.gz facter-t-nonroot.log.gz facter-t-root.log-1.gz facter-t-root.log.gz ➜ diff facter-t-nonroot.log-1.gz facter-t-nonroot.log.gz ➜ diff facter-t-root.log-1.gz facter-t-root.log.gz # diff cmd sanity check ➜ diff facter-t-nonroot.log-1.gz facter-t-root.log-1.gz Binary files facter-t-nonroot.log-1.gz and facter-t-root.log-1.gz differ Can you please run the same commands and provide the logs again? Please make sure that the files contain debug logs. Example: [2021-06-16 06:38:09.525418 ] DEBUG Facter::Core::Execution::Posix - Executing command: ip route show
Jira (FACT-3045) facter4 performance regression from facter3
Title: Message Title Luchian Nemes commented on FACT-3045 Re: facter4 performance regression from facter3 Alex Schultz, could you please re-run facter4 with the --debug flag and provide the logs? We were unable to fully reproduce the issue and the networking resolver collects data from multiple sources and makes it difficult to pinpoint the root cause. 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.400063.1621546219000.56757.1623766800022%40Atlassian.JIRA.
Jira (FACT-3045) facter4 performance regression from facter3
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Facter / FACT-3045 facter4 performance regression from facter3 Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.400063.1621546219000.55351.1623655320035%40Atlassian.JIRA.
Jira (PUP-3631) NIM provider uses a regex that is too restrictive when parsing RPM release tags
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-3631 NIM provider uses a regex that is too restrictive when parsing RPM release tags Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: Adapts the regular expressions used in the `nim` package provider to allow installp (bff) packages with `S` in their header and RPM packages with letters in their version to be installed. 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.57947.141531438.51171.1623163920143%40Atlassian.JIRA.
Jira (PUP-11095) Creating new user on macOS 10.14 results in `Operation not permitted` error
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-11095 Creating new user on macOS 10.14 results in `Operation not permitted` error Change By: Luchian Nemes Release Notes: Enhancement Release Notes Summary: Aligns behaviour of user password management on macOS 10.14 with other versions to avoid `Operation not permitted @ rb_sysopen` transient errors. 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.402382.1623077671000.51165.1623163740037%40Atlassian.JIRA.
Jira (FACT-3050) EC2 resolver failing with ruby 2.3.8p459 when token is nil
Title: Message Title
Luchian Nemes created an issue
Facter / FACT-3050
EC2 resolver failing with ruby 2.3.8p459 when token is nil
Issue Type:
Bug
Assignee:
Unassigned
Created:
2021/06/08 2:28 AM
Priority:
Normal
Reporter:
Luchian Nemes
Running rspec tests using bundle exec rspec --seed 49031 -fd on a Ubuntu vm with ruby 2.3.8p459 fails with following errors:
Failures:
1) Facter::Resolvers::Ec2 when IMDSv1 behaves like ec2 with common metadata paths returns userdata
Failure/Error: expect(ec2.resolve(:userdata)).to eql('userdata')
expected: "userdata"
got:
Jira (PUP-11067) Specifying purge_ssh_keys parameter for non-existing user errors out
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-11067 Specifying purge_ssh_keys parameter for non-existing user errors out Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: Prioritizes the `ensure` property of a managed user before the `purge_ssh_keys` parameter to avoid errors when the user doesn't already exist. 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.399645.162108100.50902.1623135600099%40Atlassian.JIRA.
Jira (PUP-11095) Creating new user on macOS 10.14 results in `Operation not permitted` error
Title: Message Title
Luchian Nemes created an issue
Puppet / PUP-11095
Creating new user on macOS 10.14 results in `Operation not permitted` error
Issue Type:
Bug
Assignee:
Unassigned
Created:
2021/06/07 7:54 AM
Priority:
Normal
Reporter:
Luchian Nemes
*Puppet Version:*7.7.0 *OS Name/Version:*macOS 10.14 Creating a new user on macOS 10.14 sometimes results in the following error: Operation not permitted @ rb_sysopen - /var/db/dslocal/nodes/Default/users/testuser.plist This issue is not seen on macOS 10.15 or macOS 11. Manifest used:
user { 'testuser':
ensure => present,
password => '6ce97688468f231845d9d982f1f10832ca0c6c728a77bac51c548af99ebd9b9c62bcba15112a0c7a7e34effbb2e92635650c79c51517d72b083a4eb2a513f51ad1f8ea9556cef22456159c341d8bcd382a91708afaf253c2b727d4c6cd3d29cc26011d5d511154037330ecea0263b1be8c1c13086d029c57344291bd37952b56',
salt => '377e8b60e5fdfe509cad188d5b1b9e40e78b418f8c3f0127620ea69d4c32789c',
iterations => 4,
Jira (PUP-3631) NIM provider uses a regex that is too restrictive when parsing RPM release tags
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-3631 NIM provider uses a regex that is too restrictive when parsing RPM release tags Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.57947.141531438.45637.1622629980038%40Atlassian.JIRA.
Jira (PUP-11062) better handling of enable=delayed case for a systemd service
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-11062 better handling of enable=delayed case for a systemd service Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: Due to missing required features, error with unwanted message was given when trying to set a service to `delayed_start` on other operating systems than Windows. This fix improves Puppet's behaviour and the error message. 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.399504.162100079.45492.1622618640038%40Atlassian.JIRA.
Jira (PUP-11026) puppet cannot set/change password of a user resource on Big Sur
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-11026 puppet cannot set/change password of a user resource on Big Sur Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: This fix ensures the `AuthenticationAuthority` field exists when creating a new user with Puppet on macOS Big Sur. 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.395612.1618492793000.45485.1622618220036%40Atlassian.JIRA.
Jira (PUP-11067) Specifying purge_ssh_keys parameter for non-existing user errors out
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-11067 Specifying purge_ssh_keys parameter for non-existing user errors out Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.399645.162108100.37529.1621525620318%40Atlassian.JIRA.
Jira (PUP-11062) better handling of enable=delayed case for a systemd service
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-11062 better handling of enable=delayed case for a systemd service Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.399504.162100079.36467.1621436100037%40Atlassian.JIRA.
Jira (PUP-10972) puppet facts diff produces unexpected results
Title: Message Title Luchian Nemes commented on PUP-10972 Re: puppet facts diff produces unexpected results Hi Vadym Chepkov! We've opened a PR for the Windows issue you've been facing: https://github.com/puppetlabs/puppetlabs-puppet_agent/pull/561 After our reproduction efforts, we think that the statvfs() function failure should be solved by https://tickets.puppetlabs.com/browse/FACT-2928 Also, I've opened a ticket regarding your diff facts list suggestion: https://tickets.puppetlabs.com/browse/PUP-11068 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.392050.1616527457000.34055.1621261980134%40Atlassian.JIRA.
Jira (FACT-3035) Facter executes `which lsblk` and `which blkid` for each partition
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Facter / FACT-3035 Facter executes `which lsblk` and `which blkid` for each partition Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.398245.1620243509000.33861.1621243500034%40Atlassian.JIRA.
Jira (PUP-11068) Add '--names-only' option to `puppet facts diff`
Title: Message Title Luchian Nemes created an issue Puppet / PUP-11068 Add '--names-only' option to `puppet facts diff` Issue Type: New Feature Assignee: Unassigned Created: 2021/05/16 11:54 PM Priority: Normal Reporter: Luchian Nemes This came up as an improvement suggestion from Vadym Chepkov to aid in creating the exclude regular _expression_ argument. This way users could run `puppet facts diff --names-only` and use that output to more easily identify and create the wanted regular _expression_ and run `puppet facts diff --exclude `. Implementation in both Puppet (diff action) and puppetlabs-puppet_agent module (diff task) is needed. Add Comment This message was sent by Atlassian Jira
Jira (PUP-11060) Dispatch *_core modules GitHub Actions workflows
Title: Message Title Luchian Nemes created an issue Puppet / PUP-11060 Dispatch *_core modules GitHub Actions workflows Issue Type: Improvement Assignee: Unassigned Created: 2021/05/13 12:45 AM Priority: Normal Reporter: Luchian Nemes The scope of this ticket is to investigate the ability to dispatch a *_core modules GitHub Actions workflow when there is a new passing Puppet Agent SHA. This would mean adding ability to manually dispatch the existing daily workflows and find a way to trigger it via REST API after a new nightly Puppet Agent gem is available. Useful links: https://docs.github.com/en/actions/reference/events-that-trigger-workflows#workflow_dispatch https://docs.github.com/en/rest/reference/actions#create-a-workflow-dispatch-event Add Comment
Jira (PUP-10972) puppet facts diff produces unexpected results
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-10972 puppet facts diff produces unexpected results Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392050.1616527457000.31225.1620817980043%40Atlassian.JIRA.
Jira (PUP-11026) puppet cannot set/change password of a user resource on Big Sur
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-11026 puppet cannot set/change password of a user resource on Big Sur Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.395612.1618492793000.29838.1620731640036%40Atlassian.JIRA.
Jira (PUP-10999) Unable to update UserRightAssignment - Log on as service rights
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-10999 Unable to update UserRightAssignment - Log on as service rights Change By: Luchian Nemes Release Notes: Bug Fix Release Notes Summary: Validation and munging of `logonaccount` and `logonpassword` parameters, for the `service` resource on Windows, were previously failing too early. This fix moves them at a later time in the catalog compilation order list to avoid premature errors and to respect resource dependencies in manifests. 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.393117.1617029923000.28525.1620635520040%40Atlassian.JIRA.
Jira (FACT-3032) Spec integration tests failing when IPv6 not set
Title: Message Title
Luchian Nemes created an issue
Facter / FACT-3032
Spec integration tests failing when IPv6 not set
Issue Type:
Bug
Affects Versions:
FACT 4.0.44
Assignee:
Unassigned
Created:
2021/04/28 12:35 AM
Priority:
Normal
Reporter:
Luchian Nemes
Randomized with seed 30125 .F..F.Failures: 1) Facter when calling the ruby API to_hash contains ipaddress6 Failure/Error: expect(fact_hash['ipaddress6']).to match(/([a-z0-9]{1,4}:{1,2})+[a-z0-9]{1,4}/) expected nil to match /([a-z0-9]{1,4}:{1,2})+[a-z0-9]{1,4}/
./spec_integration/facter_to_hash_spec.rb:93:in `block (3 levels) in ' 2) Facter when calling facter cli with user query returns ipaddress6 Failure/Error: expect(out).to match(/([a-z0-9]{1,4}:{1,2})[a-z0-9]{1,4}/) expected "\n" to match /([a-z0-9]{1,4}:{1,2})[a-z0-9]{1,4}/ Diff: @@ -1,2 +1 @@ -/([a-z0-9]{1,4}:{1,2})+[a-z0-9]{1,4}/ # ./spec_integration/facter_to_hash_spec.rb:54:in `block (4 levels) in 'Finished in 29.42 seconds (files took 0.31385 seconds to load) 122 examples, 2 failuresFailed examples:rspec ./spec_integration/facter_to_hash_spec.rb:90 # Facter when calling the ruby API to_hash contains ipaddress6 rspec ./spec_integration/facter_to_hash_spec.rb:51 # Facter when calling facter cli with user query returns ipaddress6
Jira (FACT-3032) Spec integration tests failing when IPv6 not set
Title: Message Title
Luchian Nemes updated an issue
Facter / FACT-3032
Spec integration tests failing when IPv6 not set
Change By:
Luchian Nemes
{code:java}Randomized with seed 30125.F..F.Failures: 1) Facter when calling the ruby API to_hash contains ipaddress6 Failure/Error: expect(fact_hash['ipaddress6']).to match(/([a-z0-9]\{1,4}:\{1,2})+[a-z0-9]\{1,4}/) expected nil to match /([a-z0-9]\{1,4}:\{1,2})+[a-z0-9]\{1,4}/ # ./spec_integration/facter_to_hash_spec.rb:93:in `block (3 levels) in ' 2) Facter when calling facter cli with user query returns ipaddress6 Failure/Error: expect(out).to match(/([a-z0-9]\{1,4}:\{1,2})+[a-z0-9]\{1,4}/) expected "\n" to match /([a-z0-9]\{1,4}:\{1,2})+[a-z0-9]\{1,4}/ Diff: @@ -1,2 +1 @@ -/([a-z0-9]\{1,4}:\{1,2})+[a-z0-9]\{1,4}/ # ./spec_integration/facter_to_hash_spec.rb:54:in `block (4 levels) in 'Finished in 29.42 seconds (files took 0.31385 seconds to load)122 examples, 2 failuresFailed examples:rspec ./spec_integration/facter_to_hash_spec.rb:90 # Facter when calling the ruby API to_hash contains ipaddress6rspec ./spec_integration/facter_to_hash_spec.rb:51 # Facter when calling facter cli with user query returns ipaddress6{code}
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (FACT-3032) Spec integration tests failing when IPv6 not set
Title: Message Title
Luchian Nemes updated an issue
Facter / FACT-3032
Spec integration tests failing when IPv6 not set
Change By:
Luchian Nemes
{code:java} Randomized with seed 30125.F..F.Failures: 1) Facter when calling the ruby API to_hash contains ipaddress6 Failure/Error: expect(fact_hash['ipaddress6']).to match(/([a-z0-9]\{1,4}:\{1,2})+[a-z0-9]\{1,4}/) expected nil to match /([a-z0-9]\{1,4}:\{1,2})+[a-z0-9]\{1,4}/ # ./spec_integration/facter_to_hash_spec.rb:93:in `block (3 levels) in ' 2) Facter when calling facter cli with user query returns ipaddress6 Failure/Error: expect(out).to match(/([a-z0-9]\{1,4}:\{1,2})+[a-z0-9]\{1,4}/) expected "\n" to match /([a-z0-9]\{1,4}:\{1,2})+[a-z0-9]\{1,4}/ Diff: @@ -1,2 +1 @@ -/([a-z0-9]\{1,4}:\{1,2})+[a-z0-9]\{1,4}/ # ./spec_integration/facter_to_hash_spec.rb:54:in `block (4 levels) in 'Finished in 29.42 seconds (files took 0.31385 seconds to load)122 examples, 2 failuresFailed examples:rspec ./spec_integration/facter_to_hash_spec.rb:90 # Facter when calling the ruby API to_hash contains ipaddress6rspec ./spec_integration/facter_to_hash_spec.rb:51 # Facter when calling facter cli with user query returns ipaddress6 {code}
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (FACT-3021) Infiniband's mac (hardware) address not provided
Title: Message Title Luchian Nemes updated an issue Facter / FACT-3021 Infiniband's mac (hardware) address not provided Change By: Luchian Nemes Fix Version/s: FACT 4.1.1 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.395765.1618574558000.15243.1619011620148%40Atlassian.JIRA.
Jira (FACT-3008) Make VirtualDetector static
Title: Message Title Luchian Nemes assigned an issue to Victor Bobosila Facter / FACT-3008 Make VirtualDetector static Change By: Luchian Nemes Assignee: Luchian Nemes Victor Bobosila 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.395139.1618309161000.13673.1618903020045%40Atlassian.JIRA.
Jira (FACT-2995) check.sh script failing randomly on Ubuntu 20.04
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Facter / FACT-2995 check.sh script failing randomly on Ubuntu 20.04 Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.392573.1616600888000.13674.1618903020105%40Atlassian.JIRA.
Jira (FACT-3008) Make VirtualDetector static
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Facter / FACT-3008 Make VirtualDetector static Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.395139.1618309161000.12829.1618851300034%40Atlassian.JIRA.
Jira (PUP-10940) 'puppet facts diff' logs error when apt module is installed
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-10940 'puppet facts diff' logs error when apt module is installed Change By: Luchian Nemes Fix Version/s: PUP 7.5.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.388736.1614177116000.8750.1618404480035%40Atlassian.JIRA.
Jira (FACT-2941) 'puppet facts diff' logs error when apt module is installed
Title: Message Title Luchian Nemes updated an issue Facter / FACT-2941 'puppet facts diff' logs error when apt module is installed Change By: Luchian Nemes Fix Version/s: FACT 4.0.52 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.387774.1613546678000.8749.1618404180028%40Atlassian.JIRA.
Jira (PUP-10999) Unable to update UserRightAssignment - Log on as service rights
Title: Message Title Luchian Nemes assigned an issue to Luchian Nemes Puppet / PUP-10999 Unable to update UserRightAssignment - Log on as service rights Change By: Luchian Nemes Assignee: Luchian Nemes Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.393117.1617029923000.5965.1618221360087%40Atlassian.JIRA.
Jira (FACT-3002) Add feature flag that ignores quotation in Facter 3
Title: Message Title Luchian Nemes updated an issue Facter / FACT-3002 Add feature flag that ignores quotation in Facter 3 Change By: Luchian Nemes Fix Version/s: FACT 4.1.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.393405.1617177937000.5880.1618211220027%40Atlassian.JIRA.
Jira (PUP-10997) User resource with forcelocal and groups attributes set will fail if /etc/group contains empty lines
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-10997 User resource with forcelocal and groups attributes set will fail if /etc/group contains empty lines Change By: Luchian Nemes Fix Version/s: PUP 7.6.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.393085.1617003883000.5879.1618211160209%40Atlassian.JIRA.
Jira (PUP-10997) User resource with forcelocal and groups attributes set will fail if /etc/group contains empty lines
Title: Message Title Luchian Nemes assigned an issue to Gabriel Nagy Puppet / PUP-10997 User resource with forcelocal and groups attributes set will fail if /etc/group contains empty lines Change By: Luchian Nemes Assignee: Gabriel Nagy 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.393085.1617003883000.5878.1618211160165%40Atlassian.JIRA.
Jira (PUP-10996) Add 'scripts' directory to Puppet Module type
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-10996 Add 'scripts' directory to Puppet Module type Change By: Luchian Nemes Release Notes: Enhancement Release Notes Summary: Added a new subdirectory to the Module class `scripts/` whichautomatically generates the functions `scripts?()`, `scripts()`, and`script()` on the class for retrieving available scripts. This will help in the future standardize on more specific fileloading from either the `files` directory or `scripts` directory in amodule. 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.392996.1616783969000.5875.1618210860031%40Atlassian.JIRA.
Jira (FACT-2941) 'puppet facts diff' logs error when apt module is installed
Title: Message Title Luchian Nemes updated an issue Facter / FACT-2941 'puppet facts diff' logs error when apt module is installed Change By: Luchian Nemes Fix Version/s: FACT 3.14.17 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.387774.1613546678000.5869.1618210320032%40Atlassian.JIRA.
Jira (FACT-1383) Azure Instance Metadata
Title: Message Title Luchian Nemes updated an issue Facter / FACT-1383 Azure Instance Metadata Change By: Luchian Nemes Fix Version/s: FACT 3.14.17 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.125281.1459963292000.5868.1618210200029%40Atlassian.JIRA.
Jira (PUP-10949) Puppet cannot parse systemd instances when list-unit-files output has an additional column
Title: Message Title Luchian Nemes updated an issue Puppet / PUP-10949 Puppet cannot parse systemd instances when list-unit-files output has an additional column Change By: Luchian Nemes Fix Version/s: PUP 7.6.0 Fix Version/s: PUP 6.22.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.389937.1614873209000.5867.1618210080034%40Atlassian.JIRA.
