Jira (PUP-7312) Confine systemd provider to init system matching systemd
Title: Message Title Robert August Vincent II commented on PUP-7312 Re: Confine systemd provider to init system matching systemd Any reason this is still languishing? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.178941.1488893881000.6695.1562341920250%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9814) pxp-agent.conf file missing Administrators rights when puppet agent run as SYSTEM
Title: Message Title John O'Connor assigned an issue to Unassigned Puppet / PUP-9814 pxp-agent.conf file missing Administrators rights when puppet agent run as SYSTEM Change By: John O'Connor Assignee: John O'Connor Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315397.1562338786000.6685.1562338816072%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9814) pxp-agent.conf file missing Administrators rights when puppet agent run as SYSTEM
Title: Message Title John O'Connor created an issue Puppet / PUP-9814 pxp-agent.conf file missing Administrators rights when puppet agent run as SYSTEM Issue Type: Bug Affects Versions: PUP 6.4.2 Assignee: John O'Connor Created: 2019/07/05 7:59 AM Priority: Major Reporter: John O'Connor Puppet Version: 6.4.2 Puppet Server Version: N/A OS Name/Version: Windows Server 2016 x64 This is a follow on issue from PUP-9719 to deal with the specific file pxp-agent.conf. Although the main work for PUP-9719 appears to correct the permissions/rights issue for the cache files additional work is needed to resolve the issue for C:\ProgramData/PuppetLabs/pxp-agent/etc/pxp-agent.conf Desired Behavior: Puppet Agent should run without error under Administrator Actual Behavior: Running the Puppet Agent command as Administrator gives the following result PS C:\Users\Administrator> puppet agent -t Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin
Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System
Title: Message Title
John O'Connor updated an issue
Puppet / PUP-9719
Cannot run Puppet Agent as Administrator if first PA run is done as System
Change By:
John O'Connor
*Puppet Version:* 6.4.2 *Puppet Server Version:* N/A *OS Name/Version:* Windows Server 2016 x64When installing Puppet Agent (6.4.2/PE 2019.1.0) on Server 2016 using a Powershell script running as the SYSTEM account, Administrator users can't run Puppet. Daemon/service runs are performed as expected. Direct Puppet runs appear to occur but no report is sent to the master. *UPDATE* - It the first Run as SYSTEM that is the problem - so have changed ticket title.PUP-8939 had reportedly solved this issue.*Desired Behavior:**note* - so far, this can only be replicated using scheduled tasks as {{psexec}} doesn't provide the same permissions environment : # Install: {{schtasks /create /tn PuppetInstall /RL HIGHEST /RU SYSTEM /F /SC ONCE /ST 11:15 /TR 'cmd /c c:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe -sta -WindowStyle Hidden -ExecutionPolicy Bypass -NonInteractive -NoProfile -File c:\puppet.ps1 >> C:\windows\temp\puppet-ins.log 2>&1'}} # Run PA {{schtasks /create /tn PuppetInstall /RL HIGHEST /RU SYSTEM /F /SC ONCE /ST 11:17 /TR 'cmd /c c:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe -sta -WindowStyle Hidden -ExecutionPolicy Bypass -NonInteractive -NoProfile -File c:\puppetrun.ps1 >> C:\windows\temp\puppet-run.log 2>&1'}} # Populate csr_attributes.yml and {{server}} in the agent config as necessary. # As an Administrator, run {{puppet agent --test}} on the newly installed agent. See [https://gist.github.com/jcoconnor/79767ef986a3ec600de0cd84ec4ea600] for example {{puppet-ins.ps1}} and {{puppet-run.ps1}} scripts. *Actual Behavior:*Catalog retrieval fails; log has been redacted:{code}2019-05-21 17:20:36 -0400 Puppet (debug): HTTP POST https://compiler.example.net:8140/puppet/v3/catalog/examplenode.example.net returned 200 OK2019-05-21 17:20:36 -0400 Puppet (debug): Caching connection for https://compiler.example.net:81402019-05-21 17:20:36 -0400 Puppet (info): Caching catalog for examplenode.example.net2019-05-21 17:20:38 -0400 Puppet (err): ReplaceFile(C:/ProgramData/PuppetLabs/puppet/cache/client_data/catalog/examplenode.example.net.json, C:/ProgramData/PuppetLabs/puppet/cache/client_data/catalog/examplenode.example.net.json20190521-6580-blokpv): Access is denied. c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/file.rb:89:in `replace_file'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util.rb:636:in `replace_file'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/indirector/json.rb:17:in `save'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:200:in `find'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:466:in `block in retrieve_new_catalog'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util.rb:518:in `block in thinmark'c:/P
Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System
Title: Message Title
John O'Connor updated an issue
Puppet / PUP-9719
Cannot run Puppet Agent as Administrator if first PA run is done as System
Change By:
John O'Connor
*Puppet Version:* 6.4.2 *Puppet Server Version:* N/A *OS Name/Version:* Windows Server 2016 x64When installing Puppet Agent (6.4.2/PE 2019.1.0) on Server 2016 using a Powershell script running as the SYSTEM account, Administrator users can't run Puppet. Daemon/service runs are performed as expected. Direct Puppet runs appear to occur but no report is sent to the master. *UPDATE* - It the first Run as SYSTEM that is the problem - so have changed ticket title.PUP-8939 had reportedly solved this issue.*Desired Behavior:**note* - so far, this can only be replicated using scheduled tasks as {{psexec}} doesn't provide the same permissions environment : 1. # Install: {{schtasks /create /tn PuppetInstall /RL HIGHEST /RU SYSTEM /F /SC ONCE /ST 11:15 /TR 'cmd /c c:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe -sta -WindowStyle Hidden -ExecutionPolicy Bypass -NonInteractive -NoProfile -File c:\puppet.ps1 >> C:\windows\temp\puppet-ins.log 2>&1'}} 2. # Run PA {{schtasks /create /tn PuppetInstall /RL HIGHEST /RU SYSTEM /F /SC ONCE /ST 11:17 /TR 'cmd /c c:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe -sta -WindowStyle Hidden -ExecutionPolicy Bypass -NonInteractive -NoProfile -File c:\puppetrun.ps1 >> C:\windows\temp\puppet-run.log 2>&1'}} 1. Download the Agent 6.4.2 x64 MSI to a temp path (in this example, {{C:\temp\puppet\puppet-agent-x64.msi}}). 2. Install Puppet Agent on a Server 2016 node as the SYSTEM user by running {{start-process -filepath "msiexec.exe" -arg "/qn /norestart /l*v C:\windows\temp\puppetinstall.log /i c:\temp\puppet\puppet-agent-x64.msi PUPPET_AGENT_STARTUP_MODE=Manual" -Wait}} 3. # Populate csr_attributes.yml and {{server}} in the agent config as necessary. 4. # As an Administrator, run {{puppet agent --test}} on the newly installed agent. *Actual Behavior:*Catalog retrieval fails; log has been redacted:{code}2019-05-21 17:20:36 -0400 Puppet (debug): HTTP POST https://compiler.example.net:8140/puppet/v3/catalog/examplenode.example.net returned 200 OK2019-05-21 17:20:36 -0400 Puppet (debug): Caching connection for https://compiler.example.net:81402019-05-21 17:20:36 -0400 Puppet (info): Caching catalog for examplenode.example.net2019-05-21 17:20:38 -0400 Puppet (err): ReplaceFile(C:/ProgramData/PuppetLabs/puppet/cache/client_data/catalog/examplenode.example.net.json, C:/ProgramData/PuppetLabs/puppet/cache/client_data/catalog/examplenode.example.net.json20190521-6580-blokpv): Access is denied. c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/file.rb:89:in `replace_file'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util.rb:636:in `replace_file'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/indirector/json.rb:17:in `save'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/indirector/indir
Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System
Title: Message Title
John O'Connor updated an issue
Puppet / PUP-9719
Cannot run Puppet Agent as Administrator if first PA run is done as System
Change By:
John O'Connor
*Puppet Version:* 6.4.2 *Puppet Server Version:* N/A *OS Name/Version:* Windows Server 2016 x64When installing Puppet Agent (6.4.2/PE 2019.1.0) on Server 2016 using a Powershell script running as the SYSTEM account, Administrator users can't run Puppet. Daemon/service runs are performed as expected. Direct Puppet runs appear to occur but no report is sent to the master. *UPDATE* - It the first Run as SYSTEM that is the problem - so have changed ticket title.PUP-8939 had reportedly solved this issue.*Desired Behavior:**note* - so far, this can only be replicated using scheduled tasks as {{psexec}} doesn't provide the same permissions environment :1. Install: TBD {{schtasks /create /tn PuppetInstall /RL HIGHEST /RU SYSTEM /F /SC ONCE /ST 11:15 /TR 'cmd /c c:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe -sta -WindowStyle Hidden -ExecutionPolicy Bypass -NonInteractive -NoProfile -File c:\puppet.ps1 >> C:\windows\temp\puppet-ins.log 2>&1'}} 2. Run PA {{ TBD schtasks /create /tn PuppetInstall /RL HIGHEST /RU SYSTEM /F /SC ONCE /ST 11:17 /TR 'cmd /c c:\WINDOWS\system32\WindowsPowerShell\v1.0\powershell.exe -sta -WindowStyle Hidden -ExecutionPolicy Bypass -NonInteractive -NoProfile -File c:\puppetrun.ps1 >> C:\windows\temp\puppet-run.log 2>&1' }} 1. Download the Agent 6.4.2 x64 MSI to a temp path (in this example, {{C:\temp\puppet\puppet-agent-x64.msi}}). 2. Install Puppet Agent on a Server 2016 node as the SYSTEM user by running {{start-process -filepath "msiexec.exe" -arg "/qn /norestart /l*v C:\windows\temp\puppetinstall.log /i c:\temp\puppet\puppet-agent-x64.msi PUPPET_AGENT_STARTUP_MODE=Manual" -Wait}} 3. Populate csr_attributes.yml and {{server}} in the agent config as necessary. 4. As an Administrator, run {{puppet agent --test}} on the newly installed agent.*Actual Behavior:*Catalog retrieval fails; log has been redacted:{code}2019-05-21 17:20:36 -0400 Puppet (debug): HTTP POST https://compiler.example.net:8140/puppet/v3/catalog/examplenode.example.net returned 200 OK2019-05-21 17:20:36 -0400 Puppet (debug): Caching connection for https://compiler.example.net:81402019-05-21 17:20:36 -0400 Puppet (info): Caching catalog for examplenode.example.net2019-05-21 17:20:38 -0400 Puppet (err): ReplaceFile(C:/ProgramData/PuppetLabs/puppet/cache/client_data/catalog/examplenode.example.net.json, C:/ProgramData/PuppetLabs/puppet/cache/client_data/catalog/examplenode.example.net.json20190521-6580-blokpv): Access is denied. c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/file.rb:89:in `replace_file'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util.rb:636:in `replace_file'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/indirector/json.rb:17:in `save'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb
Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System
Title: Message Title
John O'Connor updated an issue
Puppet / PUP-9719
Cannot run Puppet Agent as Administrator if first PA run is done as System
Change By:
John O'Connor
*Puppet Version:* 6.4.2 *Puppet Server Version:* N/A *OS Name/Version:* Windows Server 2016 x64When installing Puppet Agent (6.4.2/PE 2019.1.0) on Server 2016 using a Powershell script running as the SYSTEM account, Administrator users can't run Puppet. Daemon/service runs are performed as expected. Direct Puppet runs appear to occur but no report is sent to the master. *UPDATE* - It the first Run as SYSTEM that is the problem - so have changed ticket title.PUP-8939 had reportedly solved this issue.*Desired Behavior:**note* - so far, this can only be replicated using scheduled tasks as {{psexec}} doesn't provide the same permissions environment :1. Install: {{psexec -s -i "msiexec.exe" /qn /norestart /l*v C:\windows\temp\puppetinstall.log /i C:\Users\Administrator\Downloads\puppet-agent-6.4.2-x64.msi PUPPET_AGENT_STARTUP_MODE=Manual}} TBD 2. Run PA {{ psexec -s "C:\Program Files\Puppet Labs\Puppet\bin\puppet.bat" agent -t TBD }} 1. Download the Agent 6.4.2 x64 MSI to a temp path (in this example, {{C:\temp\puppet\puppet-agent-x64.msi}}). 2. Install Puppet Agent on a Server 2016 node as the SYSTEM user by running {{start-process -filepath "msiexec.exe" -arg "/qn /norestart /l*v C:\windows\temp\puppetinstall.log /i c:\temp\puppet\puppet-agent-x64.msi PUPPET_AGENT_STARTUP_MODE=Manual" -Wait}} 3. Populate csr_attributes.yml and {{server}} in the agent config as necessary. 4. As an Administrator, run {{puppet agent --test}} on the newly installed agent.*Actual Behavior:*Catalog retrieval fails; log has been redacted:{code}2019-05-21 17:20:36 -0400 Puppet (debug): HTTP POST https://compiler.example.net:8140/puppet/v3/catalog/examplenode.example.net returned 200 OK2019-05-21 17:20:36 -0400 Puppet (debug): Caching connection for https://compiler.example.net:81402019-05-21 17:20:36 -0400 Puppet (info): Caching catalog for examplenode.example.net2019-05-21 17:20:38 -0400 Puppet (err): ReplaceFile(C:/ProgramData/PuppetLabs/puppet/cache/client_data/catalog/examplenode.example.net.json, C:/ProgramData/PuppetLabs/puppet/cache/client_data/catalog/examplenode.example.net.json20190521-6580-blokpv): Access is denied. c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/file.rb:89:in `replace_file'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util.rb:636:in `replace_file'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/indirector/json.rb:17:in `save'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:200:in `find'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:466:in `block in retrieve_new_catalog'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util.rb:518:in `block in thinmark'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/benchmark.rb:308:in `realt
Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System
Title: Message Title
John O'Connor updated an issue
Puppet / PUP-9719
Cannot run Puppet Agent as Administrator if first PA run is done as System
Change By:
John O'Connor
*Puppet Version:* 6.4.2 *Puppet Server Version:* N/A *OS Name/Version:* Windows Server 2016 x64When installing Puppet Agent (6.4.2/PE 2019.1.0) on Server 2016 using a Powershell script running as the SYSTEM account, Administrator users can't run Puppet. Daemon/service runs are performed as expected. Direct Puppet runs appear to occur but no report is sent to the master.*UPDATE* - It the first Run as SYSTEM that is the problem - so have changed ticket title.PUP-8939 had reportedly solved this issue.*Desired Behavior:**note* - you need to use so far, this can only be replicated using scheduled tasks as {{psexec -s }} to repro this on {{vmpooler}} nodes to ensure doesn't provide the SYSTEM account is used same permissions environment :1. Install: {{psexec -s -i "msiexec.exe" /qn /norestart /l*v C:\windows\temp\puppetinstall.log /i C:\Users\Administrator\Downloads\puppet-agent-6.4.2-x64.msi PUPPET_AGENT_STARTUP_MODE=Manual}}2. Run PA {{psexec -s "C:\Program Files\Puppet Labs\Puppet\bin\puppet.bat" agent -t}} 1. Download the Agent 6.4.2 x64 MSI to a temp path (in this example, {{C:\temp\puppet\puppet-agent-x64.msi}}). 2. Install Puppet Agent on a Server 2016 node as the SYSTEM user by running {{start-process -filepath "msiexec.exe" -arg "/qn /norestart /l*v C:\windows\temp\puppetinstall.log /i c:\temp\puppet\puppet-agent-x64.msi PUPPET_AGENT_STARTUP_MODE=Manual" -Wait}} 3. Populate csr_attributes.yml and {{server}} in the agent config as necessary. 4. As an Administrator, run {{puppet agent --test}} on the newly installed agent.*Actual Behavior:*Catalog retrieval fails; log has been redacted:{code}2019-05-21 17:20:36 -0400 Puppet (debug): HTTP POST https://compiler.example.net:8140/puppet/v3/catalog/examplenode.example.net returned 200 OK2019-05-21 17:20:36 -0400 Puppet (debug): Caching connection for https://compiler.example.net:81402019-05-21 17:20:36 -0400 Puppet (info): Caching catalog for examplenode.example.net2019-05-21 17:20:38 -0400 Puppet (err): ReplaceFile(C:/ProgramData/PuppetLabs/puppet/cache/client_data/catalog/examplenode.example.net.json, C:/ProgramData/PuppetLabs/puppet/cache/client_data/catalog/examplenode.example.net.json20190521-6580-blokpv): Access is denied. c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/file.rb:89:in `replace_file'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util.rb:636:in `replace_file'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/indirector/json.rb:17:in `save'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:200:in `find'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:466:in `block in retrieve_new_catalog'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util.rb:518:in `block in thinmark'c
Jira (PUP-8736) /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-8736 /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs Change By: Gabriel Nagy Assignee: Gabriel Nagy Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.251027.1526491177000.6491.1562316180980%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1932) facter does not pick primary network interface properly on FreeBSD or OpenBSD
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Facter / FACT-1932 facter does not pick primary network interface properly on FreeBSD or OpenBSD Change By: Gabriel Nagy Assignee: Gabriel Nagy Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314338.1561645641000.6476.1562314980346%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1932) facter does not pick primary network interface properly on FreeBSD or OpenBSD
Title: Message Title Gabriel Nagy commented on FACT-1932 Re: facter does not pick primary network interface properly on FreeBSD or OpenBSD Hi Jim Pirzyk, as Romain Tartière mentioned, this should be fixed in 3.14.1. Can you verify this? Thanks! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314338.1561645641000.6473.1562314980328%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
