Jira (PDB-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title Rob Browning commented on PDB-2487 Re: Allow for a "resource-events-ttl" to reduce the number of days of events that are stored The plan is for it to make it in to the next "Y" release which I believe is now planned after Lovejoy, and before the LTS, and so the change would be in the LTS that Lovejoy's feeding in to, just not in Lovejoy proper, assuming I understand the current arrangements correctly. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.119255.1456852336000.128602.1570133041515%40Atlassian.JIRA.
Jira (PUP-9973) Can't create users using useradd provider when specifying uid since 6.8.0
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9973 Can't create users using useradd provider when specifying uid since 6.8.0 Change By: Josh Cooper Fix Version/s: PUP 6.4.4 Fix Version/s: PUP 5.5.17 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322037.1566509702000.128769.1570136280440%40Atlassian.JIRA.
Jira (PDB-4278) Add metric to track the number of commands "bashed in place"
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4278 Add metric to track the number of commands "bashed in place" Change By: Austin Blatt Fix Version/s: PDB 6.3.5 Fix Version/s: PDB 5.2.10 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.297778.1551375448000.129173.1570143720502%40Atlassian.JIRA.
Jira (PUP-10084) Prepare documentation updates and release notes (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10084 Prepare documentation updates and release notes (Puppet Platform 6.10.1) Issue Type: Task Assignee: Jean Bond Created: 2019/10/03 4:31 PM Due Date: 2019/10/11 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) Please post a link to the docs PR in the 'Publish Docs' ticket. For X and Y releases, ensure that the WEB team has prepared Drupal for the release. Add Comment
Jira (PDB-4509) Fresh install of puppetdb will not start ERROR: invalid byte sequence for encoding "UTF8"
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4509 Fresh install of puppetdb will not start ERROR: invalid byte sequence for encoding "UTF8" Change By: Austin Blatt Fix Version/s: PDB 6.3.5 Fix Version/s: PDB 5.2.10 Fix Version/s: PDB 6.7.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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.325166.1568831083000.129125.1570142340288%40Atlassian.JIRA.
Jira (PDB-4513) puppetserver fails to connect to puppetdb 6.6.0
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4513 puppetserver fails to connect to puppetdb 6.6.0 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.326149.1569370509000.129133.1570142400844%40Atlassian.JIRA.
Jira (PDB-4513) puppetserver fails to connect to puppetdb 6.6.0
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4513 puppetserver fails to connect to puppetdb 6.6.0 Change By: Austin Blatt Fix Version/s: PDB 6.7.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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.326149.1569370509000.129142.1570142400909%40Atlassian.JIRA.
Jira (PUP-10080) Exec resources fail if the working directory is inaccessible
Title: Message Title Josh Cooper commented on PUP-10080 Re: Exec resources fail if the working directory is inaccessible The base exec provider is defaulting the cwd, which seems wrong if it's not being managed. If I comment out that line, then I run into the facter issue. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327890.1570115712000.128736.1570135920370%40Atlassian.JIRA.
Jira (PUP-10080) Exec resources fail if the working directory is inaccessible
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10080 Exec resources fail if the working directory is inaccessible Change By: Josh Cooper Team: Coremunity 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327890.1570115712000.128739.1570135920382%40Atlassian.JIRA.
Jira (PUP-9824) Expand the apt provider to support virtual packages
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9824 Expand the apt provider to support virtual packages Change By: Josh Cooper Fix Version/s: PUP 6.4.4 Fix Version/s: PUP 5.5.17 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305263.135711000.128778.1570136460291%40Atlassian.JIRA.
Jira (PUP-10016) Systemd provider is not correctly selected as the service provider if puppet is run as non root
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10016 Systemd provider is not correctly selected as the service provider if puppet is run as non root Change By: Josh Cooper Fix Version/s: PUP 6.10.0 Fix Version/s: PUP 6.4.4 Fix Version/s: PUP 5.5.17 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324178.1568121391000.128884.1570137360413%40Atlassian.JIRA.
Jira (PUP-10026) skip_tags not documented for puppet agent
Title: Message Title Jerald Sheets assigned an issue to Josh Cooper I did the pull based on PUP10026 and am assigning it to you on instruction from Ben Ford. (still learning the process) I do hope I did this right!! Puppet / PUP-10026 skip_tags not documented for puppet agent Change By: Jerald Sheets Assignee: Jerald Sheets Josh Cooper 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.325377.1568896957000.128463.1570130280364%40Atlassian.JIRA.
Jira (PUP-9824) Expand the apt provider to support virtual packages
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-9824
Expand the apt provider to support virtual packages
Change By:
Josh Cooper
This seems to be a problem for the rubygems package, particularly in Debian / Ubuntu. I linked to a couple older tickets where this is reported as a minor issue with no workaround.*UPDATE*This ticket added virtual package support for apt & dpkg in 6.8.0, but it unintentionally caused the default value of the {{virtual}} parameter to change from {{false}} to {{true}}. It also caused a regression when packages have special characters in the name (PUP-9975) , and the regex was overly greedy (PUP-9974). The code was reverted in 6.8.1, so puppet does not currently support virtual packages for apt & dpkg. Issue A new ticket PUP-10023 has been fixed filed to re- add virtual package support .
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
Jira (PUP-10080) Exec resources fail if the working directory is inaccessible
Title: Message Title
John Bollinger commented on PUP-10080
Re: Exec resources fail if the working directory is inaccessible
Trace of example 1:
# puppet apply --trace --execute "exec { '/bin/echo': }"
Notice: Compiled catalog for moby.stjude.org in environment production in 0.04 seconds
Error: Working directory /mnt/auto/home/miller2grp/jbolling does not exist!
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/execution.rb:196:in `execute'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/exec.rb:60:in `block in run'
/opt/puppetlabs/puppet/lib/ruby/2.5.0/timeout.rb:93:in `block in timeout'
/opt/puppetlabs/puppet/lib/ruby/2.5.0/timeout.rb:103:in `timeout'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/exec.rb:53:in `run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/exec/posix.rb:45:in `run'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/exec.rb:133:in `block in sync'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/exec.rb:130:in `times'
Jira (PUP-9824) Expand the apt provider to support virtual packages
Title: Message Title Josh Cooper commented on PUP-9824 Re: Expand the apt provider to support virtual packages George Mrejea This is another case where commits for this ticket landed in 5.5.x and 6.4.x, but the original regression and the fix were resolved before 5.5.17 and 6.4.4 releases. So from the user's perspective, the bug never affected the 5.5.x and 6.4.x streams, and we don't want to tag this ticket with those fix versions. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305263.135711000.128775.1570136406727%40Atlassian.JIRA.
Jira (PUP-9824) Expand the apt provider to support virtual packages
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-9824
Expand the apt provider to support virtual packages
Change By:
Josh Cooper
This seems to be a problem for the rubygems package, particularly in Debian / Ubuntu. I linked to a couple older tickets where this is reported as a minor issue with no workaround. *UPDATE*This issue added virtual package support for apt & dpkg, but it caused the default value of the {{virtual}} parameter to change from false to true in 6.8.0. The code was reverted in 6.8.1, so puppet does not currently support virtual packages for apt & dpkg. Issue
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 view this discussion on the web visit
Jira (PUP-10085) Prepare release announcement (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10085 Prepare release announcement (Puppet Platform 6.10.1) Issue Type: Task Assignee: Bill Tang Created: 2019/10/03 4:31 PM Due Date: 2019/10/14 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Jean Bond for review and any important hyperlinks. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary. Add Comment
Jira (PUP-10082) Prepare JIRA and Confluence for release (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10082 Prepare JIRA and Confluence for release (Puppet Platform 6.10.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/03 4:31 PM Due Date: 2019/10/09 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments. 3) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 4) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 5) Update the “master” filters for Puppet Platform 6.10.1 and puppet-agent 6.10.1 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform
Jira (PUP-10081) Puppet Platform 6.10.1 Release - 2019-10-15
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10081 Puppet Platform 6.10.1 Release - 2019-10-15 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/10/03 4:31 PM Due Date: 2019/10/15 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.10.1 Release - 2019-10-15 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10083) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10083 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.10.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/03 4:31 PM Due Date: 2019/10/09 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in Slack) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved. Add Comment
Jira (PUP-10089) Update Confluence and JIRA based on release (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10089 Update Confluence and JIRA based on release (Puppet Platform 6.10.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/03 4:32 PM Due Date: 2019/10/16 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update
Jira (PUP-10087) Publish documentation and updates and release notes (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10087 Publish documentation and updates and release notes (Puppet Platform 6.10.1) Issue Type: Task Assignee: Jean Bond Created: 2019/10/03 4:32 PM Due Date: 2019/10/15 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out. Add Comment
Jira (PUP-10090) Communicate scope and timeline of next release (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10090 Communicate scope and timeline of next release (Puppet Platform 6.10.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/03 4:32 PM Due Date: 2019/10/16 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 1) Create versions and filters for the release in in JIRA. Ensure that the filters are shared with the ‘All Employees’ group. 2) Create or update the Kanban board for the release series. Ensure that the underlying filter for the board includes issues from the release filter and add a quick filter to highlight just those issues. 3) Create Release tickets (in the Project Central project) for the Puppet Platform and puppet-agent releases, with sub-tasks for each milestone (e.g., “String Freeze”, “Stop Ship Line”, “Ready to Ship”, and “General Availability (GA)”. 4) Create release pages for the Puppet Platform and puppet-agent releases in Confluence, under the appropriate “Upcoming Releases” parent page. Make sure the pages reference the release filters, tickets, and Kanban board as needed. 5) Update the “Versions & Dependencies” pages for Puppet Platform and puppet-agent with dependency versions for releases. Format the release versions in italics and link them to their corresponding release pages. 6) Add events for the release milestone dates to Group-Platform Google calendar. Ensure the description for each event includes a link to the release page. 7) Send an email to stakeholders (e.g., puppet-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release.
Jira (PUP-10086) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10086 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.10.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/10/03 4:32 PM Due Date: 2019/10/14 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in #proj-puppet-releases Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-10088) Send release announcement (Puppet Platform 6.10.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-10088 Send release announcement (Puppet Platform 6.10.1) Issue Type: Task Assignee: Molly Waggett Created: 2019/10/03 4:32 PM Due Date: 2019/10/15 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account - Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 6.10.1 is now available".
Jira (PDB-4509) Fresh install of puppetdb will not start ERROR: invalid byte sequence for encoding "UTF8"
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4509 Fresh install of puppetdb will not start ERROR: invalid byte sequence for encoding "UTF8" 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.325166.1568831083000.128644.1570133940981%40Atlassian.JIRA.
Jira (PDB-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title Rob Browning commented on PDB-2487 Re: Allow for a "resource-events-ttl" to reduce the number of days of events that are stored Oh, and perhaps worth noting that the relevant work has actually now been folded in to this PR https://github.com/puppetlabs/puppetdb/pull/3027 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.119255.1456852336000.129116.1570141741384%40Atlassian.JIRA.
Jira (PUP-10080) Exec resources fail if the working directory is inaccessible
Title: Message Title Josh Cooper commented on PUP-10080 Re: Exec resources fail if the working directory is inaccessible I don't have an easy way to reproduce example 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327890.1570115712000.129183.1570143900124%40Atlassian.JIRA.
Jira (PUP-9824) Expand the apt provider to support virtual packages
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-9824
Expand the apt provider to support virtual packages
Change By:
Josh Cooper
This seems to be a problem for the rubygems package, particularly in Debian / Ubuntu. I linked to a couple older tickets where this is reported as a minor issue with no workaround.*UPDATE*This issue ticket added virtual package support for apt & dpkg in 6.8.0 , but it unintentionally caused the default value of the {{virtual}} parameter to change from {{ false }} to {{ true in 6 }} . 8.0. It also caused a regression when packages have special characters in the name (PUP-9975) The code was reverted in 6.8.1, so puppet does not currently support virtual packages for apt & dpkg. IssuePUP-10023 has been fixed to re-add virtual package support
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
Jira (PDB-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title Dylan Ratcliffe commented on PDB-2487 Re: Allow for a "resource-events-ttl" to reduce the number of days of events that are stored Rob Browning Is there nothing we can do to get this moving faster? The ticket's been open for three years, there are at least 45 customers affected (the ones linked here) and it's pretty crippling for those that it does affect, plus it seems that the code is done. Though there is a workaround it's not normally a quick thing to diagnose and the implementation is pretty ugly. Plus if we were to be aggressive and set the ttl to say 2 days (since the console only ever uses one day for the event inspector) then we would likely mean that nobody ever needs to actually raise the ticket in the first place. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.119255.1456852336000.128816.1570136641304%40Atlassian.JIRA.
Jira (PUP-10080) Exec resources fail if the working directory is inaccessible
Title: Message Title
John Bollinger commented on PUP-10080
Re: Exec resources fail if the working directory is inaccessible
Huh. Do you reproduce example 1 with unmodified Puppet, Josh Cooper? Because when I hit the facter issue, it seems like puppet doesn't go anywhere at all – even puppet help fails – yet under Example 1 circumstances (the working directory exists but is inaccessible) an Exec with cwd set applies successfully for me. That would be Example 3
Set up as in Example 1
Execute the command
puppet apply --execute "exec { '/bin/echo': cwd => '/tmp' }"
The catalog is compiled and applied successfully in that case.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed
Jira (FACT-2055) Facter fails if its working directory does not exist
Title: Message Title John Bollinger created an issue Facter / FACT-2055 Facter fails if its working directory does not exist Issue Type: Bug Affects Versions: FACT 3.14.3 Assignee: Unassigned Components: CLI Created: 2019/10/03 12:00 PM Priority: Minor Reporter: John Bollinger Originally reported as part of PUP-10080: puppet fails if its working directory does not exist. Josh Cooper attributes the failure to Facter, and indeed, the standalone facter executable seems to exhibit related behavior. All puppet faces seem to be affected, including those that have no plausible need for working-directory access, such as puppet help. Facter does not exhibit such a failure when the working directory exists but is inaccessible to it. Expected behavior When its working directory does not exist, facter should nevertheless run successfully and evaluate and report all the facts it can do. This should happen for both the standalone executable and for the Puppet-integrated version. Observed behavior Facter crashes immediately when its working directory does not exist. For the puppet-integrated version, this crashes the whole puppet process. To reproduce 1. Create a fresh directory for the experiment: mkdir doomed. 2. Make that directory the working directory: cd doomed. 3. In a separate shell, remove the directory: rm doomed. 4. In the first shell, run facter or any Puppet command at all, for example facter
Jira (PUP-10026) skip_tags not documented for puppet agent
Title: Message Title Jerald Sheets assigned an issue to Jerald Sheets Puppet / PUP-10026 skip_tags not documented for puppet agent Change By: Jerald Sheets Assignee: Jerald Sheets 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.325377.1568896957000.128389.1570129260756%40Atlassian.JIRA.
Jira (PUP-10080) Exec resources fail if the working directory is inaccessible
Title: Message Title John Bollinger commented on PUP-10080 Re: Exec resources fail if the working directory is inaccessible FACT-2055 created for the Facter side. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327890.1570115712000.128396.1570129260821%40Atlassian.JIRA.
Jira (PUP-10026) skip_tags not documented for puppet agent
Title: Message Title Jerald Sheets commented on PUP-10026 Re: skip_tags not documented for puppet agent I added the documentation for --skip_tags to the agent file puppet/lib/puppet/application/agent.rb as follows: '--skip_tags' is a flag used to filter resources. If this is set, then only resources not tagged with the specified tags will be applied. Values must be comma-separated. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.325377.1568896957000.128421.1570129980935%40Atlassian.JIRA.
Jira (PDB-4541) Merge-up, branch, and create pipelines (PuppetDB 6.7.1)
Title: Message Title
Nirupama Mantha created an issue
PuppetDB / PDB-4541
Merge-up, branch, and create pipelines (PuppetDB 6.7.1)
Issue Type:
Task
Assignee:
Austin Blatt
Created:
2019/10/03 4:34 PM
Due Date:
2019/10/08
Priority:
Normal
Reporter:
Nirupama Mantha
(Initial planned release date: 2019-10-15) Is the code ready for release? Check that the latest nightly ("Periodic") build was green. You only need to check the links that are relevant to the release that you're preparing (for example, doing a release that doesn't include LTS).
master: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/master
6.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
5.2.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.2.x/
pe-puppetdb-extensions travis builds: https://travis-ci.com/puppetlabs/pe-puppetdb-extensions/branches
Do merge-ups:
Merge 5.2.x -> 6.3.x
Merge
Jira (PDB-4544) Check builds, promote to PE (PuppetDB 6.7.1)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4544 Check builds, promote to PE (PuppetDB 6.7.1) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/03 4:35 PM Due Date: 2019/10/11 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) Check that all the builds are green. Choose the tab for your branch over at https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/, then run the "manual promotion kickoff" job with the GIT_SHA set to the git tag version and PROMOTION_ENABLED set to TRUE. Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release. Remember to revert pe-puppetdb-extensions to reading the version from the file
Jira (PDB-4542) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.7.1)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4542 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.7.1) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/03 4:34 PM Due Date: 2019/10/08 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Once fixVersions are set for all tickets, verify that each ticket has the proper release notes Add Comment
Jira (PDB-4543) Bump versions, push directly, and tag (PuppetDB 6.7.1)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4543 Bump versions, push directly, and tag (PuppetDB 6.7.1) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/03 4:34 PM Due Date: 2019/10/11 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) (if you're making the first release off a new branch you may already have done some of this) Check that there aren't any essential updates to ezbake needed in this release and that the ezbake versions match between puppetdb and pe-puppetdb-extensions before pushing a non-snapshot version and tagging. Disable automatic promotions: If this release will be released in a PE release, disable automatic promotions on the branch(es) you are releasing from. This is done via a PR to ci-job-configs, see https://github.com/puppetlabs/ci-job-configs/pull/6324/files for an example. Set the real version for release: Remove the -SNASPHOT portion of the verison in project.clj in puppetdb and push directly to the branch you're releasing. Go into the '#release-new-new' Slack channel to make yourself a tag ! tag puppetdb at with Remove the -SNASPHOT portions of the versions in
Jira (PDB-4545) Update winston (PuppetDB 6.7.1)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4545 Update winston (PuppetDB 6.7.1) Issue Type: Task Assignee: Austin Blatt Created: 2019/10/03 4:35 PM Due Date: 2019/10/16 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-10-15) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-2052) Implement Config Options Class
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2052 Implement Config Options Class Issue Type: Task Assignee: Unassigned Created: 2019/10/03 12:42 AM Priority: Normal Reporter: Sebastian Miclea We need a way to handle all flags that can be added to facter and make them available everywhere in the code. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10016) Systemd provider is not correctly selected as the service provider if puppet is run as non root
Title: Message Title George Mrejea updated an issue Puppet / PUP-10016 Systemd provider is not correctly selected as the service provider if puppet is run as non root Change By: George Mrejea Fix Version/s: PUP 6.4.4 Fix Version/s: PUP 5.5.17 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324178.1568121391000.127316.1570099560301%40Atlassian.JIRA.
Jira (PUP-10013) Update minitar version and call new fsync=false option
Title: Message Title George Mrejea updated an issue Puppet / PUP-10013 Update minitar version and call new fsync=false option Change By: George Mrejea Fix Version/s: PUP 5.5.z Fix Version/s: PUP 5.5.17 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323877.1567788493000.127309.1570099500540%40Atlassian.JIRA.
Jira (FACT-2053) Kernel facts for Solaris
Title: Message Title Alexandru Popa created an issue Facter / FACT-2053 Kernel facts for Solaris Issue Type: Task Assignee: Unassigned Created: 2019/10/03 3:54 AM Priority: Normal Reporter: Alexandru Popa 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 view this discussion on the web visit
Jira (PUP-9754) Log resident configuration upon daemon launch
Title: Message Title George Mrejea updated an issue Puppet / PUP-9754 Log resident configuration upon daemon launch Change By: George Mrejea Fix Version/s: PUP 6.4.4 Fix Version/s: PUP 5.5.17 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312512.1560543853000.127411.1570101840709%40Atlassian.JIRA.
Jira (PUP-9928) New installers no longer needs puppetres.dll
Title: Message Title George Mrejea updated an issue Puppet / PUP-9928 New installers no longer needs puppetres.dll Change By: George Mrejea Fix Version/s: PUP 6.4.4 Fix Version/s: PUP 5.5.17 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318202.156413329.127427.1570101900176%40Atlassian.JIRA.
Jira (PUP-9908) When setting ensure=running on a osx service, Puppet is reporting the service as absent
Title: Message Title George Mrejea updated an issue Puppet / PUP-9908 When setting ensure=running on a osx service, Puppet is reporting the service as absent Change By: George Mrejea Fix Version/s: PUP 6.4.4 Fix Version/s: PUP 5.5.17 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.317053.1563430406000.127424.1570101840767%40Atlassian.JIRA.
Jira (PUP-9824) Expand the apt provider to support virtual packages
Title: Message Title George Mrejea updated an issue Puppet / PUP-9824 Expand the apt provider to support virtual packages Change By: George Mrejea Fix Version/s: PUP 6.4.4 Fix Version/s: PUP 5.5.17 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305263.135711000.127417.1570101840739%40Atlassian.JIRA.
Jira (PUP-9249) Backport sensitive DSL method PUP-8514
Title: Message Title George Mrejea updated an issue Puppet / PUP-9249 Backport sensitive DSL method PUP-8514 Change By: George Mrejea Fix Version/s: PUP 5.5.z Fix Version/s: PUP 6.4.4 Fix Version/s: PUP 5.5.17 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.281329.1539907632000.127392.1570101660258%40Atlassian.JIRA.
Jira (PUP-9722) Regression: File mode changed on every puppet run
Title: Message Title George Mrejea updated an issue Puppet / PUP-9722 Regression: File mode changed on every puppet run Change By: George Mrejea Fix Version/s: PUP 6.4.4 Fix Version/s: PUP 5.5.17 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310253.1558976203000.127404.1570101728460%40Atlassian.JIRA.
Jira (PUP-9605) Type package (provider yum) fails when handling kernel packages
Title: Message Title George Mrejea updated an issue Puppet / PUP-9605 Type package (provider yum) fails when handling kernel packages Change By: George Mrejea Fix Version/s: PUP 6.4.4 Fix Version/s: PUP 5.5.17 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.303636.1554712703000.127397.1570101728358%40Atlassian.JIRA.
Jira (PUP-9973) Can't create users using useradd provider when specifying uid since 6.8.0
Title: Message Title George Mrejea updated an issue Puppet / PUP-9973 Can't create users using useradd provider when specifying uid since 6.8.0 Change By: George Mrejea Fix Version/s: PUP 6.4.4 Fix Version/s: PUP 5.5.17 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322037.1566509702000.127436.1570101960389%40Atlassian.JIRA.
Jira (PDB-4540) DNS_ALT_NAMES set by docker puppetdb >= 6.6.0
Title: Message Title
Christoph Roeder updated an issue
PuppetDB / PDB-4540
DNS_ALT_NAMES set by docker puppetdb >= 6.6.0
Change By:
Christoph Roeder
*Puppet Version: 6.7.0* *Puppet Server Version: 6.7.0* *OS Name/Version: Ubuntu 18.04*puppetdb 6.6.0 and upwards creates an dns alt cert even if no env variable DNS_ALT_NAMES is set.*Desired Behavior:* create an cert for puppetdb*Actual Behavior:* created an cert for puppetdb with alt name "puppetdb,"puppetdb_1 | Running /docker-entrypoint.d/30-configure-ssl.sh puppetdb_1 | (/ssl.sh) Using configuration values: puppetdb_1 | (/ssl.sh) * CERTNAME: 'puppetdb' (/CN=puppetdb) {color:# FF ff }puppetdb_1 | (/ssl.sh) * DNS_ALT_NAMES: 'puppetdb,' {color}puppetdb_1 | (/ssl.sh) * CA: 'https://puppet:8140/puppet-ca/v1' puppetdb_1 | (/ssl.sh) * SSLDIR: '/opt/puppetlabs/server/data/puppetdb/certs' puppetdb_1 | (/ssl.sh) * WAITFORCERT: '120' seconds puppetdb_1 | subject=CN = Puppet CA: puppet.home.roeder.io puppetdb_1 | issuer=CN = Puppet CA: puppet.home.roeder.io puppetdb_1 | (/ssl.sh) Error: CA already has signed certificate for 'puppetdb' The Problem was introduced here [https://github.com/puppetlabs/puppetdb/commit/023bfcd0fd9e703e384e8167c768e61f22e46919]
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-10013) Update minitar version and call new fsync=false option
Title: Message Title George Mrejea updated an issue Puppet / PUP-10013 Update minitar version and call new fsync=false option Change By: George Mrejea Fix Version/s: PUP 6.4.z Fix Version/s: PUP 6.4.4 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323877.1567788493000.127313.1570099500601%40Atlassian.JIRA.
Jira (PUP-8319) Win-2012r2 FR Puppet Acceptance showing 4 test failures (localisation)
Title: Message Title George Mrejea updated an issue Puppet / PUP-8319 Win-2012r2 FR Puppet Acceptance showing 4 test failures (localisation) Change By: George Mrejea Fix Version/s: PUP 6.4.4 Fix Version/s: PUP 5.5.17 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.229124.1515149849000.127389.1570101600620%40Atlassian.JIRA.
Jira (PUP-7312) Confine systemd provider to init system matching systemd
Title: Message Title George Mrejea updated an issue Puppet / PUP-7312 Confine systemd provider to init system matching systemd Change By: George Mrejea Fix Version/s: PUP 6.4.4 Fix Version/s: PUP 5.5.17 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.178941.1488893881000.127387.1570101600610%40Atlassian.JIRA.
Jira (PUP-9752) Systemd should be default service provider for Debian buster
Title: Message Title George Mrejea updated an issue Puppet / PUP-9752 Systemd should be default service provider for Debian buster Change By: George Mrejea Fix Version/s: PUP 6.4.4 Fix Version/s: PUP 5.5.17 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312293.1560388027000.127406.1570101780210%40Atlassian.JIRA.
Jira (FACT-2054) Facter::Core::Execution.execute incorrectly expands shell builtins
Title: Message Title
Charlie Sharpsteen updated an issue
Facter / FACT-2054
Facter::Core::Execution.execute incorrectly expands shell builtins
Change By:
Charlie Sharpsteen
When executing commands, Facter will expand the first word in the command string to be a fully qualified path. I.e. {{ls -l}} will become {{/usr/bin/ls -l}}. If the command string is a compound command that contains a pipeline or looping construct, then Facter will wrap the executing in {{/bin/sh -c}}.However, the first word of the compound is still expanded to an absolute path. This breaks shell builtins like {{cd}} as they are expanded to external commands like {{/usr/bin/cd}} or fail to be found on the PATH.h2. Reproduction Case- Install the latest version of {{puppet-agent}} on CentOS 7, along with strace:{code:bash}yum install -y http://yum.puppetlabs.com/puppet-release-el-7.noarch.rpmyum install -y puppet-agent strace{code}- Create a test script that loads Facter, and uses it to execute a compound command that begins with {{cd}}:{code:bash}cat < test.rb#!/opt/puppetlabs/puppet/bin/rubyrequire 'facter'puts Facter::Core::Execution.execute('cd /opt/puppetlabs && ls')EOFchmod +x test.rb{code} - Execute the test scrip script .h3. OutcomeThe script prints the contents of the current working directory instead of {{/opt/puppetlabs}}:{noformat}# ./test.rb1anaconda-ks.cfglinux.isotest.rb{noformat}Running the script under strrace reveals that {{cd}} is being expanded to {{/usr/bin/cd}} before being passed to {{sh -c}}:{noformat}# strace -f -e trace=execve ./test.rbexecve("./test.rb", ["./test.rb"], [/* 23 vars */]) = 0strace: Process 20373 attachedstrace: Process 20374 attached[pid 20374] execve("/usr/bin/sh", ["sh", "-c", "/usr/bin/cd /opt/puppetlabs && l"...], [/* 24 vars */]) = 0strace: Process 20375 attached[pid 20375] execve("/usr/bin/cd", ["/usr/bin/cd", "/opt/puppetlabs"], [/* 24 vars */]) = 0[pid 20375] +++ exited with 0 +++[pid 20374] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=20375, si_uid=0, si_status=0, si_utime=0, si_stime=0} ---strace: Process 20376 attached[pid 20376] execve("/usr/bin/ls", ["ls"], [/* 24 vars */]) = 0[pid 20376] +++ exited with 0 +++[pid 20374] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=20376, si_uid=0, si_status=0, si_utime=0, si_stime=0} ---[pid 20374] +++ exited with 0 +++[pid 20372] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=20374, si_uid=0, si_status=0, si_utime=0, si_stime=0} ---1anaconda-ks.cfglinux.isotest.rb[pid 20373] +++ exited with 0 ++ exited with 0 +++{noformat}h3. Expected OutcomeThe script prints the content of {{/opt/puppetlabs}}:{noformat}# ./test.rbbinfacterpuppetpxp-agent{noformat}h3. Suggested WorkaroundThe expansion only affects the first word in the command line, so adding an extra {{true &&}} to the compound command acts as a sacrificial noop that takes the hit instead.
Jira (FACT-2054) Facter::Core::Execution.execute incorrectly expands shell builtins
Title: Message Title Charlie Sharpsteen created an issue Facter / FACT-2054 Facter::Core::Execution.execute incorrectly expands shell builtins Issue Type: Bug Assignee: Unassigned Created: 2019/10/03 7:03 AM Priority: Normal Reporter: Charlie Sharpsteen When executing commands, Facter will expand the first word in the command string to be a fully qualified path. I.e. ls -l will become /usr/bin/ls -l. If the command string is a compound command that contains a pipeline or looping construct, then Facter will wrap the executing in /bin/sh -c. However, the first word of the compound is still expanded to an absolute path. This breaks shell builtins like cd as they are expanded to external commands like /usr/bin/cd or fail to be found on the PATH. Reproduction Case Install the latest version of puppet-agent on CentOS 7, along with strace: yum install -y http://yum.puppetlabs.com/puppet-release-el-7.noarch.rpm yum install -y puppet-agent strace Create a test script that loads Facter, and uses it to execute a compound command that begins with cd:
Jira (FACT-2054) Facter::Core::Execution.execute incorrectly expands shell builtins
Title: Message Title Charlie Sharpsteen updated an issue Facter / FACT-2054 Facter::Core::Execution.execute incorrectly expands shell builtins Change By: Charlie Sharpsteen Team: Night's Watch 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327886.1570111406000.127523.1570111680091%40Atlassian.JIRA.
Jira (FACT-2054) Facter::Core::Execution.execute incorrectly expands shell builtins
Title: Message Title
Charlie Sharpsteen updated an issue
Facter / FACT-2054
Facter::Core::Execution.execute incorrectly expands shell builtins
Change By:
Charlie Sharpsteen
When executing commands, Facter will expand the first word in the command string to be a fully qualified path. I.e. {{ls -l}} will become {{/usr/bin/ls -l}}. If the command string is a compound command that contains a pipeline or looping conditional construct, then Facter will wrap the executing string in {{/ usr/ bin/sh -c}}.However, the first word of the compound is still expanded to an absolute path. This breaks shell builtins like {{cd}} as they are expanded to external commands like {{/usr/bin/cd}} or fail to be found on the PATH.h2. Reproduction Case- Install the latest version of {{puppet-agent}} on CentOS 7, along with strace:{code:bash}yum install -y http://yum.puppetlabs.com/puppet-release-el-7.noarch.rpmyum install -y puppet-agent strace{code}- Create a test script that loads Facter, and uses it to execute a compound command that begins with {{cd}}:{code:bash}cat < test.rb#!/opt/puppetlabs/puppet/bin/rubyrequire 'facter'puts Facter::Core::Execution.execute('cd /opt/puppetlabs && ls')EOFchmod +x test.rb{code} - Execute the test script.h3. OutcomeThe script prints the contents of the current working directory instead of {{/opt/puppetlabs}}:{noformat}# ./test.rb1anaconda-ks.cfglinux.isotest.rb{noformat}Running the script under strrace reveals that {{cd}} is being expanded to {{/usr/bin/cd}} before being passed to {{sh -c}}:{noformat}# strace -f -e trace=execve ./test.rbexecve("./test.rb", ["./test.rb"], [/* 23 vars */]) = 0strace: Process 20373 attachedstrace: Process 20374 attached[pid 20374] execve("/usr/bin/sh", ["sh", "-c", "/usr/bin/cd /opt/puppetlabs && l"...], [/* 24 vars */]) = 0strace: Process 20375 attached[pid 20375] execve("/usr/bin/cd", ["/usr/bin/cd", "/opt/puppetlabs"], [/* 24 vars */]) = 0[pid 20375] +++ exited with 0 +++[pid 20374] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=20375, si_uid=0, si_status=0, si_utime=0, si_stime=0} ---strace: Process 20376 attached[pid 20376] execve("/usr/bin/ls", ["ls"], [/* 24 vars */]) = 0[pid 20376] +++ exited with 0 +++[pid 20374] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=20376, si_uid=0, si_status=0, si_utime=0, si_stime=0} ---[pid 20374] +++ exited with 0 +++[pid 20372] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=20374, si_uid=0, si_status=0, si_utime=0, si_stime=0} ---1anaconda-ks.cfglinux.isotest.rb[pid 20373] +++ exited with 0 ++ exited with 0 +++{noformat}h3. Expected OutcomeThe script prints the content of {{/opt/puppetlabs}}:{noformat}# ./test.rbbinfacterpuppetpxp-agent{noformat}h3. Suggested WorkaroundThe expansion only affects the first word in the command line, so adding an extra {{true &&}} to the compound command acts as a sacrificial noop that takes the hit instead.
Jira (PUP-10080) Exec resources fail if the working directory is inaccessible
Title: Message Title John Bollinger created an issue Puppet / PUP-10080 Exec resources fail if the working directory is inaccessible Issue Type: Bug Affects Versions: PUP 6.8.1 Assignee: Unassigned Components: Types and Providers, UX Created: 2019/10/03 8:15 AM Priority: Minor Reporter: John Bollinger Puppet Version: 6.8.1 Puppet Server Version: 6.5.0 OS Name/Version: CentOS 7 Exec resources fail unnecessarily when the working directory from which the 'agent' or 'apply' face is launched does not exist or is inaccessible to puppet. Additionally, in the event that the working directory exists but is inaccessible to the process, the diagnostic emitted incorrectly reports that the directory does not exist. I typically observe this on machines where my home directory is NFS-mounted, such that it is inaccessible to the local root account. With that as my working directory, I sudo a privileged shell in which to run the Puppet agent, but catalog application fails on account of errors from multiple Exec resources. Changing directory to a root-accessible one allows catalog application to succeed. In at least some cases, the command being executed is insensitive to the accessibility of the working directory, so there's no particular reason that the Exec should fail. Desired Behavior: Exec resources should not automatically fail on account of a missing or inaccessible working directory, unless a specific working directory is requested via the cwd parameter. Puppet, generally, should not rely on the working directory being accessible except where it actually needs to access it for some configuration-, face-, or catalog-specific reason. Actual Behavior: Exec resources spuriously fail when the working directory cannot be accessed, even when no particular working directory is
Jira (PUP-10080) Exec resources fail if the working directory is inaccessible
Title: Message Title
John Bollinger updated an issue
Puppet / PUP-10080
Exec resources fail if the working directory is inaccessible
Change By:
John Bollinger
*Puppet Version:* 6.8.1 *Puppet Server Version:* 6.5.0 *OS Name/Version:* CentOS 7Exec resources fail unnecessarily when the working directory from which the 'agent' or 'apply' face is launched does not exist or is inaccessible to puppet. Additionally, in the event that the working directory exists but is inaccessible to the process, the diagnostic emitted incorrectly reports that the directory does not exist.I typically observe this on machines where my home directory is NFS-mounted, such that it is inaccessible to the local root account. With that as my working directory, I {{sudo}} a privileged shell in which to run the Puppet agent, but catalog application fails on account of errors from multiple {{Exec}} resources. Changing directory to a root-accessible one allows catalog application to succeed. In at least some cases, the command being executed is insensitive to the accessibility of the working directory, so there's no particular reason that the {{Exec}} should fail.*Desired Behavior:*{{Exec}} resources should not automatically fail on account of a missing or inaccessible working directory, unless a specific working directory is requested via the {{cwd}} parameter.Puppet, generally, should not rely on the working directory being accessible except where it actually needs to access it for some configuration-, face-, or catalog-specific reason.*Actual Behavior:*{{Exec}} resources spuriously fail when the working directory cannot be accessed, even when no particular working directory is specified, and even when execution of the command does not depend on accessing the working directory. The specific failure mode seems to depend on details of the situation, but the one I normally run into can be reproduced with {{puppet apply}}, too, like so:*Example 1*1. log in to a machine on which my home directory is on an automounted NFS file system with root squashing in effect 2. {{sudo bash}} to obtain a root shell 3. Execute{code:shell}puppet apply --execute "exec { '/bin/echo': }"{code}*_Output:_*{quote}Notice: Compiled catalog for moby xxx . stjude yyy . org zzz in environment production in 0.04 seconds Error: Working directory /mnt/auto/home/ miller2grp a_group /jbolling does not exist! Error: /Stage[main]/Main/Exec[/bin/echo]/returns: change from 'notrun' to ['0'] failed: Working directory /mnt/auto/home/miller2grp/jbolling does not exist! Notice: Applied catalog in 0.12 seconds{quote}Errors of the same form are also reported by the agent under these circumstances if the catalog being applied contains `Exec` resources without {{cwd}} parameters. On the other hand, these particular failures do not occur if the {{Exec}} in question has a {{cwd}} parameter designating an existing, accessible directory, notwithstanding that the Puppet process's own working directory is inaccessible to it.Oddly enough, a different failure occurs if
Jira (PUP-10080) Exec resources fail if the working directory is inaccessible
Title: Message Title
John Bollinger updated an issue
Puppet / PUP-10080
Exec resources fail if the working directory is inaccessible
Change By:
John Bollinger
*Puppet Version:* 6.8.1 *Puppet Server Version:* 6.5.0 *OS Name/Version:* CentOS 7Exec resources fail unnecessarily when the working directory from which the 'agent' or 'apply' face is launched does not exist or is inaccessible to puppet. Additionally, in the event that the working directory exists but is inaccessible to the process, the diagnostic emitted incorrectly reports that the directory does not exist.I typically observe this on machines where my home directory is NFS-mounted, such that it is inaccessible to the local root account. With that as my working directory, I {{sudo}} a privileged shell in which to run the Puppet agent, but catalog application fails on account of errors from multiple {{Exec}} resources. Changing directory to a root-accessible one allows catalog application to succeed. In at least some cases, the command being executed is insensitive to the accessibility of the working directory, so there's no particular reason that the {{Exec}} should fail.*Desired Behavior:*{{Exec}} resources should not automatically fail on account of a missing or inaccessible working directory, unless a specific working directory is requested via the {{cwd}} parameter.Puppet, generally, should not rely on the working directory being accessible except where it actually needs to access it for some configuration-, face-, or catalog-specific reason.*Actual Behavior:*{{Exec}} resources with no {{cwd}} spuriously specified fail spuriously when Puppet's working directory cannot be accessed, even when execution of the command does not depend on accessing that directory. The specific failure mode seems to depend on details of the situation, but the one I normally run into can be reproduced with {{puppet apply}}, too, like so:*Example 1*1. log in to a machine on which my home directory is on an automounted NFS file system with root squashing in effect 2. {{sudo bash}} to obtain a root shell 3. Execute{code:shell}puppet apply --execute "exec { '/bin/echo': }"{code}*_Output:_*{quote}Notice: Compiled catalog for xxx.yyy.zzz in environment production in 0.04 seconds Error: Working directory /mnt/auto/home/a_group/jbolling does not exist! Error: /Stage[main]/Main/Exec[/bin/echo]/returns: change from 'notrun' to ['0'] failed: Working directory /mnt/auto/home/miller2grp/jbolling does not exist! Notice: Applied catalog in 0.12 seconds{quote}Errors of the same form are also reported by the agent under these circumstances if the catalog being applied contains `Exec` resources without {{cwd}} parameters. On the other hand, these particular failures do not occur if the {{Exec}} in question has a {{cwd}} parameter designating an existing, accessible directory, notwithstanding that the Puppet process's own working directory is inaccessible to it.Oddly enough, a different failure occurs if Puppet's working directory actually doesn't exist. That
Jira (PUP-10080) Exec resources fail if the working directory is inaccessible
Title: Message Title
John Bollinger updated an issue
Puppet / PUP-10080
Exec resources fail if the working directory is inaccessible
Change By:
John Bollinger
*Puppet Version:* 6.8.1 *Puppet Server Version:* 6.5.0 *OS Name/Version:* CentOS 7Exec resources fail unnecessarily when the working directory from which the 'agent' or 'apply' face is launched does not exist or is inaccessible to puppet. Additionally, in the event that the working directory exists but is inaccessible to the process, the diagnostic emitted incorrectly reports that the directory does not exist.I typically observe this on machines where my home directory is NFS-mounted, such that it is inaccessible to the local root account. With that as my working directory, I {{sudo}} a privileged shell in which to run the Puppet agent, but catalog application fails on account of errors from multiple {{Exec}} resources. Changing directory to a root-accessible one allows catalog application to succeed. In at least some cases, the command being executed is insensitive to the accessibility of the working directory, so there's no particular reason that the {{Exec}} should fail.*Desired Behavior:*{{Exec}} resources should not automatically fail on account of a missing or inaccessible working directory, unless a specific working directory is requested via the {{cwd}} parameter.Puppet, generally, should not rely on the working directory being accessible except where it actually needs to access it for some configuration-, face-, or catalog-specific reason.*Actual Behavior:*{{Exec}} resources with no {{cwd}} spuriously fail when the Puppet's working directory cannot be accessed, even when no particular working directory is specified, and even when execution of the command does not depend on accessing the working that directory. The specific failure mode seems to depend on details of the situation, but the one I normally run into can be reproduced with {{puppet apply}}, too, like so:*Example 1*1. log in to a machine on which my home directory is on an automounted NFS file system with root squashing in effect 2. {{sudo bash}} to obtain a root shell 3. Execute{code:shell}puppet apply --execute "exec { '/bin/echo': }"{code}*_Output:_*{quote}Notice: Compiled catalog for xxx.yyy.zzz in environment production in 0.04 seconds Error: Working directory /mnt/auto/home/a_group/jbolling does not exist! Error: /Stage[main]/Main/Exec[/bin/echo]/returns: change from 'notrun' to ['0'] failed: Working directory /mnt/auto/home/miller2grp/jbolling does not exist! Notice: Applied catalog in 0.12 seconds{quote}Errors of the same form are also reported by the agent under these circumstances if the catalog being applied contains `Exec` resources without {{cwd}} parameters. On the other hand, these particular failures do not occur if the {{Exec}} in question has a {{cwd}} parameter designating an existing, accessible directory, notwithstanding that the Puppet process's own working directory is inaccessible to it.Oddly enough, a different failure
Jira (PDB-4540) DNS_ALT_NAMES set by docker puppetdb >= 6.6.0
Title: Message Title Christoph Roeder created an issue PuppetDB / PDB-4540 DNS_ALT_NAMES set by docker puppetdb >= 6.6.0 Issue Type: Bug Affects Versions: PDB 6.6.0 Assignee: Unassigned Created: 2019/10/03 6:16 AM Fix Versions: PDB 6.5.0 Priority: Major Reporter: Christoph Roeder Puppet Version: 6.7.0 Puppet Server Version: 6.7.0 OS Name/Version: Ubuntu 18.04 puppetdb 6.6.0 and upwards creates an dns alt cert even if no env variable DNS_ALT_NAMES is set. Desired Behavior: create an cert for puppetdb Actual Behavior: created an cert for puppetdb with alt name "puppetdb," puppetdb_1 | Running /docker-entrypoint.d/30-configure-ssl.sh puppetdb_1 | (/ssl.sh) Using configuration values: puppetdb_1 | (/ssl.sh) * CERTNAME: 'puppetdb' (/CN=puppetdb) puppetdb_1 | (/ssl.sh) * DNS_ALT_NAMES: 'puppetdb,' puppetdb_1 | (/ssl.sh) * CA: 'https://puppet:8140/puppet-ca/v1' puppetdb_1 | (/ssl.sh) * SSLDIR: '/opt/puppetlabs/server/data/puppetdb/certs' puppetdb_1 | (/ssl.sh) * WAITFORCERT: '120' seconds puppetdb_1 | subject=CN = Puppet CA: puppet.home.roeder.io puppetdb_1 | issuer=CN = Puppet CA: puppet.home.roeder.io puppetdb_1 | (/ssl.sh) Error: CA already has signed certificate for 'puppetdb'
Jira (PUP-9249) Backport sensitive DSL method PUP-8514
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9249 Backport sensitive DSL method PUP-8514 Change By: Jorie Tappa Fix Version/s: PUP 6.4.4 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.281329.1539907632000.127882.1570122000277%40Atlassian.JIRA.
Jira (PUP-10013) Update minitar version and call new fsync=false option
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-10013 Update minitar version and call new fsync=false option Change By: Jorie Tappa Release Notes Summary: On platforms that use minitar, extraction when installing modules would take a long time due to minitar's fsync'ing every directory and file. The way Puppet extracts and copies modules during install makes this task unnecessary. As of minitar 0.9, there's an option to turn this off. Puppet now uses minitar 0.9, improving install time on larger modules. Release Notes: Enhancement 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323877.1567788493000.127879.1570121940337%40Atlassian.JIRA.
Jira (PUP-9295) Notify resource exposes Sensitive data when message is a Sensitive data
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9295 Notify resource exposes Sensitive data when message is a Sensitive data Change By: Josh Cooper Release Notes Summary: Redact sensitive values when interpolated in a notify resource's message. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.283215.1540998541000.127896.1570122240488%40Atlassian.JIRA.
Jira (PUP-8986) pip provider fails if "pip --version" does not emit the version on the first line of output
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8986 pip provider fails if "pip --version" does not emit the version on the first line of output Change By: Josh Cooper Summary: Puppet agent crashes because of bug in pip provider fails if "pip --version" does not emit the version on the first line of output 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.263957.1530879286000.127899.1570122300267%40Atlassian.JIRA.
Jira (PUP-8986) pip provider fails if "pip --version" does not emit the version on the first line of output
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8986 pip provider fails if "pip --version" does not emit the version on the first line of output Change By: Josh Cooper Release Notes Summary: Improve how puppet detects the current pip version so that catalog application does not fail when managing pip package resources. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.263957.1530879286000.127909.1570122480661%40Atlassian.JIRA.
Jira (PUP-10058) Allow static catalogs to inline metadata for deeper modulepaths
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10058 Allow static catalogs to inline metadata for deeper modulepaths Change By: Josh Cooper Team: Coremunity 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.290273.1546538287000.127926.1570122600520%40Atlassian.JIRA.
Jira (PUP-9647) Pip package provider does not handle pip executable paths with spaces
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9647 Pip package provider does not handle pip executable paths with spaces Change By: Josh Cooper Release Notes Summary: Puppet could not manage pip resources if the pip command was in a directory containing spaces, like C:\Program Files\Python27 on Windows. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305257.133562000.127919.1570122540412%40Atlassian.JIRA.
Jira (PUP-10058) Allow static catalogs to inline metadata for deeper modulepaths
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10058 Allow static catalogs to inline metadata for deeper modulepaths Change By: Josh Cooper Sprint: Coremunity 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.290273.1546538287000.127930.1570122660201%40Atlassian.JIRA.
Jira (PUP-10080) Exec resources fail if the working directory is inaccessible
Title: Message Title Josh Cooper commented on PUP-10080 Re: Exec resources fail if the working directory is inaccessible Thanks John Bollinger. Could you run the first example with --trace? It may be related to PUP-9997 The second case is failing due to facter. Could you file a FACT ticket for that? [root@rbbd3d3x1dbupp3 test]# facter --debug shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory 2019-10-03 17:16:34.811353 INFO puppetlabs.facter - executed with command line: --debug. 2019-10-03 17:16:34.812893 INFO leatherman.ruby:139 - ruby loaded from "/opt/puppetlabs/puppet/lib/libruby.so.2.5.3". 2019-10-03 17:16:34.813368 DEBUG leatherman.dynamic_library:77 - symbol rb_data_object_alloc not found in library /opt/puppetlabs/puppet/lib/libruby.so.2.5.3, trying alias rb_data_object_wrap. 2019-10-03 17:16:34.893465 INFO leatherman.ruby:195 - using ruby version 2.5.3 2019-10-03 17:16:34.893562 INFO puppetlabs.facter - resolving all facts. 2019-10-03 17:16:34.893661 DEBUG puppetlabs.facter - fact "facterversion" has resolved to "3.14.3". 2019-10-03 17:16:34.893774 DEBUG puppetlabs.facter - fact "aio_agent_version" has resolved to "6.8.1". 2019-10-03 17:16:34.894163 DEBUG leatherman.file_util:65 - Error reading file: No such file or directory
Jira (PUP-10059) Puppet won't install (some) packages with ensure => held
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10059 Puppet won't install (some) packages with ensure => held Change By: Josh Cooper Team: Night's Watch 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.327639.157002023.128007.1570123500289%40Atlassian.JIRA.
Jira (PUP-10053) Update webmock and vcr
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10053 Update webmock and vcr Change By: Josh Cooper Release Notes: 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.326852.1569539131000.127610.1570117560076%40Atlassian.JIRA.
