Jira (PDB-4093) Set up CI with Azure Pipelines
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4093 Set up CI with Azure Pipelines Issue Type: Bug Assignee: Unassigned Created: 2018/09/17 5:26 PM 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
Jira (PUP-4687) Windows User resource managehome doesn't support custom directories
Title: Message Title Sean McDonald assigned an issue to Sean McDonald Puppet / PUP-4687 Windows User resource managehome doesn't support custom directories Change By: Sean McDonald Assignee: Sean McDonald 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-6542) Group resource emits misleading change notification with auth_membership => false
Title: Message Title Sean McDonald commented on PUP-6542 Re: Group resource emits misleading change notification with auth_membership => false Moving this back to ready. We are going to wait on a session with Branan to learn about the resource harness before talking this. Should happen this week (week of 9/17) and we'll pull the ticket back in to doing then. 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-843) Generate a "retry" file when some nodes fail
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-843 Generate a "retry" file when some nodes fail Issue Type: New Feature Assignee: Unassigned Created: 2018/09/17 4:17 PM Priority: Normal Reporter: Nick Lewis When a task/command/script/upload fails, Bolt should generate a retry file that includes the list of nodes that failed. That simplifies iterative workflows, whereby a user can try to run a task, make any needed adjustments on failed nodes, and then try it again. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-842) set_feature(), etc functions should work with a TargetSpec
Title: Message Title Nick Lewis created an issue Puppet Task Runner / BOLT-842 set_feature(), etc functions should work with a TargetSpec Issue Type: Improvement Assignee: Unassigned Created: 2018/09/17 4:16 PM Priority: Normal Reporter: Nick Lewis Currently, set_feature() and related functions operate on a single Target instance, which requires one to call get_targets() and loop over the results to set a feature on multiple targets. Those functions should accept a TargetSpec and expand it if necessary. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-3834) remove webrick/rack support from Puppet
Title: Message Title Justin Stoller updated an issue Puppet / PUP-3834 remove webrick/rack support from Puppet Change By: Justin Stoller Fix Version/s: PUP 6.0.0 Fix Version/s: PUP 6.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-8918) Separate CA and SSL dirs
Title: Message Title Justin Stoller updated an issue Puppet / PUP-8918 Separate CA and SSL dirs Change By: Justin Stoller Fix Version/s: PUP 6.0.0 Fix Version/s: PUP 6.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 (PDB-2647) automatic updating of documented ERD diagram
Title: Message Title Rob Browning commented on PDB-2647 Re: automatic updating of documented ERD diagram postgresql-autodoc can generate svg via dot, which is what I use locally. 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-658) Validate JSON data in bolt-transport-api requests
Title: Message Title Michael Smith assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-658 Validate JSON data in bolt-transport-api requests Change By: Michael Smith Assignee: Nick Lewis Cas Donoghue 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-3559) Add PUPPETSERVER_REPO and PUPPET_REPO overrides
Title: Message Title Rob Browning commented on PDB-3559 Re: Add PUPPETSERVER_REPO and PUPPET_REPO overrides Superseded by the addition of ext/bin/test-config, update-puppetserver-ref, etc. in the lead up to 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 (PDB-3874) (maint) update clj-parent and rbac dependencies
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3874 (maint) update clj-parent and rbac dependencies Change By: Rob Browning Fix Version/s: PDB 5.2.z 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-841) Display where modules are located in "show" commands
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-841 Display where modules are located in "show" commands Issue Type: New Feature Assignee: Unassigned Created: 2018/09/17 3:32 PM Priority: Normal Reporter: Alex Dreyer when a user runs bolt task show or bolt plan show bolt should display to path to the moduledirectory the module is installed in. For bundled content bolt should display . Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-840) Include unvendored Puppet 6 content in Bolt
Title: Message Title Ryan Coleman commented on BOLT-840 Re: Include unvendored Puppet 6 content in Bolt To add a little color onto my experience, here's how I arrived at a point where I was pulling in yumrepo_core and ran into a problem loading the sensitive function. get excited by blog post https://puppet.com/blog/introducing-masterless-puppet-bolt follow getting started guide to try on my own with Bolt 0.22.0 installed via MacOS package (successful) https://puppet.com/docs/bolt/0.x/create_sample_manifest_nix.html refactor example to use puppet-nginx module instead of base resources install puppet-nginx into workstation modulepath clone https://github.com/puppetlabs/puppetlabs-yumrepo_core into workstation modulepath to resolve missing yumrepo resource needed by puppet-nginx apply plan and fail Starting: plan plive::nginx Starting: install puppet and gather facts on 10.234.3.35 Finished: install puppet and gather facts with 0 failures in 11.97 sec Starting: apply catalog on 10.234.3.35 Finished: apply catalog with 1 failure in 21.32 sec Finished: plan plive::nginx in 33.33 sec The task failed with exit code 1: /tmp/d20180917-23557-yhvb9v/yumrepo_core/lib/puppet/type/yumrepo.rb:323:in `block (2
Jira (BOLT-840) Include unvendored Puppet 6 content in Bolt
Title: Message Title Michael Smith assigned an issue to Nick Lewis Puppet Task Runner / BOLT-840 Include unvendored Puppet 6 content in Bolt Change By: Michael Smith 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 (BOLT-840) Include unvendored Puppet 6 content in Bolt
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-840 Include unvendored Puppet 6 content in Bolt Change By: Michael Smith Sprint: Bolt Ready for Grooming Kanban 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-840) Include unvendored Puppet 6 content in Bolt
Title: Message Title Nick Lewis commented on BOLT-840 Re: Include unvendored Puppet 6 content in Bolt We need to install these to a location where we can skip syncing them to agents during apply(), because they're a) unnecessary, b) potentially incompatible with Puppet 5 agents. 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-840) Include unvendored Puppet 6 content in Bolt
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-840 Include unvendored Puppet 6 content in Bolt Change By: Michael Smith Puppet 6 removed several resource declarations from the Puppet gem, but added them back in packaging. To make the apply experience smooth, we should include the same modules in packaging Bolt. That list consists of * augeas_core * host_core * scheduled_task * sshkeys_core * zfs_core * cron_core * mount_core * selinux_core * yumrepo_core * zone_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 (BOLT-840) Include unvendored Puppet 6 content in Bolt
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-840 Include unvendored Puppet 6 content in Bolt Issue Type: Improvement Assignee: Unassigned Created: 2018/09/17 2:59 PM Priority: Normal Reporter: Michael Smith Puppet 6 removed several resource declarations from the Puppet gem, but added them back in packaging. To make the apply experience smooth, we should include the same modules in packaging Bolt. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-3471) Support "!=" syntax in PQL
Title: Message Title Austin Blatt assigned an issue to Unassigned PuppetDB / PDB-3471 Support "!=" syntax in PQL Change By: Austin Blatt Assignee: 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 (BOLT-804) Bolt unable to connect to customer windows 2012 server over winrm
Title: Message Title Dave Johnston commented on BOLT-804 Re: Bolt unable to connect to customer windows 2012 server over winrm In the UI I entered it as puppet.com\dave So no need for extra escaping by the user. 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-6919) Puppet::Util::Windows::Process.execute should accept a working directory
Title: Message Title
Enis Inan updated an issue
Puppet / PUP-6919
Puppet::Util::Windows::Process.execute should accept a working directory
Change By:
Enis Inan
The Windows API supports setting a working directory when starting a process. However, Puppet does not currently allow setting this value programatically.The win32-process gem can pass {{ cwd}} supplied through it's argument hash - see code at https://github.com/djberg96/win32-process/blob/win32-process-0.7.5/lib/win32/process.rb#L681 Puppet currently uses {{Dir.chdir}} to set a working directory before creating a process - however, this might not always work properly on Windows. The {{cwd}} has {{File.directory?(dir)}} used to validate it, which could fail on UNC or other path types (like reparse points - i.e. symlinks) on Windows - meaning that {{Dir.chdir}} at https : //github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/exec.rb#L29 never gets called as expected.{{cwd}} should be passed in to {{Puppet : : Util::Execution.execute}} at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/exec.rb#L59 / and should take in a `cwd` option that lets the call to {{Process.create}} at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/ user specify the new process ' working directory . rb#L12 should pass the {{arguments}} value through.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9150) cwd option in Puppet::Util::Execution.execute should work with different Windows path types
Title: Message Title Enis Inan commented on PUP-9150 Re: cwd option in Puppet::Util::Execution.execute should work with different Windows path types There's an issue with Process.create where the process will still start in the `cwd` even if the user does not have permissions to access it. However, the process cannot manipulate anything in the `cwd` so this is not a security issue. It just produces weird behavior. Another approach might be to modify `Puppet::FileSystem.directory?` to work with the different types of Windows paths that are out there. Currently, we just delegate to `File.directory?` as seen here 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-9150) cwd option in Puppet::Util::Execution.execute should work with different Windows path types
Title: Message Title
Enis Inan updated an issue
Puppet / PUP-9150
cwd option in Puppet::Util::Execution.execute should work with different Windows path types
Change By:
Enis Inan
The Windows API supports setting a working directory when starting a process. However, Puppet does not currently allow setting this value programatically.The win32-process gem can pass {{cwd}} supplied through it's argument hash - see code at [https://github.com/djberg96/win32-process/blob/win32-process-0.7.5/lib/win32/process.rb#L681]Puppet currently uses {{Dir.chdir}} to set a working directory before creating a process - however, this might not always work properly on Windows. The {{cwd}} has {{File.directory?(dir)}} used to validate it, which could fail on UNC or other path types (like reparse points - i.e. symlinks) on Windows - meaning that {{Dir.chdir}} never gets called as expected. {{cwd}} should be passed in to {{Puppet::Util::Execution.execute}} at [https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/exec.rb#L59] / and the The call to {{Process.create}} at [https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/process.rb#L12] should pass the {{arguments}} value through.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9150) cwd option in Puppet::Util::Execution.execute should work with different Windows path types
Title: Message Title
Enis Inan updated an issue
Puppet / PUP-9150
cwd option in Puppet::Util::Execution.execute should work with different Windows path types
Change By:
Enis Inan
The Windows API supports setting a working directory when starting a process. However, Puppet does not currently allow setting this value programatically.The win32-process gem can pass {{cwd}} supplied through it's argument hash - see code at [https://github.com/djberg96/win32-process/blob/win32-process-0.7.5/lib/win32/process.rb#L681]Puppet currently uses {{Dir.chdir}} to set a working directory before creating a process - however, this might not always work properly on Windows. The {{cwd}} has {{File.directory?(dir)}} used to validate it, which could fail on UNC or other path types (like reparse points - i.e. symlinks) on Windows - meaning that {{Dir.chdir}} never gets called as expected.{{cwd}} should be passed in to {{Puppet::Util::Execution.execute}} at [https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/exec.rb#L59] / and the call to {{Process.create}} at [https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/process.rb#L12] should pass the {{arguments}} value through.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9150) cwd option in Puppet::Util::Execution.execute should work with different Windows path types
Title: Message Title Enis Inan created an issue Puppet / PUP-9150 cwd option in Puppet::Util::Execution.execute should work with different Windows path types Issue Type: Bug Assignee: Unassigned Created: 2018/09/17 1:59 PM Priority: Normal Reporter: Enis Inan 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
Jira (PUP-9149) Agents should re-download CRLs when they are newer than the local copy
Title: Message Title Kenn Hussey commented on PUP-9149 Re: Agents should re-download CRLs when they are newer than the local copy Thanks Maggie Dreyer and Justin Stoller. Do we need to create a separate ticket (with a different fix version) for the parts that won't go out with 6.0.0 (or vice versa)? 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-9147) External comms on Puppet 6 CA cert changes
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-9147 External comms on Puppet 6 CA cert changes Change By: Maggie Dreyer 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-9147) External comms on Puppet 6 CA cert changes
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-9147 External comms on Puppet 6 CA cert changes Change By: Maggie Dreyer Team: Server 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-804) Bolt unable to connect to customer windows 2012 server over winrm
Title: Message Title Michael Smith commented on BOLT-804 Re: Bolt unable to connect to customer windows 2012 server over winrm Ok, I'll check how that works when it goes to Bolt as an environment variable. 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-804) Bolt unable to connect to customer windows 2012 server over winrm
Title: Message Title
Dave Johnston commented on BOLT-804
Re: Bolt unable to connect to customer windows 2012 server over winrm
Michael Smith we don't log this to avoid leaking secrets, but I ran up a local version and added the debug. Here is the output: {"nodes":[{"name":"10.16.127.166","config":{"transport":"winrm","winrm": {"user":"puppet.com\\dave","password":"Q*!","ssl":true,"allow_http_fallback":true,"ssl-verify":false} }}]} So the user appears to be double escaped, as you suggested. "user":"puppet.comdave"
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-9143) Puppet device raises `undefined method` error
Title: Message Title Thomas Kishel commented on PUP-9143 Re: Puppet device raises `undefined method` error Manual test of PR 7096/7097: [root@pe-20190nightly-master production]# diff /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/device.rb device.rb.55 378a379,383 > # We need to specify a ca location for all of the SSL-related > # indirected classes to work; in fingerprint mode we just need > # access to the local files and we don't need a ca. > Puppet::SSL::Host.ca_location = :remote > 386a392 > [root@pe-20190nightly-master production]# puppet device --verbose --trace --strict=error --target cisco.example.com
Jira (PUP-9143) Puppet device raises `undefined method` error
Title: Message Title David Schmitt commented on PUP-9143 Re: Puppet device raises `undefined method` error Maggie Dreyer I can confirm that using this change the Resource API tests that originally flagged that issue pass now: https://travis-ci.org/puppetlabs/puppet-resource_api/jobs/429743241 Finished in 2 minutes 48.7 seconds (files took 2.45 seconds to load) 1272 examples, 0 failures, 1 pending 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
Jira (PUP-9143) Puppet device raises `undefined method` error
Title: Message Title Scott Garman assigned an issue to Maggie Dreyer Puppet / PUP-9143 Puppet device raises `undefined method` error Change By: Scott Garman Assignee: Maggie Dreyer 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-9143) Puppet device raises `undefined method` error
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9143 Puppet device raises `undefined method` error Change By: Kenn Hussey Team: Server 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-9148) apple.rake references incorrect location after Rakefile changed to use packaging as a gem
Title: Message Title Clay Caviness commented on PUP-9148 Re: apple.rake references incorrect location after Rakefile changed to use packaging as a gem Pull request here 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-9146) r10k pipelines failing for Ubuntu18 shellgit
Title: Message Title Amy Sahli commented on PUP-9146 Re: r10k pipelines failing for Ubuntu18 shellgit Closing as a duplicate of https://tickets.puppetlabs.com/browse/RK-324 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-8913) Agents should re-download CRLs when they are newer than the local copy
Title: Message Title
Justin Stoller updated an issue
Puppet / PUP-8913
Agents should re-download CRLs when they are newer than the local copy
Change By:
Justin Stoller
This is the original ticket, but is being used for the Server side work that will ship in Puppet Server 6.0.0. For the remaining, agent-side work, see the cloned ticket PUP-9149. - While my agents are running, I expect them to check the CRL to see if it's been updated since the last download, and if so to get the latest one from the CA, so that they can correctly validate that the masters they are talking to are still valid.This is mostly relevant for agents talking to compile masters, which also get certificates from the CA. We don't want agents to try to talk to compile masters whose certificates have been revoked.See PUP-2310.Q: Do CRLs have TTLs that we could respect? A: Yes, but it's complicated and we probably should just check last modified.*Details:*So the plan going forward will be this (see [https://github.com/puppetlabs/puppet/blob/76043d833f70d70fd2b5e3c43f13c5226223d8f9/lib/puppet/ssl/host.rb#L301):]1. From from `ssl_store` => `build_ssl_store`=> We will alter the `build_ssl_store` method to ALWAYS call the altered/renamed `download_and_save_crl_bundle` method. 2. That will continue to call the `Puppet::Rest::Routes.get_crls` method, but the `get_crls` method will send a *header* (ex *{{If-Modified-Since)}}*containing the last_modified timestamp of the current crl. The * /certificate_revocation_list/name* endpoint on puppetserver will then be altered to either accept a header with the timestamp and, * If the *{{If-Modified-Since}}* header is present AND the timestamp is OLDER than the master's crl, will return the NEW crl to the agent in the response body and 200 response. * If no *{{If-Modified-Since}}* header is included, the endpoint will function the same way as it currently functions. * If the *{{If-Modified-Since}}* header is present AND the timestamp is EQUAL to or NEWER than the master's crl, will return an empty body and something like a 204 response.-We need to decide if a header or query param is more appropriate for our case.- [~josh] -thoughts on this?- See comment below.*Acceptance Criteria:* * The *certificate_revocation_list/name* endpoint on puppetserver continues to function as it always did if no *{{If-Modified-Since}}* header are received. * If the *{{If-Modified-Since}}* header is passed to the above endpoint, it will return a crl if the timestamp provided is OLDER than the master crl file's timestamp. * If the *{{If-Modified-Since}}* header is passed to the above endpoint, it will return an empty body (no crl) if the timestamp provided is EQUAL to or NEWER than the master crl file's timestamp. * New endpoint behavior with headers are documented.
Jira (PUP-9149) Agents should re-download CRLs when they are newer than the local copy
Title: Message Title Justin Stoller created an issue Puppet / PUP-9149 Agents should re-download CRLs when they are newer than the local copy Issue Type: Story Assignee: Nick Walker Created: 2018/09/17 12:16 PM Fix Versions: SERVER 6.0.0 Labels: Blocked Priority: Normal Reporter: Justin Stoller While my agents are running, I expect them to check the CRL to see if it's been updated since the last download, and if so to get the latest one from the CA, so that they can correctly validate that the masters they are talking to are still valid. This is mostly relevant for agents talking to compile masters, which also get certificates from the CA. We don't want agents to try to talk to compile masters whose certificates have been revoked. See PUP-2310. Q: Do CRLs have TTLs that we could respect? A: Yes, but it's complicated and we probably should just check last modified. Details: So the plan going forward will be this (see https://github.com/puppetlabs/puppet/blob/76043d833f70d70fd2b5e3c43f13c5226223d8f9/lib/puppet/ssl/host.rb#L301): 1. From from `ssl_store` => `build_ssl_store`=> We will alter the `build_ssl_store` method to ALWAYS call the altered/renamed `download_and_save_crl_bundle` method. 2. That will continue to call the `Puppet::Rest::Routes.get_crls` method, but the `get_crls` method will send a header (ex If-Modified-Since)*containing the last_modified timestamp of the current crl. The /certificate_revocation_list/name* endpoint on puppetserver will then be altered to either accept a header with the timestamp and, If the If-Modified-Since header is present AND the timestamp is OLDER than the master's crl, will return the NEW crl to the
Jira (PUP-9148) apple.rake references incorrect location after Rakefile changed to use packaging as a gem
Title: Message Title Clay Caviness created an issue Puppet / PUP-9148 apple.rake references incorrect location after Rakefile changed to use packaging as a gem Issue Type: Bug Assignee: Unassigned Created: 2018/09/17 12:14 PM Priority: Normal Reporter: Clay Caviness Puppet Version: 5.5.6 OS Name/Version: 10.13.6 We are building puppet from source based of the method described in this post to the puppet-users list. A recent change to the puppet Rakefile started using packaging as a gem instead of expanding/vendoring/whatever the term is inside of ext/. However, the apple.rake task still references ext/packaging on line 73. This means that the PackageInfo.plist is not found, and the pkgbuild fails. I'm not sure what is expected here, or how your build systems works around this. Perhaps it is both using packaging as a gem and expanding into ext/? I have a small patch for this that works locally which I will send as a pull request shortly. Add Comment
Jira (PUP-9146) r10k pipelines failing for Ubuntu18 shellgit
Title: Message Title
Amy Sahli updated an issue
Puppet / PUP-9146
r10k pipelines failing for Ubuntu18 shellgit
Change By:
Amy Sahli
*Puppet Version:* current *Puppet Server Version:* current *OS Name/Version:* ONLY shellgit, beaker, ubuntu 1804-64.*Desired Behavior:* Our r10k pipelines for Irving and Johnson branches are all passing*Actual Behavior:*Our r10k pipelines for Irving and Johnson branches are failing. Example:[https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/job/enterprise_r10k_intn-van-sys_irving/GIT_PROVIDER=shellgit,SLAVE_LABEL=beaker,TEST_TARGET=ubuntu1804-64.mdca/22/consoleFull]Various environments are successfully deployed, until at some point one fails with the below output: {code:java}15:42:56 INFO -> Environment c6a5f95de5324a73b988636f86acbe33 is now at 9fbd204382b755fcdb9815222dd46026e61c2501 15:42:56 INFO -> Deploying environment /etc/puppetlabs/code/environments/f856ae9752dd4bcfaca9a6a4fe18dedf 15:42:56 INFO -> Environment f856ae9752dd4bcfaca9a6a4fe18dedf is now at 9fbd204382b755fcdb9815222dd46026e61c2501 15:42:56 INFO -> Deploying environment /etc/puppetlabs/code/environments/f9a687a266e54f8089f28b943c821e31 15:42:56 [ASYNC BUG] (6) 15:42:56 EPIPE 15:42:56 15:42:56 ruby 2.4.4p296 (2018-03-28 revision 63013) [x86_64-linux] 15:42:56 15:42:56 [NOTE] 15:42:56 You may have encountered a bug in the Ruby interpreter or extension libraries. 15:42:56 Bug reports are welcome. 15:42:56 For details: http://www.ruby-lang.org/bugreport.html 15:42:56 15:42:56 ssw16hcquetuscm.delivery.puppetlabs.net (ubuntu1804-64-1) executed in 1.25 seconds 15:42:56 Beaker::Host::CommandFailure: Host 'ssw16hcquetuscm.delivery.puppetlabs.net' connection failure running: 15:42:56 /opt/puppetlabs/puppet/bin/r10k deploy environment -v 15:42:56 Last 10 lines of output were: 15:42:56 INFO -> Deploying environment /etc/puppetlabs/code/environments/f9a687a266e54f8089f28b943c821e31 15:42:56 [ASYNC BUG] (6) 15:42:56 EPIPE 15:42:56 15:42:56 ruby 2.4.4p296 (2018-03-28 revision 63013) [x86_64-linux] 15:42:56 15:42:56 [NOTE] 15:42:56 You may have encountered a bug in the Ruby interpreter or extension libraries. 15:42:56 Bug reports are welcome. 15:42:56 For details: http://www.ruby-lang.org/bugreport.html{code}
Add Comment
Jira (PUP-9146) r10k pipelines failing for Ubuntu18 shellgit
Title: Message Title
Amy Sahli updated an issue
Puppet / PUP-9146
r10k pipelines failing for Ubuntu18 shellgit
Change By:
Amy Sahli
*Puppet Version:* current *Puppet Server Version:* current *OS Name/Version:* ONLY shellgit, beaker, ubuntu 1804-64.*Desired Behavior:* Our r10k pipelines for Irving and Johnson branches are all passing*Actual Behavior:*Our r10k pipelines for Irving and Johnson branches are failing. Example:[https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/job/enterprise_r10k_intn-van-sys_irving/GIT_PROVIDER=shellgit,SLAVE_LABEL=beaker,TEST_TARGET=ubuntu1804-64.mdca/22/consoleFull]Various environments are successfully deployed, until at some point one fails with the below output: {code:java} 15:42:56 INFO -> Environment c6a5f95de5324a73b988636f86acbe33 is now at 9fbd204382b755fcdb9815222dd46026e61c2501 15:42:56 INFO -> Deploying environment /etc/puppetlabs/code/environments/f856ae9752dd4bcfaca9a6a4fe18dedf 15:42:56 INFO -> Environment f856ae9752dd4bcfaca9a6a4fe18dedf is now at 9fbd204382b755fcdb9815222dd46026e61c250115:42:56 INFO -> Deploying environment /etc/puppetlabs/code/environments/f9a687a266e54f8089f28b943c821e31 15:42:56 [ASYNC BUG] (6) 15:42:56 EPIPE 15:42:56 15:42:56 ruby 2.4.4p296 (2018-03-28 revision 63013) [x86_64-linux] 15:42:56 15:42:56 [NOTE] 15:42:56 You may have encountered a bug in the Ruby interpreter or extension libraries. 15:42:56 Bug reports are welcome.15:42:56 For details: http://www.ruby-lang.org/bugreport.html 15:42:56 15:42:56 ssw16hcquetuscm.delivery.puppetlabs.net (ubuntu1804-64-1) executed in 1.25 seconds 15:42:56Beaker::Host::CommandFailure: Host 'ssw16hcquetuscm.delivery.puppetlabs.net' connection failure running: 15:42:56 /opt/puppetlabs/puppet/bin/r10k deploy environment -v 15:42:56 Last 10 lines of output were: 15:42:56 INFO -> Deploying environment /etc/puppetlabs/code/environments/f9a687a266e54f8089f28b943c821e31 15:42:56 [ASYNC BUG] (6) 15:42:56 EPIPE 15:42:56 15:42:56 ruby 2.4.4p296 (2018-03-28 revision 63013) [x86_64-linux] 15:42:56 15:42:56 [NOTE] 15:42:56 You may have encountered a bug in the Ruby interpreter or extension libraries. 15:42:56 Bug reports are welcome. 15:42:56 For details: http://www.ruby-lang.org/bugreport.html{code}
Add Comment
Jira (PUP-9146) r10k pipelines failing for Ubuntu18 shellgit
Title: Message Title
Amy Sahli updated an issue
Puppet / PUP-9146
r10k pipelines failing for Ubuntu18 shellgit
Change By:
Amy Sahli
*Puppet Version:* current *Puppet Server Version:* current *OS Name/Version:* ONLY shellgit, beaker, ubuntu 1804-64.*Desired Behavior:* Our r10k pipelines for Irving and Johnson branches are all passing*Actual Behavior:*Our r10k pipelines for Irving and Johnson branches are failing. Example:[https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/job/enterprise_r10k_intn-van-sys_irving/GIT_PROVIDER=shellgit,SLAVE_LABEL=beaker,TEST_TARGET=ubuntu1804-64.mdca/22/consoleFull]Various environments are successfully deployed, until at some point one fails with the below output: Test Case tests {code:java}15:42:56 INFO -> Environment c6a5f95de5324a73b988636f86acbe33 is now at 9fbd204382b755fcdb9815222dd46026e61c2501 15:42:56 INFO -> Deploying environment / user_scenario etc / basic_workflow puppetlabs / multi_env_1000_branches code/environments/f856ae9752dd4bcfaca9a6a4fe18dedf 15:42:56 INFO -> Environment f856ae9752dd4bcfaca9a6a4fe18dedf is now at 9fbd204382b755fcdb9815222dd46026e61c2501 15:42:56 INFO -> Deploying environment /etc/puppetlabs/code/environments/f9a687a266e54f8089f28b943c821e31 15:42:56 [ASYNC BUG] (6) 15:42:56 EPIPE 15:42:56 15:42:56 ruby 2 . rb, when "Deploy Environments via r10k" Errored Tests Cases 4.4p296 (2018-03-28 revision 63013) [x86_64-linux] 15 : *11 42 : 29 56 15 : 05* Test Case tests 42:56 [NOTE] 15:42:56 You may have encountered a bug in the Ruby interpreter or extension libraries. 15:42:56 Bug reports are welcome. 15:42:56 For details: http: / user_scenario / basic_workflow www.ruby-lang.org / multi_env_1000_branches bugreport . rb reported html 15 : #< 42:56 15:42:56 ssw16hcquetuscm.delivery.puppetlabs.net (ubuntu1804-64-1) executed in 1.25 seconds 15:42:56 Beaker::Host::CommandFailure: Host ' q9cpm4j0sg4r2qx ssw16hcquetuscm .delivery.puppetlabs.net' connection failure running: *11 15 : 29 42 : 05* 56 /opt/puppetlabs/puppet/bin/r10k deploy environment -v *11 15 : 29 42 : 05* 56 Last 10 lines of output were: *11 15 : 29 42 : 05* 56 INFO -> Deploying environment /etc/puppetlabs/code/environments/ 5137ae6d16eb4cd49d6545189c487fb75137ae6d16eb4cd49d6545189c487fb75137ae6d16eb4cd49d6545189c487fb7*11 f9a687a266e54f8089f28b943c821e31 15 : 29 42 : 05* 56 [ASYNC BUG] (6) *11 15 : 29 42 : 05* 56 EPIPE *11 15 : 29 42 : 05* *11 56 15 : 29 42 : 05* 56 ruby 2.4.4p296 (2018-03-28 revision 63013) [x86_64-linux] *11 15 : 29 42 : 05* *11 56 15 : 29 42 : 05* 56 [NOTE] *11 15 : 29 42 : 05* 56 You may have encountered a bug in the Ruby interpreter or extension libraries. *11 15 : 29 42 : 05* 56 Bug reports are welcome. *11 15 : 29 42 : 05* 56 For details: [ http://www.ruby-lang.org/bugreport.html ] {code}
Jira (PUP-9143) Puppet device raises `undefined method` error
Title: Message Title Maggie Dreyer commented on PUP-9143 Re: Puppet device raises `undefined method` error PR filed. 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-9146) r10k pipelines failing for Ubuntu18 shellgit
Title: Message Title
Amy Sahli updated an issue
Puppet / PUP-9146
r10k pipelines failing for Ubuntu18 shellgit
Change By:
Amy Sahli
*Puppet Version:* current *Puppet Server Version:* current *OS Name/Version:* ONLY shellgit, beaker, ubuntu 1804-64. Describe your issue in as much detail as possible… Describe steps to reproduce… *Desired Behavior:* Our r10k pipelines for Irving and Johnson branches are all passing *Actual Behavior:* Please take a moment Our r10k pipelines for Irving and attach any relevant log output and/or manifests Johnson branches are failing . This will help us immensely when troubleshooting the issue. Example: Examples [https : Run puppet agent with //cinext - jenkinsmaster - test enterprise - prod - trace 1.delivery.puppetlabs.net/job/enterprise_r10k_intn - van - debug sys_irving/GIT_PROVIDER=shellgit,SLAVE_LABEL=beaker,TEST_TARGET=ubuntu1804-64.mdca/22/consoleFull] Relevant sections of {{ Various environments are successfully deployed, until at some point one fails with the below output: Test Case tests / var user_scenario / log basic_workflow / multi_env_1000_branches.rb, when "Deploy Environments via r10k" Errored Tests Cases:*11:29:05* Test Case tests/user_scenario/basic_workflow/multi_env_1000_branches.rb reported: # puppetlabs .net' connection failure running:*11:29:05* / puppetserver opt / puppetserver puppetlabs/puppet/bin/r10k deploy environment -v*11:29:05* Last 10 lines of output were:*11:29:05* INFO -> Deploying environment /etc/puppetlabs/code/environments/5137ae6d16eb4cd49d6545189c487fb75137ae6d16eb4cd49d6545189c487fb75137ae6d16eb4cd49d6545189c487fb7*11:29:05* [ASYNC BUG] (6)*11:29:05* EPIPE*11:29:05* *11:29:05* ruby 2 . log}} or any applicable logs from the same directory 4 . For more detailed information turn up the server logs by upping the log level 4p296 (2018-03-28 revision 63013) [x86_64-linux]*11:29:05* *11:29:05* [NOTE]*11:29:05* You may have encountered a bug in the server's logback Ruby interpreter or extension libraries . xmlRelevant sections of configurations files (puppet *11:29:05* Bug reports are welcome . conf, hiera *11:29:05* For details: [http://www . conf, Server's conf ruby-lang . d, defaults org / sysconfig)For memory issues with server heap dumps are also helpful bugreport . html]
Jira (PUP-9147) External comms on Puppet 6 CA cert changes
Title: Message Title David Mallon created an issue Puppet / PUP-9147 External comms on Puppet 6 CA cert changes Issue Type: Task Affects Versions: PUP 6.0.0 Assignee: Maggie Dreyer Created: 2018/09/17 11:45 AM Fix Versions: PUP 6.0.0 Priority: Normal Reporter: David Mallon Upcoming changes in Puppet 6 around CA cert functionality will likely cause breakages to external users - (thinking of vox pupili and TAPP partners). An email targeting these groups would be great to let them know the changes that will affect them and how they can recover/protect themselves Maggie Dreyer - apologies, not sure who or what team to assign this to so I've added you in off the back of the conversation you, TP and I had around this on Friday - feel free to point the correct person to it if you are not the one Add Comment
Jira (PUP-9146) r10k pipelines failing for Ubuntu18 shellgit
Title: Message Title Amy Sahli created an issue Puppet / PUP-9146 r10k pipelines failing for Ubuntu18 shellgit Issue Type: Bug Assignee: Unassigned Created: 2018/09/17 11:39 AM Priority: Normal Reporter: Amy Sahli Puppet Version: Puppet Server Version: OS Name/Version: Describe your issue in as much detail as possible… Describe steps to reproduce… Desired Behavior: Actual Behavior: Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. Examples: Run puppet agent with --test --trace --debug Relevant sections of /var/log/puppetlabs/puppetserver/puppetserver.log or any applicable logs from the same directory. For more detailed information turn up the server logs by upping the log level in the server's logback.xml Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig) For memory issues with server heap dumps are also helpful. Add Comment
Jira (PUP-9143) Puppet device raises `undefined method` error
Title: Message Title Maggie Dreyer commented on PUP-9143 Re: Puppet device raises `undefined method` error Thanks, I'll put up the naive PR. 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-804) Bolt unable to connect to customer windows 2012 server over winrm
Title: Message Title Michael Smith commented on BOLT-804 Re: Bolt unable to connect to customer windows 2012 server over winrm One scenario we should explore is whether there's a way to enter a username for Discovery where backslashes are lost. If using a Windows domain, then a username might be DOMAIN\User. In Bash, that would result in DOMAINUser without the appropriate escape character (i.e. you need to type DOMAINUser). 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-1882) facter.rb:35: [BUG] Segmentation fault
Title: Message Title David Brůha commented on FACT-1882 Re: facter.rb:35: [BUG] Segmentation fault Yesterday at 4:02 GMT the problem occured for the last time and nothing since. This could really mean a problem with one of memory dimms. Could this be software related? 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-9143) Puppet device raises `undefined method` error
Title: Message Title David Mallon commented on PUP-9143 Re: Puppet device raises `undefined method` error Maggie Dreyer thanks for the quick feedback, if you guys have a potential fix I can work with you to get someone on the Network Automation team to help test it out 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-8913) Agents should re-download CRLs when they are newer than the local copy
Title: Message Title Justin Stoller updated an issue Puppet / PUP-8913 Agents should re-download CRLs when they are newer than the local copy Change By: Justin Stoller Fix Version/s: SERVER 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-8913) Agents should re-download CRLs when they are newer than the local copy
Title: Message Title Justin Stoller commented on PUP-8913 Re: Agents should re-download CRLs when they are newer than the local copy Note: the server side work to enable this will go out in Puppet Server 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-9143) Puppet device raises `undefined method` error
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9143 Puppet device raises `undefined method` error Change By: Kenn Hussey Flagged: Impediment 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-9143) Puppet device raises `undefined method` error
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9143 Puppet device raises `undefined method` error Change By: Kenn Hussey 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-9143) Puppet device raises `undefined method` error
Title: Message Title Maggie Dreyer commented on PUP-9143 Re: Puppet device raises `undefined method` error This is related to the CA removal, yes. Looks like we missed a spot (the PR got shuffled around a lot). I'll need to poke at it a bit find out how big of a change is needed, though at first glance it looks like it might be a one-line change. Unfortunately I don't really have any idea how to test it beyond what our automated tests do (I don't know anything about `puppet device`). So if we need to do some more thorough testing I might need help. 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-9145) puppet run fails with 'unable to get issuer certificate' error after installation in legacy agent job in 2019.0.x
Title: Message Title Shaigy Nixon created an issue Puppet / PUP-9145 puppet run fails with 'unable to get issuer certificate' error after installation in legacy agent job in 2019.0.x Issue Type: CI Blocker Assignee: Unassigned Created: 2018/09/17 10:16 AM Priority: Normal Reporter: Shaigy Nixon puppet agent run fails on the master with following error after installation on master in legacy agent job b5h9ub2qcoiaoj4.delivery.puppetlabs.net (centos6-64-1) 16:55:48$ puppet agent -t Info: Caching certificate for b5h9ub2qcoiaoj4.delivery.puppetlabs.net Error: Could not request certificate: SSL_connect returned=1 errno=0 state=error: certificate verify failed: [unable to get issuer certificate for /CN=Puppet Enterprise CA generated on my8tyb1hy9rgte3.delivery.puppetlabs.net at +2018-09-17 16:49:28 +] Exiting; failed to retrieve certificate and waitforcert is disabled
Jira (PDB-4008) Use jruby-gem-list for all version
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-4008 Use jruby-gem-list for all version Change By: Kenn Hussey Team: PuppetDB 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-3470) Add pdb sandboxing infrastructure, and use it in travis
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3470 Add pdb sandboxing infrastructure, and use it in travis Change By: Kenn Hussey Team: PuppetDB 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 Kenn Hussey updated an issue Puppet / PUP-9110 Accept and produce ASCII_8BIT as Binary value Change By: Kenn Hussey Fix Version/s: PUP 6.0.0 Fix Version/s: PUP 6.0.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-3600) Create support for binary content on the File type
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-3600 Create support for binary content on the File type Change By: Kenn Hussey Fix Version/s: PUP 6.0.0 Fix Version/s: PUP 6.0.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 (BOLT-656) Bypass batching and threading for bolt-server
Title: Message Title Alex Dreyer assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-656 Bypass batching and threading for bolt-server Change By: Alex Dreyer Assignee: 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 (PDB-4090) Has a Puppet DB admin i believe the docs for puppetDB DLO are incorrect please review and amend.
Title: Message Title Austin Blatt commented on PDB-4090 Re: Has a Puppet DB admin i believe the docs for puppetDB DLO are incorrect please review and amend. It looks like that documentation is out of date, and the module you linked to needs fixing. The DLO directory is determined by the user's setting of vardir. With the actual dlo directory being /stockpile/discard/. I'll use this ticket to track the documentation changes to puppetdb, and PDB-4092 to track the bug fix for the module. < /td> 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-4092) Fix hardcoded DLO path in puppetdb module
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4092 Fix hardcoded DLO path in puppetdb module Issue Type: Bug Assignee: Austin Blatt Created: 2018/09/17 9:21 AM Priority: Normal Reporter: 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
Jira (PDB-4091) Investigate what is needed to make pdb module release for pdb 6.0.
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4091 Investigate what is needed to make pdb module release for pdb 6.0. Change By: Zachary Kent Summary: Investigate what is needed to make pdb modules module release for pdb 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 (PDB-4091) Investigate what is needed to make pdb modules release for pdb 6.0.0
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-4091 Investigate what is needed to make pdb modules release for pdb 6.0.0 Change By: Zachary Kent Assignee: Zachary Kent 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-4091) Investigate what is needed to make pdb modules release for pdb 6.0.0
Title: Message Title Zachary Kent created an issue PuppetDB / PDB-4091 Investigate what is needed to make pdb modules release for pdb 6.0.0 Issue Type: Task Assignee: Unassigned Created: 2018/09/17 9:04 AM Priority: Normal Reporter: Zachary Kent look into what changes if any are needed in our testing infrastructure to support pdb 6.0.0 and the puppet ca changes. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-804) Bolt unable to connect to customer windows 2012 server over winrm
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-804 Bolt unable to connect to customer windows 2012 server over winrm Change By: Michael Smith Assignee: Michael Smith 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-804) Bolt unable to connect to customer windows 2012 server over winrm
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-804 Bolt unable to connect to customer windows 2012 server over winrm Change By: Michael Smith Sprint: Bolt Ready for Grooming Kanban 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-9028) Create a `puppet ssl` subcommand that can perform SSL client actions on the agent
Title: Message Title Jacob Helwig commented on PUP-9028 Re: Create a `puppet ssl` subcommand that can perform SSL client actions on the agent Yeah, I'm just marking those as resolved now. We can track everything through this ticket. 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-1883) facter 3.11.4 build broken on OpenBSD utmpx is not available
Title: Message Title Sebastian Reitenbach created an issue Facter / FACT-1883 facter 3.11.4 build broken on OpenBSD utmpx is not available Issue Type: Bug Affects Versions: FACT 3.11.4 Assignee: Unassigned Created: 2018/09/17 6:29 AM Environment: OpenBSD 6.3 amd64 Priority: Normal Reporter: Sebastian Reitenbach in the uptime resolver, facter 3.11.3 was just calling out to the "uptime" binary, in 3.11.4, that change to get the uptime via the utmpx interface, which apparently is not available on OpenBSD, and therefore breaks building. Add Comment
Jira (PDB-4017) Use Puppet's ToStringifiedConverter to handle rich data
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-4017 Use Puppet's ToStringifiedConverter to handle rich data Change By: Kenn Hussey Flagged: Impediment 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-9144) PAL for Catalog Compilation does not evaluate defines and classes
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9144 PAL for Catalog Compilation does not evaluate defines and classes Change By: Henrik Lindberg The PAL support for catalog compilation does not evaluate defines and classes if they are defined inside of the body of the PAL . Thus a catalog will only contain top level instances of classes and resources that were evaluated during the main part of the compilation (i . e. if given a manifest or initial code to evaluate). 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 (PDOC-266) Getting "unexpected construct regexp_literal" when using resource API title_patterns
Title: Message Title Sean Millichamp commented on PDOC-266 Re: Getting "unexpected construct regexp_literal" when using resource API title_patterns No reason I have. Here is a PR: https://github.com/puppetlabs/puppet-strings/pull/189 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 (PDOC-266) Getting "unexpected construct regexp_literal" when using resource API title_patterns
Title: Message Title David Schmitt commented on PDOC-266 Re: Getting "unexpected construct regexp_literal" when using resource API title_patterns That looks like a sensible approach to solve this. Anything speaking against getting that merged right now? 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-8596) Add support for CatalogCompiler in PAL
Title: Message Title Henrik Lindberg commented on PUP-8596 Re: Add support for CatalogCompiler in PAL The initial work was done in the ticket PUP-8973, which is for a different Epic. Closing this ticket in favor of the more detailed PUP-8973. 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-9144) PAL for Catalog Compilation does not evaluate defines and classes
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-9144 PAL for Catalog Compilation does not evaluate defines and classes Issue Type: Bug Assignee: Henrik Lindberg Created: 2018/09/17 5:12 AM Fix Versions: PUP 6.0.1 Priority: Major Reporter: Henrik Lindberg The PAL support for catalog compilation does not evaluate defines and classes. Thus a catalog will only contain top level resources. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDOC-266) Getting "unexpected construct regexp_literal" when using resource API title_patterns
Title: Message Title Sean Millichamp commented on PDOC-266 Re: Getting "unexpected construct regexp_literal" when using resource API title_patterns Sure, here it is: https://github.com/seanmil/puppet-strings/commit/c0165422d677d0f861d6e889e3cc27f8cb109978 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-4090) Has a Puppet DB admin i believe the docs for puppetDB DLO are incorrect please review and amend.
Title: Message Title Adam Buxton created an issue PuppetDB / PDB-4090 Has a Puppet DB admin i believe the docs for puppetDB DLO are incorrect please review and amend. Issue Type: Bug Assignee: Unassigned Components: DOCS Created: 2018/09/17 4:28 AM Priority: Normal Reporter: Adam Buxton Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are
Jira (PDOC-266) Getting "unexpected construct regexp_literal" when using resource API title_patterns
Title: Message Title David Schmitt commented on PDOC-266 Re: Getting "unexpected construct regexp_literal" when using resource API title_patterns I'm glad it's not a "everything on fire" situation. That said, it should definitely not swallow the docs for types using title_patterns. Can you post the patch somewhere, even if we don't think it'll be the right solution. It's at least a pointer to the offending code 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 (PDOC-266) Getting "unexpected construct regexp_literal" when using resource API title_patterns
Title: Message Title Sean Millichamp commented on PDOC-266 Re: Getting "unexpected construct regexp_literal" when using resource API title_patterns It breaks doc generation for the type containing title_patterns - nothing is generated. The other types generate okay. In order to try to ensure comprehensive documentation on everything that we release we do default our pipeline to prohibiting anything though where Strings reports any warnings or any missing coverage (classes, parameters, etc.), but we also have a toggle to enable docs with failures to continue though so I can work around that. I did fiddle around with Strings enough to get a patch that has it continue without any warning, but I wasn't sure if it was a valid approach or not so I stopped working on it. 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-9143) Puppet device raises `undefined method` error
Title: Message Title David Armstrong updated an issue Puppet / PUP-9143 Puppet device raises `undefined method` error Change By: David Armstrong Summary: Puppet device when executed without deviceconfig raises `undefined method` 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-9143) Puppet device when executed without deviceconfig raises `undefined method` error
Title: Message Title David Armstrong updated an issue Puppet / PUP-9143 Puppet device when executed without deviceconfig raises `undefined method` error Change By: David Armstrong Summary: Puppet device when execueted executed without deviceconfig raises `undefined method` 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-9143) Puppet device when execueted without deviceconfig raises `undefined method` error
Title: Message Title David Armstrong created an issue Puppet / PUP-9143 Puppet device when execueted without deviceconfig raises `undefined method` error Issue Type: Bug Affects Versions: PUP 6.0.0 Assignee: Unassigned Created: 2018/09/17 2:56 AM Priority: Blocker Reporter: David Armstrong Puppet Version: 6.0.0 Puppet Server Version: OS Name/Version: The following behaviour was found in `master` and `6.0.x` branches Desired Behavior: Running *`puppet device --verbose --trace --strict=error --modulepath spec/fixtures --target the_node`* should raise an error similar to: `Error: Target device / certificate 'the_node' not found in /Users/david.armstrong/.puppetlabs/etc/puppet/device.conf` Actual Behavior: Instead, the error received is: "undefined method `ca_location=' for Puppet::SSL::Host:Class`" This can be observed in the Travis job: https://travis-ci.org/puppetlabs/puppet-resource_api/builds/429478193?utm_source=github_status_medium=notification Error: Could not prepare for execution: undefined method `ca_location=' for Puppet::SSL::Host:Class /home/travis/build/puppetlabs/puppet-resource_api/vendor/bundle/ruby/2.5.0/bundler/gems/puppet-7a952fe11207/lib/puppet/application/device.rb:382:in `setup'
Jira (PDOC-266) Getting "unexpected construct regexp_literal" when using resource API title_patterns
Title: Message Title David Schmitt updated an issue Puppet Strings / PDOC-266 Getting "unexpected construct regexp_literal" when using resource API title_patterns Change By: David Schmitt Method Found: Needs Assessment Customer Feedback 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 (PDOC-266) Getting "unexpected construct regexp_literal" when using resource API title_patterns
Title: Message Title David Schmitt updated an issue Puppet Strings / PDOC-266 Getting "unexpected construct regexp_literal" when using resource API title_patterns Sean Millichamp, how big is the impact here? Is this only annoying, or does it break doc generation? If the latter, how hard? 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.
