Jira (BOLT-830) Running a script via PCP fails on Windows
Title: Message Title
Andy Fry commented on BOLT-830
Re: Running a script via PCP fails on Windows
Debug information. [root@cme-custa-pup01 ~]# bolt --version 0.22.0 [root@cme-custa-pup01 ~]# bolt command run date --no-ssl --nodes winrm://cme-win01.internal.com --user ### --password "###" Started on cme-win01.internal.com... Finished on cme-win01.internal.com: STDOUT: Friday, September 7, 2018 4:31:28 AM Successful on 1 node: winrm://cme-win01.internal.com Ran on 1 node in 3.59 seconds [root@cme-custa-pup01 ~]# bolt command run date --no-ssl --nodes $WINNODES Started on cme-win01.internal.com... Failed on cme-win01.internal.com: The command failed with exit code 1 STDOUT: The current date is: Fri 09/07/2018 Enter the new date: (mm-dd-yy) Failed on 1 node: pcp://cme-win01.internal.com Ran on 1 node in 2.76 seconds [root@cme-custa-pup01 ~]# echo $WINNODES pcp://cme-win01.internal.com [root@cme-custa-pup01 ~]# bolt script run TestConnection.ps1 -n $WINNODES --debug > /tmp/bolt_debug_pcp 2>&1 [root@cme-custa-pup01 ~]# cat /tmp/bolt_debug_pcp Loaded inventory from /root/.puppetlabs/bolt/inventory.yaml Did not find config for pcp://cme-win01.internal.com in inventory Started with 100 max thread(s) Starting: script TestConnection.ps1 on pcp://cme-win01.internal.com Running script TestConnection.ps1 with '[]' on ["pcp://cme-win01.internal.com"] Submitting analytics: { "v": 1, "cid": "820a8fab-c9f8-4a27-8d98-ef29ff02e2f4", "tid": "UA-120367942-1", "an": "bolt", "av": "0.22.0", "aip": true, "ul": "en-US", "cd1": "CentOS 7", "t": "event", "ec": "Transport", "ea": "initialize", "el": "orch", "ev": 1 } Submitting analytics: { "v": 1, "cid": "820a8fab-c9f8-4a27-8d98-ef29ff02e2f4", "tid": "UA-120367942-1", "an": "bolt", "av": "0.22.0", "aip": true, "ul": "en-US", "cd1": "CentOS 7", "t": "screenview", "cd": "script_run", "cd5": "human", "cd4": 1, "cd2": 7, "cd3": 3 } Creating orchestrator client for {"User-Agent"=>"Bolt/0.22.0"} Started plan Completed analytics submission Completed analytics submission [\{"node":"pcp://cme-win01.internal.com","status":"failure","result":{"_error":{"msg":"Task exited 1:\nC:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/2.4.0/open3.rb:199:in `spawn': Exec format error - C:/Windows/Temp/bolt_script20180907-2508-1dfqn41 (Errno::ENOEXEC)\n\tfrom C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/2.4.0/open3.rb:199:in `popen_run'\n\tfrom C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/2.4.0/open3.rb:95:in `popen3'\n\tfrom C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/2.4.0/open3.rb:258:in `capture3'\n\tfrom C:/ProgramData/PuppetLabs/pxp-agent/tasks-cache/6f7fc86c2712323a0c0322f215b2cb2409f924dd153f411b3a8a84cdc682b568/script.rb:10:in `command'\n\tfrom C:/ProgramData/PuppetLabs/pxp-agent/tasks-cache/6f7fc86c2712323a0c0322f215b2cb2409f924dd153f411b3a8a84cdc682b568/script.rb:22:in `script'\n\tfrom C:/ProgramData/PuppetLabs/pxp-agent/tasks-cache/6f7fc86c2712323a0c0322f215b2cb2409f924dd153f411b3a8a84cdc682b568/script.rb:27:in `'\n","kind":"puppetlabs.tasks/task-error","details":{"exit_code":1}},"_output":""}}] Finished: script TestConnection.ps1 with 1 failure in 1.79 sec Started on cme-win01.internal.com... Failed on cme-win01.internal.com: Task exited 1: C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/2.4.0/open3.rb:199:in `spawn': Exec format error - C:/Windows/Temp/bolt_script20180907-2508-1dfqn41 (Errno::ENOEXEC) from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/2.4.0/open3.rb:199:in `popen_run' from C:/Program Files/Puppet Labs/Puppet/sys/ruby/lib/ruby/2.4.0/open3.rb:95:in `popen3' from C:/Program Files/Puppet La
Jira (PUP-9068) Windows admin? check should consider group membership
Title: Message Title Ethan Brown commented on PUP-9068 Re: Windows admin? check should consider group membership There's a nice PowerShell module that does all the heavy lifting with privilege assignment at https://gallery.technet.microsoft.com/scriptcenter/Grant-Revoke-Query-user-26e259b0 Through the process of elimination, I was able to determine the single token privilege necessary to "trick" our code - namely SeImpersonatePrivilege # create the user net user testadmin Admin123 /add # grant the impersonation privilege Grant-UserRight -Account testadmin -Right SeImpersonatePrivilege # verify user rights - should return only the SeImpersonatePrivilege Get-UserRightsGrantedToAccount testadmin # use psexec to launch a cmd process and navigate to a directory with Puppet installed, for instance C:\source\puppetlabs-scheduled_task> # run ruby and show elevated is on bundle exec ruby -e "require 'puppet'; puts Puppet::Util::Windows::Process.elevated_security?" # true
Jira (BOLT-459) Reboot a target and wait for it to become available.
Title: Message Title
Nick Maludy commented on BOLT-459
Re: Reboot a target and wait for it to become available.
Taking what Alex mocked up and making it functional i came with the following:
# Reboots a host and waits for it to come back up
plan encore_rp::reboot (
TargetSpec $nodes,
Integer $timeout_sec = 600,
Integer $retry_sec = 3,
) {
$start_time = Timestamp()
$targets = get_targets($nodes)
# get last boot time
$begin_boot_time_results = run_task('encore_rp::last_boot_time', $nodes)
# reboot
# catch errors here because the conne
Jira (PDB-4067) Support running pdb external tests from pdbext, and run them in travis
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4067 Support running pdb external tests from pdbext, and run them in travis Issue Type: Improvement Assignee: Unassigned Created: 2018/09/06 4:22 PM Priority: Normal Reporter: Rob Browning 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. Visi
Jira (PUP-9112) :undef still shows up in types and providers
Title: Message Title
Adam Gardner updated an issue
Puppet / PUP-9112
:undef still shows up in types and providers
Change By:
Adam Gardner
*Puppet Version:* 5.5.6 *Puppet Server Version:* N/A *OS Name/Version:* Centos 7, same on Windows 10Per the discussion in PUP-1467, all Ruby code in Types and Providers is supposed to receive {{undef}} values as {{nil}}. However, in at least some circumstances, I am receiving the Symbol {{:undef}} instead.For example, given the following resource declaration: {code:java}foo { 'bar': baz => {quux => undef, },}{code} *Desired Behavior:*Inside the provider, {{resource[:baz]}} evaluates to {{ \ {'quux' => nil \ }}}*Actual Behavior:*Inside the provider, {{resource[:baz]}} evaluates to {{ \ {'quux' => :undef \ }}}*Additional Context*Besides behaving contrary to the discussions in PUP-1467 (which is the closest I could find to documentation on {{:undef}} vs {{nil}}, this is also problematic when the provider is constructing JSON, perhaps to communicate with an API; the desired JSON string would be {{ \ {"quux": null \ }}}, but instead you end up with {{ \ {"quux": "undef" \ }}}.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9112) :undef still shows up in types and providers
Title: Message Title
Adam Gardner created an issue
Puppet / PUP-9112
:undef still shows up in types and providers
Issue Type:
Bug
Affects Versions:
PUP 5.5.6
Assignee:
Unassigned
Components:
Types and Providers
Created:
2018/09/06 4:16 PM
Priority:
Minor
Reporter:
Adam Gardner
Puppet Version: 5.5.6 Puppet Server Version: N/A OS Name/Version: Centos 7, same on Windows 10 Per the discussion in PUP-1467, all Ruby code in Types and Providers is supposed to receive undef values as nil. However, in at least some circumstances, I am receiving the Symbol :undef instead. For example, given the following resource declaration:
foo { 'bar':
baz => {
quux => undef,
},
Jira (PUP-8836) Remove type/provider code from puppet
Title: Message Title Josh Cooper commented on PUP-8836 Re: Remove type/provider code from puppet Merged to master in https://github.com/puppetlabs/puppet/commit/8863489f74cdb047b76b417b1363490641f9a5d2 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9091) Change deprecation warning for illegal top level constructs to an error
Title: Message Title Kris Bosland commented on PUP-9091 Re: Change deprecation warning for illegal top level constructs to an error Going forward with the hard error. 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4242) Add errors for manifests declaring things in wrong namespace
Title: Message Title Kris Bosland commented on PUP-4242 Re: Add errors for manifests declaring things in wrong namespace Going forward with the hard error. 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-719) Allow modulepath to include paths relative to the Boltdir
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-719 Allow modulepath to include paths relative to the Boltdir Change By: Nick Lewis Assignee: Nick Lewis 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9111) Restarting services using launchd service provider is flaky
Title: Message Title Clay Caviness commented on PUP-9111 Re: Restarting services using launchd service provider is flaky https://github.com/puppetlabs/puppet/pull/7053 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9111) Restarting services using launchd service provider is flaky
Title: Message Title Clay Caviness created an issue Puppet / PUP-9111 Restarting services using launchd service provider is flaky Issue Type: Bug Affects Versions: PUP 5.4.0 Assignee: Unassigned Attachments: keepalive.plist, keepalive.pp, keepalive.sh Created: 2018/09/06 2:44 PM Priority: Normal Reporter: Clay Caviness Puppet Version: 5.4.0 OS Name/Version: macOS 10.13.6 Restarting jobs will frequently fail. When restarting a service, the launchd provider calls stop and then start. The stop method executes launchctl unload -w , and then calls enable The enable method reads the disable overrides pilst (/var/db/com.apple.xpc.launchd/disabled.plist) and modifies it. However, there is a race. While the launchd process is changing states, the disables plist is sometimes zero-length. When this occurs, read_plist (which is just Puppet::Util::(Plist.read_plist_file fails: Info: /Stage[main]/Main/File[/tmp/foo]: Scheduling refresh of Service[keepalive] Warning: Cannot read file /var/db/com.apple.xpc.launchd/disabled.plist; Puppet is skipping it.\nDetails: Execution of '/usr/bin/plutil -convert xml1 -o - /var/db/com.apple.xpc.launchd/disabled.plist' returned 1: /var/db/com.apple.xpc.launchd/disabled.plist: Property List error: Cannot parse a
Jira (PUP-6254) Windows Service start reports failures instead of success under some states
Title: Message Title Sean McDonald commented on PUP-6254 Re: Windows Service start reports failures instead of success under some states This should be resolved with the resolution of PUP-5475, tests have been added like https://github.com/puppetlabs/puppet/pull/7017/files#diff-3605a66d10a7037dc84d525509509608R102 that should determine that ensure => running should not fail when the service enters a pending state. 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. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3952) Find/fix database connection errors after clj-parent 2.0 dep upgrades
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3952 Find/fix database connection errors after clj-parent 2.0 dep upgrades Change By: Rob Browning Assignee: Rob Browning 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. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4017) Accommodate rich data (initially) by ignoring it
Title: Message Title Rob Browning assigned an issue to Austin Blatt PuppetDB / PDB-4017 Accommodate rich data (initially) by ignoring it Change By: Rob Browning Assignee: Rob Browning Austin Blatt 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. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1881) Windows operating system versions fact should include build numbers for Windows 10 / resolve correctly on Server 2019
Title: Message Title Ethan Brown created an issue Facter / FACT-1881 Windows operating system versions fact should include build numbers for Windows 10 / resolve correctly on Server 2019 Issue Type: Bug Affects Versions: FACT 3.11.4 Assignee: Unassigned Components: Windows Created: 2018/09/06 1:34 PM Fix Versions: FACT 3.11.z Labels: windows fact Priority: Normal Reporter: Ethan Brown Some assumptions were made in FACT-1492 about how Windows version numbers should resolve. Those assumptions are codified in https://github.com/puppetlabs/facter/blob/2ad48c341831ac261c9ef16e94f94e74735959c2/lib/src/facts/windows/operating_system_resolver.cc#L103-L104 The story around Windows versioning has changed a bit, such that there are many versions of Windows 10 with different build numbers. See https://en.wikipedia.org/wiki/Windows_10_version_history for the current history. Furthermore, Windows 2019 now exists and it appears that it will follow a similar format going forward. Facter should be updated to address these details.
Jira (PUP-8837) Move all outstanding PUP tickets to Modules
Title: Message Title Jorie Tappa assigned an issue to Jorie Tappa Puppet / PUP-8837 Move all outstanding PUP tickets to Modules Change By: Jorie Tappa Assignee: Jorie Tappa 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4242) Add errors for manifests declaring things in wrong namespace
Title: Message Title Henrik Lindberg commented on PUP-4242 Re: Add errors for manifests declaring things in wrong namespace The errors that this prevents are kind of really bad and mysterious (arbitrary top level code, and ending up with definitions that came from some arbitrary place). For that reason I would like this to be a non configurable and hard error. However, since we just recently added the deprecation making it a hard error now may be too soon. If we make it configurable but make strict=warning be an error, and strict=off make it be ignored, then users will miss seeing what strict=warning (the default) would have shown them (for other issues) if they use strict=off to get rid of the errors. That is probably not a good alternative as it only pushes their technical debt forward for those other issues. Therefore if we feel that we do not want to force users to fix their errors for Puppet 6.0.0, then it is best to just use the strict severity levels as they are - warning by default, off, or error depending on the setting. Then, making it a hard error in Puppet 7. So, I recommend one of: hard error always configurable, follow the severity indicated by --strict 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, sen
Jira (FACT-1380) Restore --timing option to native facter
Title: Message Title
Adrian Parreiras Horta commented on FACT-1380
Re: Restore --timing option to native facter
A hack using `jq` to get a list of the facts and time each one. One could probably substitute Python's json tool or something else.
#!/bin/bash
shopt -s nullglob
facts=($(facter -p --json | jq -cr 'keys | .[]'))
for f in "${facts[@]}"; do
echo "${f}:"
time facter -p "$f" &>/dev/null
done
Jira (PUP-9094) Switch rest client back to using Puppet::Network::HttpPool
Title: Message Title Rob Braden commented on PUP-9094 Re: Switch rest client back to using Puppet::Network::HttpPool Currently blocked waiting on puppet server certificate to land 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4543) Document how to run AIO puppet acceptance in acceptance_tests.md
Title: Message Title Rob Braden updated an issue Puppet / PUP-4543 Document how to run AIO puppet acceptance in acceptance_tests.md Change By: Rob Braden Fix Version/s: PUP 5.y 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9110) Accept and produce ASCII_8BIT as Binary value
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9110 Accept and produce ASCII_8BIT as Binary value Change By: Josh Cooper Team: Platform Core 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9091) Change deprecation warning for illegal top level constructs to an error
Title: Message Title Kris Bosland commented on PUP-9091 Re: Change deprecation warning for illegal top level constructs to an error Josh Cooper, Henrik Lindberg, Eric Sorenson, similar to PUP-4242, should this error be prevented when strict=off? 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4242) Add errors for manifests declaring things in wrong namespace
Title: Message Title Kris Bosland commented on PUP-4242 Re: Add errors for manifests declaring things in wrong namespace Henrik Lindberg, Eric Sorenson, do you agree with the request to prevent this error when strict=off? 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4242) Add errors for manifests declaring things in wrong namespace
Title: Message Title Kris Bosland updated an issue Puppet / PUP-4242 Add errors for manifests declaring things in wrong namespace Change By: Kris Bosland Release Notes Summary: Errors will be reported for module puppet files declaring things in a namespace inconsistent with their directory and file location. Release Notes: Bug Fix 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6716) Error when purging local users on Windows
Title: Message Title Scott McClellan assigned an issue to Scott McClellan Puppet / PUP-6716 Error when purging local users on Windows Change By: Scott McClellan Assignee: Scott McClellan 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. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4066) (MAINT) OpenJDK10 cacerts do not trust clojars by default
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4066 (MAINT) OpenJDK10 cacerts do not trust clojars by default Issue Type: Bug Assignee: Unassigned Created: 2018/09/06 11:15 AM Priority: Normal Reporter: gepetto-bot 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:
Jira (FACT-1380) Restore --timing option to native facter
Title: Message Title Paul Anderson commented on FACT-1380 Re: Restore --timing option to native facter I came up with a quick and dirty bash one-liner that is neither elegant nor guaranteed accurate, but was enough to help the user get a rough order of magnitude read on each of their facts. for fact in `facter -p | egrep '^\w+\s=>' | cut -f 1 -d "="`; do echo $fact; time /usr/local/bin/facter -p $fact > /dev/null; done 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6729) NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators
Title: Message Title Ethan Brown commented on PUP-6729 Re: NTFS permissions should be recalculated given SYSTEM is an implicit member of local Administrators A couple of additional related tickets have been filed to wrap up this effort: PUP-8985 - set manage_internal_file_permissions to false in the packaging so that Puppet doesn't try to manage (and undo) ACLs set by the installer PUP-9068 - make sure that the check for Administrators includes group membership in addition to tokens PUP-9106 - when writing the SYSTEM ACE to the DACL, never write anything other than F 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. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1380) Restore --timing option to native facter
Title: Message Title Paul Anderson updated an issue Facter / FACT-1380 Restore --timing option to native facter Change By: Paul Anderson Labels: PS linux regression windows 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. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1380) Restore --timing option to native facter
Title: Message Title Jeremy Adams commented on FACT-1380 Re: Restore --timing option to native facter +1 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9104) YAML safe_load prevents aliases
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9104 YAML safe_load prevents aliases Since the switch to YAML.safe_yaml and this PR were made together, there are no user facing changes. Puppet should behave as it did before with respect to YAML aliases. Change By: Josh Cooper Release Notes: Bug Fix Not Needed 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. For more options, visit https://groups.google.com/d/optout
Jira (FACT-1380) Restore --timing option to native facter
Title: Message Title Paul Anderson commented on FACT-1380 Re: Restore --timing option to native facter Robert Petersson Can you tell us what further information you're looking for? 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-829) modulepath argument does not handle paths with spaces
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-829 modulepath argument does not handle paths with spaces Change By: Michael Smith Sprint: Bolt Ready for Grooming 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9104) YAML safe_load prevents aliases
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9104 YAML safe_load prevents aliases Change By: Josh Cooper Summary: YAML safe_load too strict prevents aliases 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9103) Build Puppet Agent for Ubuntu 16.04
Title: Message Title Michael Smith commented on PUP-9103 Re: Build Puppet Agent for Ubuntu 16.04 This already happens at http://apt.puppet.com/pool/xenial/puppet5/p/puppet-agent/. I'm not clear what this ticket covers. 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. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1380) Restore --timing option to native facter
Title: Message Title Paul Anderson commented on FACT-1380 Re: Restore --timing option to native facter This came up for a user I was speaking with today. 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4242) Add errors for manifests declaring things in wrong namespace
Title: Message Title Josh Cooper commented on PUP-4242 Re: Add errors for manifests declaring things in wrong namespace I agree on making it a hard error in 6, with the ability to turn it off only when strict=off 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9110) Accept and produce ASCII_8BIT as Binary value
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9110 Accept and produce ASCII_8BIT as Binary value Change By: Henrik Lindberg Fix Version/s: PUP 6.0.0 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9110) Accept and produce ASCII_8BIT as Binary value
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-9110 Accept and produce ASCII_8BIT as Binary value Issue Type: Improvement Assignee: Unassigned Created: 2018/09/06 10:12 AM Priority: Normal Reporter: Henrik Lindberg The Binary data type (PUP-5831) has been around a while but never really been used. Instead we have accepted ASCII-8BIT strings as values and switching to PSON in the serialization when encountering such values. The File type has been given support such that it accepts instances of Binary (i.e. Puppet::Pops::Types::PBinaryType::Binary to be precise. Other existing types and providers naturally does not know how to deal with that runtime value and can thus not immediately benefit from rich serialization of a Binary. To resolve this, the Binary data type should be used in the catalog (rich data is on by default in puppet 6.0.0) but the runtime type should be changed from the special Binary to simply use ASCII_8BIT encoded String. Add Comment
Jira (PUP-7601) Remove built-in LDAP Node Terminus
Title: Message Title Kris Bosland assigned an issue to Kris Bosland Puppet / PUP-7601 Remove built-in LDAP Node Terminus Change By: Kris Bosland Assignee: Kris Bosland 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. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-830) Running a script via PCP fails on Windows
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-830 Running a script via PCP fails on Windows Issue Type: Bug Affects Versions: BOLT 0.22.0 Assignee: Unassigned Created: 2018/09/06 9:42 AM Priority: Normal Reporter: Michael Smith Trying to run a powershell script via PCP with Bolt fails. The file extension is not sent along, so the script task doesn't know how to run it. Additionally Bolt hard-codes how to run several types of scripts in the WinRM transport; we should send this mappings to the script task so it can implement similar support for ruby, powershell, puppet, and batch scripts. Add Comment
Jira (PDB-4065) (MAINT) Fix a spelling typo in .travis.yml
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4065 (MAINT) Fix a spelling typo in .travis.yml Issue Type: Bug Assignee: Unassigned Created: 2018/09/06 9:16 AM Priority: Normal Reporter: gepetto-bot It looks like the previous PR was merged from a commit before this typo was fixed. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-658) Validate JSON data in bolt-transport-api requests
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-658 Validate JSON data in bolt-transport-api requests Change By: Lucy Wyman Assignee: Cas Donoghue Lucy Wyman 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9079) Rich data tags __ptype and __pvalue must not be allowed as attribute names
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9079 Rich data tags __ptype and __pvalue must not be allowed as attribute names Change By: Kenn Hussey Team: Platform Core 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9104) YAML safe_load too strict
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9104 YAML safe_load too strict Change By: Kenn Hussey Team: Platform Core 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8622) Allow concatenate with + on Binary type
Title: Message Title Henrik Lindberg commented on PUP-8622 Re: Allow concatenate with + on Binary type Added in commit: a0eb081 merged at e9fc495 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8622) Allow concatenate with + on Binary type
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-8622 Allow concatenate with + on Binary type Change By: Henrik Lindberg Assignee: Tony Vu 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8622) Allow concatenate with + on Binary type
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8622 Allow concatenate with + on Binary type Change By: Henrik Lindberg Fix Version/s: PUP 5.y Fix Version/s: PUP 6.0.0 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9109) File: source attribute broken for HTTP(s) URI's containing query parameters
Title: Message Title Matthias Baur commented on PUP-9109 Re: File: source attribute broken for HTTP(s) URI's containing query parameters PR: https://github.com/puppetlabs/puppet/pull/7051 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9109) File: source attribute broken for HTTP(s) URI's containing query parameters
Title: Message Title Matthias Baur assigned an issue to Unassigned Puppet / PUP-9109 File: source attribute broken for HTTP(s) URI's containing query parameters Change By: Matthias Baur Assignee: Matthias Baur 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9109) File: source attribute broken for HTTP(s) URI's containing query parameters
Title: Message Title
Matthias Baur created an issue
Puppet / PUP-9109
File: source attribute broken for HTTP(s) URI's containing query parameters
Issue Type:
Bug
Affects Versions:
PUP 5.5.6, PUP 4.10.0
Assignee:
Matthias Baur
Created:
2018/09/06 4:02 AM
Priority:
Normal
Reporter:
Matthias Baur
Puppet Version: 4.4.0 - 5.5.6 Puppet Server Version: All OS Name/Version: All We want to use the `source` attribute of the file type to get host specific stuff from a web service. For this we're using the following code:
file { '/etc/path/to/file':
ensure => file,
source => 'https://fancywebservice.example.org/get_host_specific_config.py?host=foobar'
}
The important part here is the `host=foobar` parameter. If it's not added, the web service will return a 404. Desired
Jira (PUP-9104) YAML safe_load too strict
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9104 YAML safe_load too strict Change By: Henrik Lindberg Release Notes Summary: YAML safe_load was too strict and refused to load local aliases in a yaml file.Now it is possible to use such aliases. Release Notes: Bug Fix 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9104) YAML safe_load too strict
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9104 YAML safe_load too strict Change By: Henrik Lindberg Fix Version/s: PUP 6.0.0 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9104) YAML safe_load too strict
Title: Message Title Henrik Lindberg commented on PUP-9104 Re: YAML safe_load too strict merged to master at ef7b7fc 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9104) YAML safe_load too strict
Title: Message Title Thomas Franklin commented on PUP-9104 Re: YAML safe_load too strict David Mallon PR is ready, just waiting on the test results. 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9104) YAML safe_load too strict
Title: Message Title David Mallon commented on PUP-9104 Re: YAML safe_load too strict Thomas Franklin could you get a PR with that fix created for puppet master? 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4242) Add errors for manifests declaring things in wrong namespace
Title: Message Title Henrik Lindberg commented on PUP-4242 Re: Add errors for manifests declaring things in wrong namespace We are still not quite clear on the severeness of the raised issue from this validation for Puppet 6.0.0. On 5.y the issue is :deprecation and will always warn. The earlier PR, as well as the new has these issues under control of the strict setting, which is actually more relaxed than the 5.y hard :deprecation level. We should either make it a hard error or possibly if we think users may run into problems in such bad ways that we want to allow them to turn this off by using `strict=off`, then we could make it an error also for strict=warning (since that is the default setting). My preference is to make it a hard error. 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. For more options, visit https://groups.google.com/d/optout.
