Jira (FACT-3065) submit facts for new facter releases to facterdb
Title: Message Title Gabriel Nagy commented on FACT-3065 Re: submit facts for new facter releases to facterdb I attached a factset for the current list of supported platforms, please let me know if there's anything else to be changed. The AIX filenames look weird because of the fact values that are used in building the filename (hardwaremodel, operatingsystemmajrelease) - should we change them to something like aix-7.1-powerpc ? I will change the directory structure to also include the Facter patch version, but the public mirroring of the factsets won't happen until after the holidays. facts.tar.gz Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.412672.1629371747000.6093.1639574880025%40Atlassian.JIRA.
Jira (FACT-3065) submit facts for new facter releases to facterdb
Title: Message Title Gabriel Nagy updated an issue Facter / FACT-3065 submit facts for new facter releases to facterdb Change By: Gabriel Nagy Attachment: facts.tar.gz Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.412672.1629371747000.6092.1639574820042%40Atlassian.JIRA.
Jira (FACT-3065) submit facts for new facter releases to facterdb
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Facter / FACT-3065 submit facts for new facter releases to facterdb Change By: Gabriel Nagy Assignee: Gabriel Nagy Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.412672.1629371747000.5121.1639498080060%40Atlassian.JIRA.
Jira (FACT-3065) submit facts for new facter releases to facterdb
Title: Message Title Gabriel Nagy commented on FACT-3065 Re: submit facts for new facter releases to facterdb ekohl bastelfreak I updated our fact generation script to more closely resemble the layout in facterdb: https://github.com/puppetlabs/puppet-agent/pull/2176 One question I have is if you think there would be value in also including the Facter patch version in the output directory name (i.e. 4.2.6 instead of 4.2 - for us this would be trivial). Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.412672.1629371747000.5110.1639496640033%40Atlassian.JIRA.
Jira (PUP-11328) Puppet agent may download all plugins after updating
Title: Message Title Gabriel Nagy commented on PUP-11328 Re: Puppet agent may download all plugins after updating I've spoken with brandfbb over Slack and the issue stems from the fact that the ENC is configured on the agent, not the server. This is a workflow not currently supported/documented by Puppet, as the documentation explicitly states the ENC is called by Puppet Server. The way this ticket impacts the workflow is the following, assuming Puppet Server has no ENC configured (so it doesn't decide the agent's environment): with last_run_summary.yaml absent, the agent run will make a node request; because the indirection class is exec, the local ENC script will be executed the ENC returns the environment the agent should run in, the agent switches to that environment and continues the run because the server is not authoritative, it will compile a catalog for the environment requested by the agent the agent applies the catalog and writes the initial environment (production or whatever's in puppet.conf) and the converged environment (ENC-specified environment) to last_run_summary.yaml because the initial and converged environment are different, subsequent agent runs will assume the last used environment was authoritative and will skip the node request the agent will no longer honor the environment specified by the ENC or the environment set in puppet.conf, and will always use the converged environment specified in last_run_summary.yaml A viable workaround for this case could be to specify the environment on the CLI: puppet agent -t --environment=$(/path/to/enc) Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
Jira (PUP-11328) Puppet agent may download all plugins after updating
Title: Message Title Gabriel Nagy commented on PUP-11328 Re: Puppet agent may download all plugins after updating I don't believe that changes anything; I updated my comment above to mention that I also tested using your setup (with separate server and agent boxes) and I get the same behavior. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.421154.1635201319000.111.1638887880028%40Atlassian.JIRA.
Jira (PUP-11328) Puppet agent may download all plugins after updating
Title: Message Title Gabriel Nagy commented on PUP-11328 Re: Puppet agent may download all plugins after updating I'm doing this on a single VM with the latest versions of puppet and puppetserver. I'll also try to reproduce using your specific setup: [root@jutish-crushing ~]# cat /etc/puppetlabs/puppet/enc.sh cat < --- environment: env3 ENV [root@jutish-crushing ~]# puppet --version 7.12.1 [root@jutish-crushing ~]# puppetserver --version puppetserver version: 7.4.2 [root@jutish-crushing ~]# cat /etc/puppetlabs/puppet/puppet.conf [main]
Jira (PUP-11328) Puppet agent may download all plugins after updating
Title: Message Title Gabriel Nagy commented on PUP-11328 Re: Puppet agent may download all plugins after updating Hi brandfbb, I wasn't able to reproduce your issue. Indeed, the logs are a bit misleading since Puppet always prints the environment it starts in (not necessarily the converged one). I set up a fresh environment where I first configured the ENC to return env1, then env2, then env3. The behavior looks correct to me, I'm sharing my logs below: [root@jutish-crushing ~]# grep environment /etc/puppetlabs/puppet/enc.sh environment: env1 [root@jutish-crushing ~]# puppet agent -t Notice: Local environment: 'production' doesn't match server specified node environment 'env1', switching agent to 'env1'. Info: Using environment 'env1' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Caching catalog for jutish-crushing.delivery.puppetlabs.net Info: Applying configuration version '1638880188' Info: Creating state file /opt/puppetlabs/puppet/cache/state/state.yaml
Jira (PUP-11239) multiple facter implementations blogpost
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-11239 multiple facter implementations blogpost Change By: Gabriel Nagy 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.414802.1631086704000.10427.1637236320050%40Atlassian.JIRA.
Jira (FACT-3087) 'os.name' value changed for OS VirtuozzoLinux
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Facter / FACT-3087 'os.name' value changed for OS VirtuozzoLinux Change By: Gabriel Nagy 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.421343.163536132.5780.1636711080080%40Atlassian.JIRA.
Jira (FACT-3083) Add wwn and sn to disk fact
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Facter / FACT-3083 Add wwn and sn to disk fact Change By: Gabriel Nagy 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.420812.163498016.4887.1636634400040%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gabriel Nagy commented on FACT-3039 Re: Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 PR for rspec-puppet: https://github.com/puppetlabs/rspec-puppet/pull/16 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.380977.1608048829000.89.1636112580153%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gabriel Nagy commented on FACT-3039 Re: Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 I did a first pass of the rspec-puppet Facter implementation: https://github.com/GabrielNagy/rspec-puppet/commit/7ad4c36b2abdffe0017e4cb1b928969708549d9c With this commit puppet-nginx unit tests drop by around 10 minutes (before: https://github.com/GabrielNagy/puppet-nginx/pull/2 after: https://github.com/GabrielNagy/puppet-nginx/pull/1). The runtimes still seemed long, so I also triggered some runs with puppet 5, where the total runtime drops by another 10 minutes: https://github.com/GabrielNagy/puppet-nginx/pull/4 So the slowness is caused by both Puppet 6 and Facter 4. I'm assuming catalog compilation is a bit slower on puppet 6 than on puppet 5, but I'm not sure how to start debugging this. Josh Cooper do you have any idea if this is the case? 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.380977.1608048829000.169161.1635950580093%40Atlassian.JIRA.
Jira (FACT-3039) Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Facter / FACT-3039 Puppet6/ruby2.5 runs in 42 minutes, where Puppet5/ruby2.4 runs in 25 Change By: Gabriel Nagy Assignee: Gheorghe Popescu 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.380977.1608048829000.165892.1635501780033%40Atlassian.JIRA.
Jira (PUP-11323) Puppet agent runs in environment specified on CLI when not in an agent specified environment
Title: Message Title Gabriel Nagy commented on PUP-11323 Re: Puppet agent runs in environment specified on CLI when not in an agent specified environment Hi Elaine McCloskey, we shuffled some log messages around as a result of implementing PUP-10539, however in this case PE/classifier should still be authoritative, regardless of what's specified on the CLI. Can you share the following logs? puppet agent -t --debug --environment=testing cat $(puppet config print lastrunfile) 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-3077) Inconsistent values coming from facter-ng output
Title: Message Title Gabriel Nagy commented on FACT-3077 Re: Inconsistent values coming from facter-ng output Jeremy Mozes, PE 2019.8.x ships with Facter 3 by default. Facter 4 (known as facter-ng in PE 2019.8.x) can be activated by setting facterng to true in the puppet.conf file. To my knowledge it will not be deprecated, it's just a way for customers to be able to opt-in to use Facter 4 while on PE 2019. In PE 2021, Facter 4 is shipped by default. 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.418363.1633415924000.156271.1634308200041%40Atlassian.JIRA.
Jira (PUP-11319) Updated puppet gem and rspec-puppet Failures
Title: Message Title Gabriel Nagy assigned an issue to Luchian Nemes Puppet / PUP-11319 Updated puppet gem and rspec-puppet Failures Change By: Gabriel Nagy Assignee: Gabriel Nagy 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.419463.1634134581000.155233.1634210040169%40Atlassian.JIRA.
Jira (PUP-11319) Updated puppet gem and rspec-puppet Failures
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-11319 Updated puppet gem and rspec-puppet Failures Change By: Gabriel Nagy 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.419463.1634134581000.155232.1634210040122%40Atlassian.JIRA.
Jira (FACT-3076) Custom facts cannot reference external facts
Title: Message Title Gabriel Nagy commented on FACT-3076 Re: Custom facts cannot reference external facts Hey Robert Berry, If you're using a recent enough version of Puppet 6, you can enable Facter 4 on a per-agent basis by setting facterng to true in puppet.conf (or on a per-run basis with puppet agent -t --facterng). We recommend you to be on the latest Puppet 6 version before you do this, so you benefit from the latest updates that went in Facter 4. 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.417351.1632831868000.151669.1633963140204%40Atlassian.JIRA.
Jira (PUP-11314) Requiring files inside settings hook is slow on Windows
Title: Message Title Gabriel Nagy commented on PUP-11314 Re: Requiring files inside settings hook is slow on Windows Merged to 6.x in https://github.com/puppetlabs/puppet/commit/b5e3d4e5a206010119f4c67b36c94983cae32d65 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.418429.1633451039000.149708.1633597320030%40Atlassian.JIRA.
Jira (PUP-11313) Puppet is trying to execute /etc/init.d/rc{0..6}.d directories
Title: Message Title
Gabriel Nagy assigned an issue to Gabriel Nagy
Puppet / PUP-11313
Puppet is trying to execute /etc/init.d/rc{0..6}.d directories
Change By:
Gabriel Nagy
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.387911.1613655138000.148253.1633516740100%40Atlassian.JIRA.
Jira (FACT-3077) Inconsistent values coming from facter-ng output
Title: Message Title Gabriel Nagy commented on FACT-3077 Re: Inconsistent values coming from facter-ng output Merged to main in https://github.com/puppetlabs/facter/commit/249cca06387374e0d146594842a2b173d41c702e 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.418363.1633415924000.148248.1633516200029%40Atlassian.JIRA.
Jira (FACT-3068) Facter timezone utf8 problem
Title: Message Title Gabriel Nagy updated an issue Facter / FACT-3068 Facter timezone utf8 problem Change By: Gabriel Nagy Component/s: Facter 3 Component/s: Facter 4 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.148229.1633514820516%40Atlassian.JIRA.
Jira (FACT-3068) Facter timezone utf8 problem
Title: Message Title Gabriel Nagy commented on FACT-3068 Re: Facter timezone utf8 problem Merged to main in https://github.com/puppetlabs/facter/commit/142ad0203f2dcabe1b8f703741b2813f004ca69f Dominique Arpin the commit above should fix the issue you're encountering 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.148218.1633514760086%40Atlassian.JIRA.
Jira (PUP-11311) Reduce memory usage from Pathname absolute?
Title: Message Title Gabriel Nagy commented on PUP-11311 Re: Reduce memory usage from Pathname absolute? Merged to main in https://github.com/puppetlabs/puppet/commit/7e27404bb33a06d60fdb3f793be46576efb4a657 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.418025.1633104409000.148037.1633495500023%40Atlassian.JIRA.
Jira (PUP-11313) Puppet is trying to execute /etc/init.d/rc{0..6}.d directories
Title: Message Title
Gabriel Nagy moved an issue
Puppet / PUP-11313
Puppet is trying to execute /etc/init.d/rc{0..6}.d directories
Change By:
Gabriel Nagy
Component/s:
Init Scripts
Component/s:
Types and Providers
Key:
PA PUP - 3647 11313
Affects Version/s:
puppet-agent 5.5.22
Project:
Puppet Agent
Add Comment
This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
--
You received this message because
Jira (FACT-2772) Facter in puppet 6.18.0-1 fails to prevent external facts from calling facter recursively (FACT-1373)
Title: Message Title Gabriel Nagy commented on FACT-2772 Re: Facter in puppet 6.18.0-1 fails to prevent external facts from calling facter recursively (FACT-1373) Boris I cannot reproduce this with the latest Facter 3. If I remove --no-external-facts from the facter call it shows a warning but still doesn't recurse: Warning: Facter: external fact file "/opt/puppetlabs/facter/facts.d/fact.rb" had output on stderr: 2021-10-04 10:38:30.349709 WARN puppetlabs.facter - external fact file "/opt/puppetlabs/facter/facts.d/fact.rb" had output on stderr: 2021-10-04 10:38:29.918306 WARN puppetlabs.facter - Facter was called recursively, skipping external facts. Add '--no-external-facts' to silence this warning Warning: Facter: external fact file "/opt/puppetlabs/facter/facts.d/fact.rb" had output on stderr: 2021-10-04 10:38:31.647756 WARN puppetlabs.facter - external fact file "/opt/puppetlabs/facter/facts.d/fact.rb" had output on stderr: 2021-10-04 10:38:31.219910 WARN puppetlabs.facter - Facter was called recursively, skipping external facts. Add '--no-external-facts' to silence this warning Same with Facter 4. I tested this both with facter -p and puppet facts. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97)
Jira (FACT-3058) Add DisplayVersion fact for Windows machines
Title: Message Title Gabriel Nagy updated an issue Facter / FACT-3058 Add DisplayVersion fact for Windows machines Change By: Gabriel Nagy Fix Version/s: FACT 3.14.20 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.142080.1632909360039%40Atlassian.JIRA.
Jira (PUP-11208) Puppet fails to install packages on Solaris if another pkg install is running
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-11208 Puppet fails to install packages on Solaris if another pkg install is running Change By: Gabriel Nagy Fix Version/s: PUP 7.12.0 Fix Version/s: PUP 6.25.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.412673.1629371858000.140836.1632825240033%40Atlassian.JIRA.
Jira (PUP-11265) puppet-agent : Concat not respecting environments
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-11265 puppet-agent : Concat not respecting environments Change By: Gabriel Nagy Fix Version/s: PUP 6.25.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.413595.1630046552000.140820.1632823860078%40Atlassian.JIRA.
Jira (FACT-3075) Windows 2022 is detected as Windows 2019
Title: Message Title Gabriel Nagy updated an issue Facter / FACT-3075 Windows 2022 is detected as Windows 2019 Change By: Gabriel Nagy Affects Version/s: FACT 3.14.20 Affects Version/s: FACT 4.2.5 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.416781.1632314698000.140817.1632823800360%40Atlassian.JIRA.
Jira (FACT-3075) Windows 2022 is detected as Windows 2019
Title: Message Title Gabriel Nagy updated an issue Facter / FACT-3075 Windows 2022 is detected as Windows 2019 Change By: Gabriel Nagy Fix Version/s: FACT 3.14.20 Fix Version/s: FACT 4.2.5 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.416781.1632314698000.140816.1632823800315%40Atlassian.JIRA.
Jira (FACT-3058) Add DisplayVersion fact for Windows machines
Title: Message Title Gabriel Nagy updated an issue Facter / FACT-3058 Add DisplayVersion fact for Windows machines Change By: Gabriel Nagy Fix Version/s: FACT 4.2.5 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.408768.1627470358000.140818.1632823800404%40Atlassian.JIRA.
Jira (FACT-3075) Windows 2022 is detected as Windows 2019
Title: Message Title Gabriel Nagy assigned an issue to Luchian Nemes Facter / FACT-3075 Windows 2022 is detected as Windows 2019 Change By: Gabriel Nagy Assignee: Ciprian Badescu 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.416781.1632314698000.140810.1632823740357%40Atlassian.JIRA.
Jira (FACT-3058) Add DisplayVersion fact for Windows machines
Title: Message Title Gabriel Nagy assigned an issue to Luchian Nemes Facter / FACT-3058 Add DisplayVersion fact for Windows machines Change By: Gabriel Nagy 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.408768.1627470358000.140803.1632823620166%40Atlassian.JIRA.
Jira (PUP-11265) puppet-agent : Concat not respecting environments
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-11265 puppet-agent : Concat not respecting environments Change By: Gabriel Nagy 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.413595.1630046552000.140688.1632815760169%40Atlassian.JIRA.
Jira (FACT-2955) AIX - mismatched processor frequencies found; facter will only report one of them
Title: Message Title Gabriel Nagy commented on FACT-2955 Re: AIX - mismatched processor frequencies found; facter will only report one of them Merged to main in https://github.com/puppetlabs/facter/commit/fd5ffa85a48203ea5f8e126a09217c5bc71ca60b and to 3.x in https://github.com/puppetlabs/facter/commit/c42634e4a3a6441d0b70fc457a90a48f0e982a7e 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.389740.161478837.133575.1632130440190%40Atlassian.JIRA.
Jira (FACT-3069) Facter 4.x on MS Azure: wrong domain is used in FQDN
Title: Message Title Gabriel Nagy commented on FACT-3069 Re: Facter 4.x on MS Azure: wrong domain is used in FQDN Sanjay Tripathi it's likely that you are hitting the same issue fixed in https://tickets.puppetlabs.com/browse/FACT-2923. Is this error reproducible with the latest puppet-agent/facter? 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.413950.1630428635000.132517.1631882220338%40Atlassian.JIRA.
Jira (PUP-11241) Not all user attributes honor forcelocal (e.g. home, shell)
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-11241 Not all user attributes honor forcelocal (e.g. home, shell) Change By: Gabriel Nagy Community Contributors: natemccurdy Release Notes: Bug Fix Release Notes Summary: Fix an issue where setting `forcelocal => true` on an user resource would still check the resource's `home` and `shell` attributes against their values from the directory service provider. 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-11241) Not all user attributes honor forcelocal (e.g. home, shell)
Title: Message Title Gabriel Nagy commented on PUP-11241 Re: Not all user attributes honor forcelocal (e.g. home, shell) Merged to 6.x in https://github.com/puppetlabs/puppet/commit/62c2cba0d7bfd61715e40d3720416b9bab8dc70b Thanks Nate McCurdy! 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.415709.1631667793000.132490.1631878800046%40Atlassian.JIRA.
Jira (PUP-11241) Not all user attributes honor forcelocal (e.g. home, shell)
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-11241 Not all user attributes honor forcelocal (e.g. home, shell) Change By: Gabriel Nagy Fix Version/s: PUP 7.12.0 Fix Version/s: PUP 6.25.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.415709.1631667793000.132491.1631878800068%40Atlassian.JIRA.
Jira (FACT-3069) Facter 4.x on MS Azure: wrong domain is used in FQDN
Title: Message Title Gabriel Nagy commented on FACT-3069 Re: Facter 4.x on MS Azure: wrong domain is used in FQDN Hi Sanjay Tripathi, we're going to start looking over this. This happening on both Azure and AWS might be linked to the fact that the Windows flavor is DataCenter, so there shouldn't be a separate ticket for that. 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.413950.1630428635000.132489.1631878380034%40Atlassian.JIRA.
Jira (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title Gabriel Nagy commented on PUP-9041 Re: AIX nim provider can't be used on a NIM master For future reference, the PR for this is https://github.com/puppetlabs/puppet/pull/7655 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.267945.153332494.130275.1631698140394%40Atlassian.JIRA.
Jira (FACT-3073) Inconsistencies to set Facter::Core::Execution.execute timeout
Title: Message Title Gabriel Nagy updated an issue Facter / FACT-3073 Inconsistencies to set Facter::Core::Execution.execute timeout Change By: Gabriel Nagy Release Notes: Bug Fix Release Notes Summary: Fix the mismatch of `Facter::Core::Execution.execute` arguments between Facter 3 and Facter 4. The `.execute` method now accepts a `timeout` option like Facter 3 does, and warns when unsupported options are passed in. (Fix contributed by community members https://github.com/smortex and https://github.com/johanfleury) 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.129292.1631612400030%40Atlassian.JIRA.
Jira (FACT-3073) Inconsistencies to set Facter::Core::Execution.execute timeout
Title: Message Title Gabriel Nagy commented on FACT-3073 Re: Inconsistencies to set Facter::Core::Execution.execute timeout Merged to main in https://github.com/puppetlabs/facter/commit/2239630851761cb464fbb38cf75a8ee8f5b22ac3 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.129290.1631612100032%40Atlassian.JIRA.
Jira (PUP-11162) Update Public-facing Puppet docs to include Ubuntu 18.04 (aarch64)
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-11162 Update Public-facing Puppet docs to include Ubuntu 18.04 (aarch64) Change By: Gabriel Nagy 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.406067.1625647018000.113562.1629719880028%40Atlassian.JIRA.
Jira (PUP-11162) Update Public-facing Puppet docs to include Ubuntu 18.04 (aarch64)
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-11162 Update Public-facing Puppet docs to include Ubuntu 18.04 (aarch64) Change By: Gabriel Nagy Fix Version/s: PUP 7.11.0 Fix Version/s: PUP 6.25.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.406067.1625647018000.113561.1629719820313%40Atlassian.JIRA.
Jira (PUP-10890) lookup fails if module lookup_options are empty
Title: Message Title Gabriel Nagy commented on PUP-10890 Re: lookup fails if module lookup_options are empty Merged to 6.x in https://github.com/puppetlabs/puppet/commit/284f3d6bc6432f355e71a177f7a2d554bb879d65 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.386484.1612558652000.112712.1629450180314%40Atlassian.JIRA.
Jira (PUP-10105) regression: puppet resource --to_yaml should not emit puppet class tags
Title: Message Title Gabriel Nagy commented on PUP-10105 Re: regression: puppet resource --to_yaml should not emit puppet class tags For types subclassing String this was merged in https://github.com/puppetlabs/puppet/commit/bb79ad063382f4055fa77a46039e3441326a82af I'm not sure if we should handle the other pops changes in this ticket or create another one. 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.329731.1571238944000.112679.1629449640103%40Atlassian.JIRA.
Jira (PUP-6708) Agent does not save local copy of last_run_report.yaml if submission to report server fails
Title: Message Title Gabriel Nagy commented on PUP-6708 Re: Agent does not save local copy of last_run_report.yaml if submission to report server fails Merged to 6.x in https://github.com/puppetlabs/puppet/commit/6b109de27fe2861e1b21e9e36f708de387c2ac6c 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.152161.1473975634000.111991.1629377640029%40Atlassian.JIRA.
Jira (PUP-11208) Puppet fails to install packages on Solaris if another pkg install is running
Title: Message Title Gabriel Nagy created an issue Puppet / PUP-11208 Puppet fails to install packages on Solaris if another pkg install is running Issue Type: Bug Assignee: Unassigned Created: 2021/08/19 4:17 AM Priority: Normal Reporter: Gabriel Nagy Puppet fails hard if it tries to install a package on Solaris 11 while a pkg install command is already running in the background. pkg install fails with the following error: root@initial-holdup:~# pkg install nano pkg: The image cannot be modified as it is currently in use by another package client. root@initial-holdup:~# echo $? 7 The same error can be reproduced in a zone set up, if you execute pkg install something concurrently on global and the zone (the following output is from a puppet manifest with the nano package resource):
Jira (FACT-3063) Facter unable to get processor speed on macOS 11 arm64 which causes the resolver to blow up
Title: Message Title Gabriel Nagy updated an issue Facter / FACT-3063 Facter unable to get processor speed on macOS 11 arm64 which causes the resolver to blow up Change By: Gabriel Nagy Summary: Facter unable to get processor speed on OS macOS 11 arm64 which causes the resolver to blow up Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.409868.1628076333000.111841.1629356220032%40Atlassian.JIRA.
Jira (FACT-3057) Facter ruby API/binding fails to resolve facts from environment variables
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Facter / FACT-3057 Facter ruby API/binding fails to resolve facts from environment variables Change By: Gabriel Nagy 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.408355.1627027953000.107874.1629105960041%40Atlassian.JIRA.
Jira (PUP-11201) Refine when the last used environment is used
Title: Message Title Gabriel Nagy commented on PUP-11201 Re: Refine when the last used environment is used Merged to 6.x in https://github.com/puppetlabs/puppet/commit/500e5144702b7ebbccb3ae70a4c6033f3d8cd9b4 Additional test fix was merged to 6.x in https://github.com/puppetlabs/puppet/commit/c13689d9dfda6e125d0d66c5ab278bb2e530dd22 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.410096.1628208242000.106085.1628744400068%40Atlassian.JIRA.
Jira (FACT-3062) implement snyk Code Scanning for ruby facter
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Facter / FACT-3062 implement snyk Code Scanning for ruby facter Change By: Gabriel Nagy 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.409863.1628070635000.105087.1628681040035%40Atlassian.JIRA.
Jira (PUP-11201) Refine when the last used environment is used
Title: Message Title Gabriel Nagy commented on PUP-11201 Re: Refine when the last used environment is used That's the correct (new) behavior, work for that was done in https://tickets.puppetlabs.com/browse/PUP-6802 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.410096.1628208242000.103477.1628535240040%40Atlassian.JIRA.
Jira (PUP-11201) Refine when the last used environment is used
Title: Message Title Gabriel Nagy commented on PUP-11201 Re: Refine when the last used environment is used I opened a PR with the suggested changes here: https://github.com/puppetlabs/puppet/pull/8733 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.410096.1628208242000.103164.1628522340031%40Atlassian.JIRA.
Jira (PUP-9997) Puppet must not call Dir.chdir() except in a child process
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-9997 Puppet must not call Dir.chdir() except in a child process Change By: Gabriel Nagy Sprint: NW-2021-08-11 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.323575.156763800.103125.1628520840097%40Atlassian.JIRA.
Jira (PUP-9997) Puppet must not call Dir.chdir() except in a child process
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-9997 Puppet must not call Dir.chdir() except in a child process Change By: Gabriel Nagy Sprint: ready for triage 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.323575.156763800.103126.1628520840140%40Atlassian.JIRA.
Jira (PUP-11201) Refine when the last used environment is used
Title: Message Title Gabriel Nagy commented on PUP-11201 Re: Refine when the last used environment is used Previous behavior (before we removed the node request) was to skip the node request if a cached catalog/catalog is given, or if strict_environment_mode is true. So the node request was always performed regardless of the CLI/config value for environment Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.410096.1628208242000.102860.1628502840169%40Atlassian.JIRA.
Jira (PUP-11201) Refine when the last used environment is used
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-11201 Refine when the last used environment is used Change By: Gabriel Nagy 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.410096.1628208242000.102829.1628502060046%40Atlassian.JIRA.
Jira (PUP-11199) Document exec type's 'onlyif' and 'unless' commands behavior with --noop
Title: Message Title
Gabriel Nagy updated an issue
Puppet / PUP-11199
Document exec type's 'onlyif' and 'unless' commands behavior with --noop
Change By:
Gabriel Nagy
Taken from: https://groups.google.com/g/puppet-users/c/axT5CfVNDXUThe {{ -- noop}} flag tells Puppet to determine which resources are out of sync, and to report them without actually synchronizing them. The 'onlyif' and 'unless' commands of an Exec are used in the process of determining whether the Exec is already in sync, therefore they must be run during a {{--noop}} Puppet run. The synchronization of an out-of-sync Exec resource involves only running the command given by its 'command' property, so that's the only part that {{--noop}} prevents. Up until https://github.com/puppetlabs/puppet/commit/c127bcb1f6b3d0a0e7b9122352162528fbb65b6c {{onlyif}} and {{unless}} commands did not run in the specified {{cwd}}, which might have given the wrong impression that {{noop}} also applies to those parameters. Applying something like the following manifest would have worked prior to that commit:{code}exec { "hello world": cwd => '/home/gabi/tmp/abc', command => "/bin/echo hello world", _onlyif_ => "/bin/test -e asd",}{code}After puppet 5.5.7 applying the manifest above with {{--noop}} fails with the following error (provided that the cwd does not exist):{code}Error: /Stage[main]/Main/Exec[hello world]: Could not evaluate: Working directory /home/gabi/tmp/abc does not exist!{code}This is expected behavior since {{noop}} does not prevent {{onlyif}} and {{unless}} from being run. We should document this behavior.
Add Comment
Jira (PUP-11199) Document exec type's 'onlyif' and 'unless' commands behavior with --noop
Title: Message Title
Gabriel Nagy updated an issue
Puppet / PUP-11199
Document exec type's 'onlyif' and 'unless' commands behavior with --noop
Change By:
Gabriel Nagy
Taken from: https://groups.google.com/g/puppet-users/c/axT5CfVNDXUThe {{--noop}} flag tells Puppet to determine which resources are out of sync, and to report them without actually synchronizing them. The 'onlyif' and 'unless' commands of an Exec are used in the process of determining whether the Exec is already in sync, therefore they must be run during a {{--noop}} Puppet run. The synchronization of an out-of-sync Exec resource involves only running the command given by its 'command' property, so that's the only part that {{--noop}} prevents. Up until https://github.com/puppetlabs/puppet/commit/c127bcb1f6b3d0a0e7b9122352162528fbb65b6c {{onlyif}} and {{unless}} commands did not run in the specified {{cwd}}, which might have given the wrong impression that {{noop}} also applies to those parameters. Applying something like the following manifest would have worked prior to that commit:{code}exec { "hello world": cwd => '/home/gabi/tmp/abc', command => "/bin/echo hello world", _onlyif_ => "/bin/test -e asd",}{code}After puppet 5.5.7 applying the manifest above with {{--noop}} fails with the following error (provided that the cwd does not exist):{code}Error: /Stage[main]/Main/Exec[hello world]: Could not evaluate: Working directory /home/gabi/tmp/abc does not exist!{code}This is expected behavior since {{noop}} does not prevent {{onlyif}} and {{unless}} from being run. We should document this behavior.
Add Comment
Jira (PUP-11199) Document exec type's 'onlyif' and 'unless' commands behavior with --noop
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-11199 Document exec type's 'onlyif' and 'unless' commands behavior with --noop Change By: Gabriel Nagy 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.410026.1628169495000.100058.1628169540230%40Atlassian.JIRA.
Jira (PUP-11199) Document exec type's 'onlyif' and 'unless' commands behavior with --noop
Title: Message Title Gabriel Nagy created an issue Puppet / PUP-11199 Document exec type's 'onlyif' and 'unless' commands behavior with --noop Issue Type: Improvement Assignee: Unassigned Created: 2021/08/05 6:18 AM Priority: Normal Reporter: 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
Jira (PUP-9997) Puppet must not call Dir.chdir() except in a child process
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-9997 Puppet must not call Dir.chdir() except in a child process Change By: Gabriel Nagy 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.323575.156763800.99902.1628154900073%40Atlassian.JIRA.
Jira (PUP-11198) Directoryservice user provider unable to deserialize XML ShadowHashData plists
Title: Message Title Gabriel Nagy commented on PUP-11198 Re: Directoryservice user provider unable to deserialize XML ShadowHashData plists facepalm yes, looks like I commented on that one an eternity ago; closing this as a dup 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.409913.1628090453000.99863.1628140080034%40Atlassian.JIRA.
Jira (PUP-11198) Directoryservice user provider unable to deserialize XML ShadowHashData plists
Title: Message Title
Gabriel Nagy created an issue
Puppet / PUP-11198
Directoryservice user provider unable to deserialize XML ShadowHashData plists
Issue Type:
Bug
Assignee:
Unassigned
Created:
2021/08/04 8:20 AM
Priority:
Normal
Reporter:
Gabriel Nagy
Puppet Version: reproduced with latest nightly (7.9.0.something) Puppet Server Version: n/a OS Name/Version: macOS 11 (probably others as well) An user with an embedded XML ShadowHashData plist will fail to parse correctly. The current directoryservice logic always expects embedded binary plists: https://github.com/puppetlabs/puppet/blob/9d0de43eefce442c7a329075aea9700b449f5987/lib/puppet/provider/user/directoryservice.rb#L148 failing object:
[11] pry(directoryservice)> attribute_hash
=> {:guid=>"0DCC37EC-F153-4225-A24F-A9C402B7EAE4",
:home=>"/Users/it-admin",
:password=>"",
:gid=>20,
Jira (FACT-3063) Facter unable to get processor speed on OS 11 arm64 which causes the resolver to blow up
Title: Message Title
Gabriel Nagy updated an issue
Facter / FACT-3063
Facter unable to get processor speed on OS 11 arm64 which causes the resolver to blow up
Change By:
Gabriel Nagy
Facter queries the following items on macOS using sysctl:{code:java}ITEMS = { logical_count: 'hw.logicalcpu_max', physical_count: 'hw.physicalcpu_max', brand: 'machdep.cpu.brand_string', speed: 'hw.cpufrequency_max', cores_per_socket: 'machdep.cpu.core_count', threads_per_core: 'machdep.cpu.thread_count' }.freeze {code}The outputs get passed like this to {{build_fact_list}}:{code} def build_fact_list(processors_data)build_logical_count(processors_data[0])build_physical_count(processors_data[1])build_models(processors_data[2])build_speed(processors_data[3])build_cores_per_socket(processors_data[4])build_threads_per_core(processors_data[5], processors_data[4]) end{code}The problem surfaces when {{processors_data}} is missing one of the outputs from {{ITEMS}} and methods end up being called with {{nil}}.In our case {{hw.cpufrequency_max}} is empty so the entire {{processors_data}} output is shifted and one element short.We need to ensure the resolver works even if not all sysctl queries resolve; and fix the processor speed fact (if possible). Resolver in question: https://github.com/puppetlabs/facter/blob/main/lib/facter/resolvers/macosx/processor.rb (nit: the filename should be processors not processor)
Add Comment
Jira (FACT-3063) Facter unable to get processor speed on OS 11 arm64 which causes the resolver to blow up
Title: Message Title
Gabriel Nagy created an issue
Facter / FACT-3063
Facter unable to get processor speed on OS 11 arm64 which causes the resolver to blow up
Issue Type:
Bug
Affects Versions:
FACT 4.2.2
Assignee:
Unassigned
Created:
2021/08/04 4:25 AM
Priority:
Normal
Reporter:
Gabriel Nagy
Facter queries the following items on macOS using sysctl:
ITEMS = { logical_count: 'hw.logicalcpu_max',
physical_count: 'hw.physicalcpu_max',
brand: 'machdep.cpu.brand_string',
speed: 'hw.cpufrequency_max',
cores_per_socket: 'machdep.cpu.core_count',
Jira (PUP-10926) Cloudinit support for Puppet 6 onwards
Title: Message Title Gabriel Nagy commented on PUP-10926 Re: Cloudinit support for Puppet 6 onwards Opened a PR with the suggested changes here: https://github.com/canonical/cloud-init/pull/960 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.387968.1613669787000.98742.1628068020031%40Atlassian.JIRA.
Jira (PUP-10216) Failure to fetch node definition may result in bad pluginsync and cascading failure
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-10216 Failure to fetch node definition may result in bad pluginsync and cascading failure Change By: Gabriel Nagy Release Notes: Enhancement Release Notes Summary: Previously, Puppet agents would make a node definition request to the server in order to find out the correct environment to run in. This request has now been removed, and the agent now saves its last used environment in the `last_run_summary.yaml` file. If the environment is not specifically set via CLI or config, agents will attempt to use the environment in `last_run_summary.yaml`. 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-10926) Cloudinit support for Puppet 6 onwards
Title: Message Title Gabriel Nagy commented on PUP-10926 Re: Cloudinit support for Puppet 6 onwards Hey Steve Shipway, I'm working on updating the cloud-init puppet module, here's what I have until now https://github.com/canonical/cloud-init/compare/main...GabrielNagy:puppet-module-updates?expand=1 Update cc_puppet.py as shipped with the various distros to use Puppet6 as a default configuration. This might be hard to get pushed out though This should be done, however I decided to default to puppet7 since that is the newest release stream that we support (this setting is now configurable via the collection key). The Ubuntu cloud images seem to be updated once every few months with the latest cloud-init code, so I think this will be achievable. Allow all puppet.conf settings to be set via the puppet cloud-init configuration From what I have tested this is already possible via the conf key. Let me know if I'm missing anything. Add an option to allow an immediate puppet run to be scheduled This should be done and can be achieved by setting exec to true. Default puppet agent arguments can be overridden with the exec_args key. Update documentation to show the above method to make cc_puppet.py work with puppet 6 Documentation should be updated in the branch above. I added more configurable settings so it would be great if you could take a look and let me know what you think. I have validated the module manually, next steps are to update the unit tests and submit a PR. Add Comment
Jira (FACT-3058) Add DisplayVersion fact for Windows machines
Title: Message Title Gabriel Nagy commented on FACT-3058 Re: Add DisplayVersion fact for Windows machines Windows Server seems to share build numbers with Windows 10 so I assume yes https://docs.microsoft.com/en-us/windows-server/get-started/windows-server-release-info 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.96265.1627915260163%40Atlassian.JIRA.
Jira (PUP-11172) undefined method `[]' for nil:NilClass when handling SemanticPuppet::Dependency::UnsatisfiableGraph
Title: Message Title Gabriel Nagy commented on PUP-11172 Re: undefined method `[]' for nil:NilClass when handling SemanticPuppet::Dependency::UnsatisfiableGraph Merged to 6.x in https://github.com/puppetlabs/puppet/commit/3d23ac76122a248827e3e9e56cdf7a57ad61b141 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.407578.1626862586000.95707.1627893660025%40Atlassian.JIRA.
Jira (PUP-10926) Cloudinit support for Puppet 6 onwards
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-10926 Cloudinit support for Puppet 6 onwards Change By: Gabriel Nagy 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.387968.1613669787000.93748.1627549080041%40Atlassian.JIRA.
Jira (FACT-3058) Add DisplayVersion fact for Windows machines
Title: Message Title Gabriel Nagy created an issue Facter / FACT-3058 Add DisplayVersion fact for Windows machines Issue Type: New Feature Assignee: Unassigned Created: 2021/07/28 4:05 AM Labels: community Priority: Normal Reporter: Gabriel Nagy Context from https://www.lansweeper.com/forum/yaf_postsm65291_Windows-10-Version-Number-Wrong.aspx#post65291 Microsoft has changed the identifier in the registry for the version number. "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ReleaseID" is the old location for the version number, 1803, 1909 and such. "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DisplayVersion" is now the new location as of 2009 (20H2) but does not exist prior to 2009. The issue I have seen is that they stopped at 2009 and did not remove the old entry when they decided to create the new one. This means there is an old entry of 2009 still in the registry. Also discussed on the Community Slack: https://puppetcommunity.slack.com/archives/C0W298S9G/p1627455331127400 Facter currently provides both the build number and release ID as core facts (os.windows.release_id and kernelversion). What we need to do: add a new os.windows.display_version fact that reads the version from the DisplayVersion registry key based on the build version, make the existing release_id fact point to display_version and the other way around (this is to keep backwards compatibility and avoid breaking existing installations)
Jira (PUP-10216) Failure to fetch node definition may result in bad pluginsync and cascading failure
Title: Message Title Gabriel Nagy commented on PUP-10216 Re: Failure to fetch node definition may result in bad pluginsync and cascading failure Re-merged to 6.x in https://github.com/puppetlabs/puppet/commit/0112c68f31eb69c59697ac5fcdcd9c474600245d 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.341077.1578089491000.91287.1627396680024%40Atlassian.JIRA.
Jira (PUP-10820) Binary, Sensitive, etc deferred results can corrupt the transaction store
Title: Message Title Gabriel Nagy commented on PUP-10820 Re: Binary, Sensitive, etc deferred results can corrupt the transaction store Merged to 6.x in https://github.com/puppetlabs/puppet/commit/32f0d253309e44cf3a2cf189b9f7cf02d6229435 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.380578.1607562201000.91286.1627396620029%40Atlassian.JIRA.
Jira (PUP-11168) Add RHEL9 support for services
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-11168 Add RHEL9 support for services Change By: Gabriel Nagy Community Contributors: mwhahaha 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.406565.1626118192000.86354.1626873840039%40Atlassian.JIRA.
Jira (PUP-11164) launchd service provider fails if a parsable but invalid LaunchAgent or LaunchDaemon plist file exists
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-11164 launchd service provider fails if a parsable but invalid LaunchAgent or LaunchDaemon plist file exists Change By: Gabriel Nagy Community Contributors: ccaviness 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.406437.1625784567000.86353.1626873780094%40Atlassian.JIRA.
Jira (PUP-11171) "Server Error: no parameter named 'max_files'", when adding max_files to file resource
Title: Message Title Gabriel Nagy commented on PUP-11171 Re: "Server Error: no parameter named 'max_files'", when adding max_files to file resource Hi Dirk Heinrichs, My assumption is that this happens because the agent version on your primary server (which handles the catalog compilation) is older and doesn't have the max_files feature. That work (PUP-10946) went in 6.23.0 so it's available on the agent, which is why you're seeing the warning. Can you confirm that this is the case? To be able to set the parameter in the manifest you need at least Puppet 6.23.0 on your server node. 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.407573.1626851976000.86194.1626860220033%40Atlassian.JIRA.
Jira (PUP-8243) Allow ERB templates to be tolerant of a leading BOM
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-8243 Allow ERB templates to be tolerant of a leading BOM Change By: Gabriel Nagy Release Notes: Enhancement Release Notes Summary: Previously, if a template contained a BOM, then it was preserved by the `template` function, and would end up in the resulting file or PowerShell command. Now we pass the `bom` option when reading the file, which strips the BOM as it is read. 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.226260.151309316.76996.1625751420030%40Atlassian.JIRA.
Jira (PUP-10216) Failure to fetch node definition may result in bad pluginsync and cascading failure
Title: Message Title Gabriel Nagy commented on PUP-10216 Re: Failure to fetch node definition may result in bad pluginsync and cascading failure Opened a revert PR https://github.com/puppetlabs/puppet/pull/8679 See the description for more context, in short it'd be good to get PUP-6802 and PUP-9570 in prior to this, so we minimize possible breakage. 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.341077.1578089491000.73931.1625567340150%40Atlassian.JIRA.
Jira (FACT-3054) clean_up_interfaces_response in lib/facter/resolvers/networking.rb should also handle IPv6
Title: Message Title Gabriel Nagy commented on FACT-3054 Re: clean_up_interfaces_response in lib/facter/resolvers/networking.rb should also handle IPv6 Merged to main in https://github.com/puppetlabs/facter/commit/003ed6663c0e5ad2b4257e3d95e2d208d38eb95e 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.405222.1625075497000.73552.1625486460089%40Atlassian.JIRA.
Jira (PUP-10641) Puppet Module Tool gives unhelpful error message for bad module name
Title: Message Title Gabriel Nagy commented on PUP-10641 Re: Puppet Module Tool gives unhelpful error message for bad module name Merged to 6.x in https://github.com/puppetlabs/puppet/commit/61f5aa9894868711adaca3cb07cf43d54122f842 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.59877.1417031796000.65919.1624605300032%40Atlassian.JIRA.
Jira (PUP-10216) Failure to fetch node definition may result in bad pluginsync and cascading failure
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-10216 Failure to fetch node definition may result in bad pluginsync and cascading failure Change By: Gabriel Nagy 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.341077.1578089491000.63528.1624452420038%40Atlassian.JIRA.
Jira (PUP-11120) Readd the ability to load custom OIDs
Title: Message Title Gabriel Nagy commented on PUP-11120 Re: Readd the ability to load custom OIDs Merged to 6.x in https://github.com/puppetlabs/puppet/commit/8e1ded9301b7cd928609f0e260eeebaa83aa4b3d 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.403880.1623888725000.62114.1624368240032%40Atlassian.JIRA.
Jira (PUP-6554) Can't run puppet resource on agent with environment specified in main section
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-6554 Can't run puppet resource on agent with environment specified in main section Change By: Gabriel Nagy 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.143699.1469626368000.59531.1623947220077%40Atlassian.JIRA.
Jira (PUP-11079) Setting age=0 on a tidy resource does not remove all files
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-11079 Setting age=0 on a tidy resource does not remove all files Change By: Gabriel Nagy Release Notes: Bug Fix Release Notes Summary: Previously, the `age` parameter of the `tidy` resource did not work according to the documentation and only removed files older than the specified time. Now it removes files whose age is equal to or greater than the specified time. 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.401529.1622726494000.59224.1623935160040%40Atlassian.JIRA.
Jira (PUP-6801) agent_specified_environment fact doesn't populate with the environment setting in the [agent] section
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-6801 agent_specified_environment fact doesn't populate with the environment setting in the [agent] section Change By: Gabriel Nagy 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.155635.1475796831000.58013.1623856200162%40Atlassian.JIRA.
Jira (PUP-11079) Setting age=0 on a tidy resource does not remove all files
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-11079 Setting age=0 on a tidy resource does not remove all files Change By: Gabriel Nagy 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.401529.1622726494000.57989.1623854580028%40Atlassian.JIRA.
Jira (PUP-10796) puppet filebucket fails when using non-default environment from master
Title: Message Title Gabriel Nagy commented on PUP-10796 Re: puppet filebucket fails when using non-default environment from master Merged to 6.x in https://github.com/puppetlabs/puppet/commit/b5fb1dff0ca31f1d5d720a5c1e7eb11cefcaac28 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.379509.160685450.57951.1623852960095%40Atlassian.JIRA.
Jira (PUP-7493) The 'desired_value' as File mode is reported without leading zeros
Title: Message Title Gabriel Nagy commented on PUP-7493 Re: The 'desired_value' as File mode is reported without leading zeros Merged to 6.x in https://github.com/puppetlabs/puppet/commit/123dfd2f28adcd11155075f8f774b7f5ae7be039 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.189040.1493819823000.56472.1623739680054%40Atlassian.JIRA.
Jira (PUP-7493) The 'desired_value' as File mode is reported without leading zeros
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-7493 The 'desired_value' as File mode is reported without leading zeros Change By: Gabriel Nagy Fix Version/s: PUP 7.9.0 Fix Version/s: PUP 6.24.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.189040.1493819823000.56473.1623739680112%40Atlassian.JIRA.
Jira (PUP-4884) PMT won't install a module on windows if module_working_dir contains backslashes
Title: Message Title Gabriel Nagy commented on PUP-4884 Re: PMT won't install a module on windows if module_working_dir contains backslashes Merged to main in https://github.com/puppetlabs/puppet/commit/46e4ec1b01c0ef1577d387043d92756508ba5333 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.89342.1436984308000.54691.1623422760025%40Atlassian.JIRA.
Jira (PUP-11049) Ruby 3 changes default external encoding on Windows
Title: Message Title Gabriel Nagy commented on PUP-11049 Re: Ruby 3 changes default external encoding on Windows Merged to main in https://github.com/puppetlabs/puppet/commit/d6ca71dc40145a12c3f798cc526f5ca4e0055b3b 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.397714.1619738481000.54690.1623422700102%40Atlassian.JIRA.
Jira (PUP-10974) service enable=mask fails when service isn't present
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-10974 service enable=mask fails when service isn't present Change By: Gabriel Nagy Fix Version/s: PUP 7.8.0 Fix Version/s: PUP 6.23.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.392819.1616696402000.51882.1623225420032%40Atlassian.JIRA.
Jira (PUP-10974) service enable=mask fails when service isn't present
Title: Message Title Gabriel Nagy commented on PUP-10974 Re: service enable=mask fails when service isn't present Merged to 6.x in https://github.com/puppetlabs/puppet/commit/39461d5c51a78fb9531fa307630826620cbfbaaa 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.392819.1616696402000.51881.1623225300029%40Atlassian.JIRA.
Jira (PUP-11077) Passing SemVer prerelease or build as a hash doesn't work
Title: Message Title Gabriel Nagy updated an issue Puppet / PUP-11077 Passing SemVer prerelease or build as a hash doesn't work Change By: Gabriel Nagy Fix Version/s: PUP 6.23.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.401381.162258715.51094.1623159060096%40Atlassian.JIRA.
