Jira (PUP-9588) Unable to apply catalog successfully on nodes due to running iexplore process
Title: Message Title Tanmeet Kaur commented on PUP-9588 Re: Unable to apply catalog successfully on nodes due to running iexplore process I have stored the winlogbeat and filebeat executable in http://XX.XX.XX.XX:8081 nexus server from where it will download the file. So puppet should not try to access anything from Internet Explorer, I don't know why it is trying to perform the "Stop-Process operation" on "iexplore" 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-9588) Unable to apply catalog successfully on nodes due to running iexplore process
Title: Message Title
Tanmeet Kaur commented on PUP-9588
Re: Unable to apply catalog successfully on nodes due to running iexplore process
This is the **Beats.pp __ manifest which includes installation of both Winlogbeat and Filebeat package. class beats{ $filebeat_source = 'http://XX.XX.XX.XX:8081/nexus/content/repositories/filebeat/1.0/filebeat-1.0.zip'$winlogbeat_source = 'http://XX.XX.XX.XX:8081/nexus/content/repositories/winlogbeat/1.0/winlogbeat-1.0.zip' $filebeat_path = 'C:\\Filebeatinstall-service-filebeat.ps1' {{}} file{'C:\\tempfilebeat': {{}} {{ ensure => 'directory',}->}} file{'C:\\tempwinlogbeat': {{ ensure => 'directory',}->}} {{}} {{}} download_file{ 'filebeat.zip': {{ url ="" $filebeat_source,}} {{ destination_directory => 'C:\\temp\\filebeat',}->}} download_file{ 'winlogbeat.zip': {{ url ="" $winlogbeat_source,}} {{ destination_directory => 'C:\\temp\\winlogbeat',}->}} {{}} unzip{'filebeat.zip': {{ source => 'C:\\temp\\filebeatfilebeat-1.0.zip',}} {{ creates => "C:Filebeat",}->}} unzip{'winlogbeat.zip': {{ source => 'C:\\temp\\winlogbeatwinlogbeat-1.0.zip',}} {{ creates => "C:Winlogbeat",}->}} {{}} {{}} {{notify {"Installing winlogbeat...": withpath => true,} ->}} {{}} {{}} exec{'install-service-filebeat.ps1': {{ path => 'C:/Filebeat',}} {{ command => 'C:/Windows/System32/WindowsPowerShell/v1.0/powershell.exe -Executionpolicy Unrestricted -File C:/Filebeat/install-service-filebeat.ps1',}} {{ provider => powershell,}} {{ unless => 'C:/Windows/System32/WindowsPowerShell/v1.0/powershell.exe "if (((Get-Service | format-table property name) | out-string).contains(\'filebeat\')) {exit 0} else {exit 1}"',}>}} {{}} {{}} {{}} {{notify {"Starting filebeat...": withpath => true,} ->}} {{}} {{}} {{}} service{'filebeat': {{ ensure => running,}->}} {{}} exec{'install-service-winlogbeat.ps1': path => 'C:/Winlogbeat', {{ command => 'C:/Windows/System32/WindowsPowerShell/v1.0/powershell.exe -Executionpolicy Unrestricted -File C:/Winlogbeat/install-service-winlogbeat.ps1',}} {{ provider => powershell,}} {{ unless => 'C:/Windows/System32/WindowsPowerShell/v1.0/powershell.exe "if (((Get-Service | format-table property name) | out-string).contains(\'winlogbeat\')) {exit 0} else {exit 1}"',}>}} {{}} {{}} service{'winlogbeat': ensure => running,}}{{}} {{}}
Add Comment
Jira (PUP-7326) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts
Title: Message Title Halim Wijaya updated an issue Puppet / PUP-7326 Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts Change By: Halim Wijaya Attachment: Screen Shot 2019-04-03 at 11.45.12 AM.png 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-7326) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts
Title: Message Title Halim Wijaya commented on PUP-7326 Re: Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts This issue re-occurs in Windows 2016 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-7326) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts
Title: Message Title Halim Wijaya updated an issue Puppet / PUP-7326 Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts Change By: Halim Wijaya Attachment: Screen Shot 2019-04-03 at 11.44.28 AM.png 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-8900) "puppet facts upload" face only tries first master in server_list
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8900 "puppet facts upload" face only tries first master in server_list 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 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-9346) Remove hostcsr setting
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-9346
Remove hostcsr setting
Change By:
Josh Cooper
The {{hostcsr}} setting seems valid as it's similar to {{hostcert}}, {{hostcrl}}, but the setting is actually dead. Instead hosts generate CSRs and store them in the as " {{requestdir}}/{{certname}}.pem directory " .This ticket is to either make {{hostcsr}} resolve to the correct thing or remove . Since it's changing the default value of a setting , it needs to happen in 7 . 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-9346) Change default value of hostcsr setting
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9346 Change default value of hostcsr setting Change By: Josh Cooper Summary: Remove Change default value of hostcsr setting 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-9565) Not possible to set Mutliple Logging Destination with puppet agent anymore
Title: Message Title Rob Braden updated an issue Puppet / PUP-9565 Not possible to set Mutliple Logging Destination with puppet agent anymore Change By: Rob Braden Sprint: Coremunity Hopper Platform Core 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-9577) Large numbers of facts cause slow performance
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-9577 Large numbers of facts cause slow performance Change By: Jarret Lavallee CS Priority: Needs Priority 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-9600) Agent error message due to an "equals" sign in parameters.pp
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9600 Agent error message due to an "equals" sign in parameters.pp Change By: Josh Cooper Sub-team: Language 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-9600) Agent error message due to an "equals" sign in parameters.pp
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9600 Agent error message due to an "equals" sign in parameters.pp Change By: Josh Cooper 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-9600) Agent error message due to an "equals" sign in parameters.pp
Title: Message Title Josh Cooper moved an issue Puppet / PUP-9600 Agent error message due to an "equals" sign in parameters.pp Change By: Josh Cooper Key: PA PUP - 2579 9600 Project: Puppet Agent 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-9588) Unable to apply catalog successfully on nodes due to running iexplore process
Title: Message Title Josh Cooper commented on PUP-9588 Re: Unable to apply catalog successfully on nodes due to running iexplore process This is most likely an issue with the filebeat package. Are you passing the necessary install_options to ensure the package is installed silently? 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-9588) Unable to apply catalog successfully on nodes due to running iexplore process
Title: Message Title Josh Cooper assigned an issue to Tanmeet Kaur Puppet / PUP-9588 Unable to apply catalog successfully on nodes due to running iexplore process Change By: Josh Cooper Assignee: Tanmeet Kaur 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-8200) No docs to run Puppet 4, 5, or 6 from source
Title: Message Title Garrett Guillotte updated an issue Puppet / PUP-8200 No docs to run Puppet 4, 5, or 6 from source Change By: Garrett Guillotte Summary: No docs to run Puppet 4 or , 5 , or 6 from source 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-8200) No docs to run Puppet 4, 5, or 6 from source
Title: Message Title Garrett Guillotte updated an issue Puppet / PUP-8200 No docs to run Puppet 4, 5, or 6 from source Change By: Garrett Guillotte Acceptance Criteria: Either official documentation for running Puppet 4 or 5 or 6 from source exists, or links to the outdated docs are removed from the Puppet repository. 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-8200) No docs to run Puppet 4, 5, or 6 from source
Title: Message Title Garrett Guillotte commented on PUP-8200 Re: No docs to run Puppet 4, 5, or 6 from source Bumping since this is still true for Puppet 6. 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-1223) Inconsistencies in Result outputs vs access methods
Title: Message Title Henrik Lindberg commented on BOLT-1223 Re: Inconsistencies in Result outputs vs access methods I understand the frustration that the intended "human readable output" and the technical implementation are different - I was just explaining what I think happens when trying to get the "type" field. If there was an actual type() method for instance of that data type it would have been called instead of the general function with the same name. I supposed it is called something else internally, but is presented as "type". Looking at the output for $result where you see its attributes - you see there is a "value" attribute which you can get to with $result.value() and that is a hash. I don't know what is in it... but maybe that helps you for now until one of the Bolt folks respond. 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-1225) Link to packaged plans and tasks from running * pages
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-1225 Link to packaged plans and tasks from running * pages Issue Type: Task Assignee: Unassigned Created: 2019/04/02 1:41 PM Priority: Normal Reporter: Lucy Wyman Discovering bundled content isn't clear in our docs, and if a user doesn't run bolt [plan|task] show after installing they may never find that content. We should add a link and small blurb to https://puppet.com/docs/bolt/latest/bolt_running_plans.html and https://puppet.com/docs/bolt/latest/bolt_running_tasks.html, and maybe https://puppet.com/docs/bolt/latest/inspecting_tasks_and_plans.html linking to https://puppet.com/docs/bolt/latest/bolt_installing_modules.html#packaged-modules and indicating that there is bundled content. Add Comment
Jira (PUP-9589) waitforcert not working in 6.4
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9589 waitforcert not working in 6.4 Change By: Josh Cooper Fix Version/s: PUP 6.4.0 Fix Version/s: PUP 6.4.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-9599) Communicate scope and timeline of next release (Puppet Platform 5.5.13)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9599 Communicate scope and timeline of next release (Puppet Platform 5.5.13) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/02 10:55 AM Due Date: 2019/04/17 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-04-16) 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-9597) Send release announcement (Puppet Platform 5.5.13)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9597 Send release announcement (Puppet Platform 5.5.13) Issue Type: Task Assignee: Eric Griswold Created: 2019/04/02 10:55 AM Due Date: 2019/04/16 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-04-16) 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 5.5.13 is now available".
Jira (PUP-9598) Update Confluence and JIRA based on release (Puppet Platform 5.5.13)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9598 Update Confluence and JIRA based on release (Puppet Platform 5.5.13) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/02 10:55 AM Due Date: 2019/04/17 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-04-16) 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 the
Jira (PUP-9595) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.13)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9595 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.13) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/02 10:54 AM Due Date: 2019/04/15 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-04-16) 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 ‘Platform Core’ HipChat room for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9594) Prepare release announcement (Puppet Platform 5.5.13)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9594 Prepare release announcement (Puppet Platform 5.5.13) Issue Type: Task Assignee: Bill Tang Created: 2019/04/02 10:54 AM Due Date: 2019/04/15 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-04-16) 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-9596) Publish documentation and updates and release notes (Puppet Platform 5.5.13)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9596 Publish documentation and updates and release notes (Puppet Platform 5.5.13) Issue Type: Task Assignee: Jean Bond Created: 2019/04/02 10:54 AM Due Date: 2019/04/16 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-04-16) Merge the PR linked by Jean Bond. This kicks off a build to publish the docs, which takes some time. Add Comment
Jira (PUP-9592) Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.13)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9592 Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.13) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/02 10:54 AM Due Date: 2019/04/10 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-04-16) 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 HipChat) 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-9593) Prepare documentation updates and release notes (Puppet Platform 5.5.13)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9593 Prepare documentation updates and release notes (Puppet Platform 5.5.13) Issue Type: Task Assignee: Jean Bond Created: 2019/04/02 10:54 AM Due Date: 2019/04/12 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-04-16) 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 (PUP-9591) Prepare JIRA and Confluence for release (Puppet Platform 5.5.13)
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9591 Prepare JIRA and Confluence for release (Puppet Platform 5.5.13) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/02 10:53 AM Due Date: 2019/04/10 Labels: release Priority: Normal Reporter: Kenn Hussey (Initial planned release date: 2019-04-16) 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 5.5.13 and puppet-agent 5.5.13 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-9590) Puppet Platform 5.5.13 Release - 2019-04-16
Title: Message Title Kenn Hussey created an issue Puppet / PUP-9590 Puppet Platform 5.5.13 Release - 2019-04-16 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/04/02 10:53 AM Due Date: 2019/04/16 Priority: Normal Reporter: Kenn Hussey Puppet Platform 5.5.13 Release - 2019-04-16 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4326) PuppetDB rejects catalogs with tags added automatically by Puppet
Title: Message Title Austin Blatt commented on PDB-4326 Re: PuppetDB rejects catalogs with tags added automatically by Puppet Thanks Olav Morken for the detailed bug report, it helped a lot in tracking down the problem quickly. I've got a PR up to fix this [here|https://github.com/puppetlabs/puppetdb/pull/2882]. 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-4326) PuppetDB rejects catalogs with tags added automatically by Puppet
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4326 PuppetDB rejects catalogs with tags added automatically by Puppet 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 (PDB-4329) Change pe-client-tools-vanagon to build puppetdb-cli as a ruby project
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4329 Change pe-client-tools-vanagon to build puppetdb-cli as a ruby project Change By: Austin Blatt Change the component configs of pe-client-tools-vanagon to build puppetdb-cli as a ruby project.[https://github.com/puppetlabs/pe-client-tools-vanagon/tree/ master irving /configs/components |https://github.com/puppetlabs/puppet-client-tools-vanagon/tree/master/configs/components ] 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-4329) Change pe-client-tools-vanagon to build puppetdb-cli as a ruby project
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4329 Change pe-client-tools-vanagon to build puppetdb-cli as a ruby project Issue Type: New Feature Assignee: Unassigned Created: 2019/04/02 10:10 AM Priority: Normal Reporter: Austin Blatt Change the component configs of pe-client-tools-vanagon to build puppetdb-cli as a ruby project. https://github.com/puppetlabs/pe-client-tools-vanagon/tree/master/configs/components Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8213) Error message for certificate name mismatch is clear as mud
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8213 Error message for certificate name mismatch is clear as mud Change By: Josh Cooper Fix Version/s: PUP 6.0.8 Fix Version/s: PUP 5.5.13 Fix Version/s: PUP 6.0.z Fix Version/s: PUP 5.5.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
Jira (PDB-4328) Change puppet-client-tools-vanagon to build puppetdb-cli as a ruby project
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4328 Change puppet-client-tools-vanagon to build puppetdb-cli as a ruby project Issue Type: New Feature Assignee: Austin Blatt Created: 2019/04/02 10:08 AM Priority: Normal Reporter: Austin Blatt Change the component configs of puppet-client-tools-vanagon to build puppetdb-cli as a ruby project. https://github.com/puppetlabs/puppet-client-tools-vanagon/tree/master/configs/components Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4327) Migrate puppetdb-cli from Rust to Ruby
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4327 Migrate puppetdb-cli from Rust to Ruby Issue Type: New Feature Assignee: Austin Blatt Created: 2019/04/02 10:06 AM Priority: Normal Reporter: Austin Blatt Releasing another version of the Rust puppetdb-cli would require significant maintenance to puppetdb-cli and rust-kitchensink and maybe even other rust libraries we implemented. Instead we will migrate the puppetdb-cli to Ruby. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1223) Inconsistencies in Result outputs vs access methods
Title: Message Title Chris Barker commented on BOLT-1223 Re: Inconsistencies in Result outputs vs access methods Henrik Lindberg However given the above output from the notice($result) - how would I access the equivalent of: "type": "command" And see the output of "command" in an easy fashion? This is going back to the point that it is ridiculously complicated to just be able to get the type of the function/action that created that result. 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-9470) Add note to logs about which value we're getting the server from
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9470 Add note to logs about which value we're getting the server from Change By: Melissa Stone Release Notes Summary: Added information to the debug output specifying where the server setting originates, if it's coming from the `server` or `server_list` setting in their configuration 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 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-1223) Inconsistencies in Result outputs vs access methods
Title: Message Title Henrik Lindberg commented on BOLT-1223 Re: Inconsistencies in Result outputs vs access methods Not a bug - you end up calling the type() function which correctly is telling you what the type of the value is (by giving you the description of the type; arguably it could just display the name of the data type instead of the full definition, and you may consider it to be a bug that it outputs the full definition). 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-1209) Intermittent AppVeyor test failure - WSMAN ERROR CODE: 1018 / WSMAN ERROR CODE: 2147746132
Title: Message Title
Ethan Brown updated an issue
Puppet Task Runner / BOLT-1209
Intermittent AppVeyor test failure - WSMAN ERROR CODE: 1018 / WSMAN ERROR CODE: 2147746132
Change By:
Ethan Brown
The following code can be used to help decipher the error codes https://p0w3rsh3ll.wordpress.com/2013/03/07/deciphering-winrm-error-codes/.Error code 1018 is defined in https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes--1000-1299- as { noformat}ERROR_KEY_DELETED1018 (0x3FA)Illegal operation attempted on a registry key that has been marked for deletion. { noformat} 2147746132 could be the COM error for {{REGDB_E_CLASSNOTREG}}{noformat}C:\Users\Iristyle> (New-Object -ComObject WSMAN.Automation).GetErrorMessage((Get-ErrorCode 2147746132).Int64)Class not registered{noformat}Both of these seem to indicate some registry setup may not be complete.{{ bundle exec rake integration:appveyor_agents}} fails intermittently with a few different types of winrm errors{noformat}Failures: 1) apply over winrm on Appveyor with Puppet Agents when running against puppet 5 runs a ruby task Failure/Error: expect(result[0]).to include('status' => 'success') expected {"node" => "winrm://roddypiper@localhost:5985", "result" => {"_error" => {"details" => {}, "issue_code" => "CON... host server and proxy are properly registered. "}}, "status" => "failure"} to include {"status" => "success"} Diff: @@ -1,2 +1,4 @@ -"status" => "success", +"node" => "winrm://roddypiper@localhost:5985", +"result" => {"_error"=>{"details"=>{}, "issue_code"=>"CONNECT_ERROR", "kind"=>"puppetlabs.tasks/connect-error", "msg"=>"Failed to connect to http://localhost:5985/wsman: [WSMAN ERROR CODE: 1018]: The WSMan service could not launch a host process to process the given request. Make sure the WSMan provider host server and proxy are properly registered. "}}, +"status" => "failure", # ./spec/integration/apply_spec.rb:277:in `block (4 levels) in ' 2) apply over winrm on Appveyor with Puppet Agents when running against puppet 5 runs an apply plan Failure/Error: expect(result[0]).to include('status' => 'success') expected {"node" => "winrm://roddypiper@localhost:5985", "result" => {"_error" => {"details" => {}, "issue_code" => "CON... host server and proxy are properly registered. "}}, "status" => "failure"} to include {"status" => "success"} Diff: @@ -1,2 +1,4 @@ -"status" => "success", +"node" => "winrm://roddypiper@localhost:5985", +"result" => {"_error"=>{"details"=>{}, "issue_code"=>"CONNECT_ERROR", "kind"=>"puppetlabs.tasks/connect-error", "msg"=>"Failed to connect to http://localhost:5985/wsman: [WSMAN ERROR CODE: 1018]: The WSMan service could not launch a host process to process the given request. Make sure the WSMan provider host server and proxy are properly registered. "}}, +"status" => "failure", # ./spec/integration/apply_spec.rb:277:in `block (4 levels) in ' 3) apply over winrm on Appveyor with Puppet Agents when
Jira (PUP-9470) Add note to logs about which value we're getting the server from
Title: Message Title Josh Cooper commented on PUP-9470 Re: Add note to logs about which value we're getting the server from Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/c8eb1774c568d84ffbcb0983c745030ce25b9cb6 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-9565) Not possible to set Mutliple Logging Destination with puppet agent anymore
Title: Message Title Jacob Helwig updated an issue Puppet / PUP-9565 Not possible to set Mutliple Logging Destination with puppet agent anymore Change By: Jacob Helwig Fix Version/s: PUP 5.5.13 Fix Version/s: PUP 5.5.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-1196) bolt-inventory-pdb examples in public documentation are incorrect
Title: Message Title Nick Lewis updated an issue Puppet Task Runner / BOLT-1196 bolt-inventory-pdb examples in public documentation are incorrect Change By: Nick Lewis Component/s: DOCS 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-1196) bolt-inventory-pdb examples in public documentation are incorrect
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1196 bolt-inventory-pdb examples in public documentation are incorrect Change By: David Kramer 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-1209) Intermittent AppVeyor test failure - WSMAN ERROR CODE: 1018 / WSMAN ERROR CODE: 2147746132
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1209 Intermittent AppVeyor test failure - WSMAN ERROR CODE: 1018 / WSMAN ERROR CODE: 2147746132 Change By: David Kramer 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-1133) Add bolt community slack to README, Contributing, and docs
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1133 Add bolt community slack to README, Contributing, and docs Change By: David Kramer 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-1117) Powershell task helper library
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1117 Powershell task helper library Change By: David Kramer 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-1195) Generate a PP plan from a simple plan
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1195 Generate a PP plan from a simple plan Change By: David Kramer Sprint: Bolt 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-1194) Validate simple plans
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1194 Validate simple plans Change By: David Kramer Sprint: Bolt 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-1224) SPIKE - Investigate lighter weight code for sending analytics on Windows
Title: Message Title Ethan Brown created an issue Puppet Task Runner / BOLT-1224 SPIKE - Investigate lighter weight code for sending analytics on Windows Issue Type: Improvement Affects Versions: BOLT 1.15.0 Assignee: Unassigned Components: Windows Created: 2019/04/02 9:25 AM Priority: Normal Reporter: Ethan Brown Currently the analytics code loads both the concurrent and httpclient gems on Windows. These are fairly slow to load. For CLI consumers that haven't disabled analytics, this can slow down some of the basic bolt CLI interactions. Add Comment
Jira (BOLT-1026) Bolt package should include hiera-eyaml
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1026 Bolt package should include hiera-eyaml Change By: Alex Dreyer s/t This gem should be included in bolt-vanagon 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-1208) SPIKE - Determine next area for Windows perf improvements
Title: Message Title
Ethan Brown updated an issue
Puppet Task Runner / BOLT-1208
SPIKE - Determine next area for Windows perf improvements
Change By:
Ethan Brown
Now that BOLT-1119 and BOLT-1186 are completed in an effort to improve startup time performance on , further investigate areas for performance improvements on Windows* Loading the list of available tasks / plans from modules on disk (i.e. {{bolt plan show}} and similar)* Connecting to remote hosts once to run a command / script / task* Connecting to the same host multiple times to run a command / script / taskIt may be useful to get other scenarios that feel "slow" to Windows users. Another useful output of this ticket might be a dependency graph showing how files / classes / gems are related to one another.
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
Jira (PUP-9565) Not possible to set Mutliple Logging Destination with puppet agent anymore
Title: Message Title Jacob Helwig assigned an issue to Jacob Helwig Puppet / PUP-9565 Not possible to set Mutliple Logging Destination with puppet agent anymore Change By: Jacob Helwig Assignee: Jacob Helwig 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-1223) Inconsistencies in Result outputs vs access methods
Title: Message Title Chris Barker commented on BOLT-1223 Re: Inconsistencies in Result outputs vs access methods Also since I'm unsure on how it should behave, I don't know if I should create a ticket - but getting the ruby object definition when trying to load the result Type seems to be a bug from what I can tell. 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-9497) Deprecate fine grained file and environment timeouts
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9497 Deprecate fine grained file and environment timeouts Change By: Melissa Stone Release Notes Summary: fine grained control of file and environment timeouts is deprecated Release Notes: Deprecation 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-9589) waitforcert not working in 6.4
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9589 waitforcert not working in 6.4 Change By: Josh Cooper Sprint: Platform Core 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-9589) waitforcert not working in 6.4
Title: Message Title Josh Cooper moved an issue Puppet / PUP-9589 waitforcert not working in 6.4 Change By: Josh Cooper Affects Version/s: puppet-agent 6.4.0 Affects Version/s: PUP 6.4.0 Key: PA PUP - 2580 9589 Project: Puppet Agent 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-9589) waitforcert not working in 6.4
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9589 waitforcert not working in 6.4 Change By: Josh Cooper Fix Version/s: PUP 6.4.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-9589) waitforcert not working in 6.4
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9589 waitforcert not working in 6.4 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 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-1223) Inconsistencies in Result outputs vs access methods
Title: Message Title Chris Barker commented on BOLT-1223 Re: Inconsistencies in Result outputs vs access methods Realize this is a duplicate of BOLT-833 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-4326) PuppetDB rejects catalogs with tags added automatically by Puppet
Title: Message Title
Olav Morken updated an issue
PuppetDB / PDB-4326
PuppetDB rejects catalogs with tags added automatically by Puppet
Change By:
Olav Morken
Puppet automatically tags resources with the resource title, if it considers the title to be a valid tag name:[https://github.com/puppetlabs/puppet/blob/6.4.0/lib/puppet/resource.rb#L325|https://github.com/puppetlabs/puppet/blob/6.4.0/lib/puppet/resource.rb#L325']To determine if it is a valid tag name, it uses the following regex:{{ ValidTagRegex = /\A[[:alnum:]_][[:alnum:]_:.-]*\Z/u}}([https://github.com/puppetlabs/puppet/blob/6.4.0/lib/puppet/util/tagging.rb#L4)]Since PUP-7579, this regex allows unicode characters. The result is that when you have a resource with a non-ascii characters in its title, it will still add a tag with that title. This can be triggered by for example:{{ notify \{ 'norwegian_characters_æøå': \ } }}This is legal according to the documentation:{quote}Resource titles can contain any characters whatsoever. They are case-sensitive.{quote}([https://puppet.com/docs/puppet/6.4/lang_reserved.html#resources)]The problem is that PuppetDB has not been updated to allow unicode characters in tags. Thus there is a mismatch between what the Puppet server considers to be a valid tag name and what PuppetDB considers to be a valid tag name.This in turn causes PuppetDB to fail to store the catalog for the node. The Puppet server does not log anything except the normal "Puppet 'replace_catalog' command for submitted to PuppetDB with UUID <...>", however, looking at the logs in PuppetDB, we find:{quote}2019-04-02T14:40:14.185+02:00 ERROR [p.p.command] [81,969] [replace catalog] Fatal error on attempt 0 for vltrd077.cn.uninett.noclojure.lang.ExceptionInfo: throw+: {:fatal true, :cause #error { :cause "Resource ' \ {:type \"Notify\", :title \"norwegian_characters_???\"}' has an invalid tag 'norwegian_characters_???'. Tags must match the pattern /\\A[a-z0-9_][a-z0-9_:\\-.]* \\ Z/."{quote}(I have attached the full stack trace as puppetdb.log.)Since PuppetDB does not store the new catalog for the node, we cannot query PuppetDB for resources from that node.
Add Comment
Jira (PDB-4326) PuppetDB rejects catalogs with tags added automatically by Puppet
Title: Message Title
Olav Morken updated an issue
PuppetDB / PDB-4326
PuppetDB rejects catalogs with tags added automatically by Puppet
Change By:
Olav Morken
Puppet automatically tags resources with the resource title, if it considers the title to be a valid tag name:[https://github.com/puppetlabs/puppet/blob/6.4.0/lib/puppet/resource.rb#L325|https://github.com/puppetlabs/puppet/blob/6.4.0/lib/puppet/resource.rb#L325']To determine if it is a valid tag name, it uses the following regex:{{ ValidTagRegex = /\A[[:alnum:]_][[:alnum:]_:.-]*\Z/u}}([https://github.com/puppetlabs/puppet/blob/6.4.0/lib/puppet/util/tagging.rb#L4)]Since PUP-7579, this regex allows unicode characters. The result is that when you have a resource with a non-ascii characters in its title, it will still add a tag with that title. This can be triggered by for example:{{ notify \{ 'norwegian_characters_æøå': \ } }}This is legal according to the documentation:{quote}Resource titles can contain any characters whatsoever. They are case-sensitive.{quote}([https://puppet.com/docs/puppet/6.4/lang_reserved.html#resources)]The problem is that PuppetDB has not been updated to allow unicode characters in tags. Thus there is a mismatch between what the Puppet server considers to be a valid tag name and what PuppetDB considers to be a valid tag name.This in turn causes PuppetDB to fail to store the catalog for the node. The Puppet server does not log anything except the normal "Puppet 'replace_catalog' command for submitted to PuppetDB with UUID <...>", however, looking at the logs in PuppetDB, we find:{quote}2019-04-02T14:40:14.185+02:00 ERROR [p.p.command] [81,969] [replace catalog] Fatal error on attempt 0 for vltrd077.cn.uninett.noclojure.lang.ExceptionInfo: throw+: {:fatal true, :cause #error { :cause "Resource '\{:type \"Notify\", :title \"norwegian_characters_???\"}' has an invalid tag 'norwegian_characters_???'. Tags must match the pattern /\\A[a-z0-9_][a-z0-9_:\\-.]*\\Z/."{quote}(I have attached the full stack trace as puppetdb.log.)Since PuppetDB does not store the new catalog for the node, we cannot query PuppetDB for resources from that node.
Add Comment
Jira (PDB-4326) PuppetDB rejects catalogs with tags added automatically by Puppet
Title: Message Title
Olav Morken updated an issue
PuppetDB / PDB-4326
PuppetDB rejects catalogs with tags added automatically by Puppet
Change By:
Olav Morken
Puppet automatically tags resources with the resource title, if it considers the title to be a valid tag name:[https://github.com/puppetlabs/puppet/blob/6.4.0/lib/puppet/resource.rb#L325|https://github.com/puppetlabs/puppet/blob/6.4.0/lib/puppet/resource.rb#L325']To determine if it is a valid tag name, it uses the following regex:{{ ValidTagRegex = /\A[[:alnum:]_][[:alnum:]_:.-]*\Z/u}}([https://github.com/puppetlabs/puppet/blob/6.4.0/lib/puppet/util/tagging.rb#L4)]Since PUP-7579, this regex allows unicode characters. The result is that when you have a resource with a non-ascii characters in its title, it will still add a tag with that title. This can be triggered by for example:{{ notify \{ 'norwegian_characters_æøå': }}}This is legal according to the documentation:{quote}Resource titles can contain any characters whatsoever. They are case-sensitive.{quote}([https://puppet.com/docs/puppet/6.4/lang_reserved.html#resources)]The problem is that PuppetDB has not been updated to allow unicode characters in tags. Thus there is a mismatch between what the Puppet server considers to be a valid tag name and what PuppetDB considers to be a valid tag name.This in turn causes PuppetDB to fail to store the catalog for the node. The Puppet server does not log anything except the normal "Puppet 'replace_catalog' command for submitted to PuppetDB with UUID <...>", however, looking at the logs in PuppetDB, we find:{quote}2019-04-02T14:40:14.185+02:00 ERROR [p.p.command] [81,969] [replace catalog] Fatal error on attempt 0 for vltrd077.cn.uninett.noclojure.lang.ExceptionInfo: throw+: {:fatal true, :cause #error { :cause "Resource '\{:type \"Notify\", :title \"norwegian_characters_???\"}' has an invalid tag 'norwegian_characters_???'. Tags must match the pattern /\\A[a-z0-9_][a-z0-9_:\\-.]*\\Z/."{quote}(I have attached the full stack trace as puppetdb.log.)Since PuppetDB does not store the new catalog for the node, we cannot query PuppetDB for resources from that node.
Add Comment
Jira (PDB-4326) PuppetDB rejects catalogs with tags added automatically by Puppet
Title: Message Title Olav Morken created an issue PuppetDB / PDB-4326 PuppetDB rejects catalogs with tags added automatically by Puppet Issue Type: Bug Affects Versions: PDB 6.3.0 Assignee: Unassigned Attachments: puppetdb.log Components: PuppetDB Created: 2019/04/02 5:53 AM Environment: PuppetDB 6.3.0 on Debian Stretch: 6.3.0-1stretch Puppet server 6.3.0 on Debian Stretch: 6.3.0-1stretch Puppet agent 6.4.0 on Debian Stretch: 6.4.0-1stretch Priority: Normal Reporter: Olav Morken Puppet automatically tags resources with the resource title, if it considers the title to be a valid tag name: https://github.com/puppetlabs/puppet/blob/6.4.0/lib/puppet/resource.rb#L325 To determine if it is a valid tag name, it uses the following regex: ValidTagRegex = /\A[[:alnum:]][[:alnum:]:.-]*\Z/u (https://github.com/puppetlabs/puppet/blob/6.4.0/lib/puppet/util/tagging.rb#L4) Since PUP-7579, this regex allows unicode characters. The result is that when you have a resource with a non-ascii characters in its title, it will still add a tag with that title. This can be triggered by
Jira (BOLT-1223) Inconsistencies in Result outputs vs access methods
Title: Message Title
Chris Barker updated an issue
Puppet Task Runner / BOLT-1223
Inconsistencies in Result outputs vs access methods
Change By:
Chris Barker
There are major inconsistencies in how views a Result output vs how one accesses it. For example, running this command{code}run_command('mkdir ~/boltexamples', $nodes).each | $result | {notice($result)}{code}Provides me with a json hash output that looks easy to navigate (after piping through | python -mjson.tool:{code:json}{"node": "puppet.c.splunk-217321.internal","object": "mkdir ~/boltexamples","result": {"exit_code": 0,"stderr": "","stdout": ""},"status": "success","type": "command"}{code}Now looking at this result, I would assume I could access the node name, object, result, and status just by referring to the hash keys, since that's what I'm looking at. Assuming I've not yet dove into the docs and I'm just reading existing code and want to poke around, I may go and do this:{code}run_command('mkdir ~/boltexamples', $nodes).each | $result | {notice($result['node'])}{code}Which is frustrating because the output I get is:{code}Starting: command 'mkdir ~/boltexamples' on puppet.c.splunk-217321.internalFinished: command 'mkdir ~/boltexamples' with 0 failures in 2.28 secFinished: plan firstproject::firstplan in 5.1 secPlan completed successfully with no result{code}So I guess that's an empty hash? How do I actually access these variables? Now I have to go to the documentation to see what is what - which explains that I can access those as functions, but function names have no correllation to what I was just looking at, in fact we hide the mapping in the code here:https://github.com/puppetlabs/bolt/blob/master/lib/bolt/result.rb#L93-L99Ah, now I see if I want the node name, I have to call $result.target.name - otherwise I just get the result of {code}Target('puppet.c.splunk-217321.internal', {"user"=>"cbarker"}){code}Bonus surprise: I'd think I could get away with `$result.type` to see what type of function this was, but instead, I get the ruby definition of the object: {code}Object[{name => 'Result', attributes => {'value' => Hash[String[1], Data], 'target' => Target}, functions => {'error' => Callable[[0, 0], Optional[Error]], 'message' => Callable[[0, 0], Optional[String]], 'ok' => Callable[[0, 0], Boolean], '[]' => Callable[[String[1]], Data]}}]{code}Making the onscreen output of Bolt be logically consistent with methods to call and extract that data will be essential for new users to learn how to access and work with it. If we're going to to have `notice($result)` output a hash, I should be able to access the subhash without having to read the docs. So far I have yet to be able to access the equivalent of `$result["object"]` or `$result["type"]` even though that would be the logical way I could access it while looking at the output of the code. I can't tell if it is just undocumented or a bug or a mixture of both. Edit: to clarify, I don't know how to get the contents of object
Jira (BOLT-1223) Inconsistencies in Result outputs vs access methods
Title: Message Title
Chris Barker created an issue
Puppet Task Runner / BOLT-1223
Inconsistencies in Result outputs vs access methods
Issue Type:
Bug
Affects Versions:
BOLT 1.15.0
Assignee:
Unassigned
Created:
2019/04/02 4:20 AM
Priority:
Normal
Reporter:
Chris Barker
There are major inconsistencies in how views a Result output vs how one accesses it. For example, running this command
run_command('mkdir ~/boltexamples', $nodes).each | $result | {
notice($result)
}
Provides me with a json hash output that looks easy to navigate (after piping through | python -mjson.tool:
{
Jira (PUP-9579) device application is broken in 6.4
Title: Message Title David Schmitt commented on PUP-9579 Re: device application is broken in 6.4 assigning this to me to sweep it up in the current puppet device cleanup 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-9579) device application is broken in 6.4
Title: Message Title David Schmitt assigned an issue to David Schmitt Puppet / PUP-9579 device application is broken in 6.4 Change By: David Schmitt Assignee: Josh Cooper David Schmitt 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-9584) Puppet Device plugin sync slow
Title: Message Title David Schmitt assigned an issue to David Schmitt Puppet / PUP-9584 Puppet Device plugin sync slow Change By: David Schmitt Assignee: David Schmitt 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-9588) Unable to apply catalog successfully on nodes due to running iexplore process
Title: Message Title Tanmeet Kaur updated an issue Puppet / PUP-9588 Unable to apply catalog successfully on nodes due to running iexplore process Change By: Tanmeet Kaur *Puppet Version:* _4.10.0_ *Puppet Server Version:* _7.1_ *OS Name/Version:* _RHEL 7.1_*Puppet Agent server*_*:* Windows 2012 R2_I am trying to run 6 puppet manifests on 50 Windows servers to install Citrix, ms-office, winbeat, filebeat, uipath, and configure some system registry keys, but every time I run "puppet agent -t" cmd on the nodes, after running configuration from a few of manifests, it is opening internet explorer and asking to kill iexplore processes (running as the background processes in task manager), even though I have not mentioned any such cmd/rule/line in manifests - *" _Notice: /Stage[main]/Beats/Notify[Starting filebeat...]/message: Starting_* filebeat*_..._* *_Notice: /Stage[main]/Beats/Notify[Starting filebeat...]/message: defined 'message' as 'Starting_* filebeat*_...'_* *_Confirm All [N] No Are you sure you want to perform the Stop-Process operation on the following item:_* iexplore*_(10192)? [Y] Yes [A] Yes to [L] No to All [S] Suspend [?] Help(default is "Y"): "_* and the catalog fails to apply successfully when it gets no response for the killing of iexplore proc. If iexplore is running in the 'Apps' tab in task manager (i.e. when I manually run iexplore in the foreground to test), while manifests are running, iexplore proc is killed by itself and then the catalog is applied successfully. If no iexplore proc is running, the catalog is applied successfully on nodes.Can someone please help explain to me what is the reason for this automatic iexplore proc termination while running puppet manifest on agents and how can we prevent his from happening cos in background iexplore will always run on my nodes?Describe your issue in as much detail as possible…Describe steps to reproduce…*Desired Behavior:*_"Applied Catalog successfully"_*Actual Behavior:* _Confirm All [N] No Are _Confirm__Are you sure you want to perform the Stop-Process operation on the following item following__item : _ iexplore_ iexplore (10192)? __ [Y] Yes [A] Yes to All [ N] No [ L] No to All [S] Suspend [?] Help Help__ (default is "Y"): " Error: Command exceeded timeout__Error: /Stage[main]/Office/Exec[act]/returns: change from notrun to 0 failed: Co__mmand exceeded timeout__Info: Stage[main]: Unscheduling all events on Stage[main] _ _Notice: Applied catalog in 315.64 seconds_
Jira (PUP-9588) Unable to apply catalog successfully on nodes due to running iexplore process
Title: Message Title Tanmeet Kaur created an issue Puppet / PUP-9588 Unable to apply catalog successfully on nodes due to running iexplore process Issue Type: Bug Affects Versions: PUP 4.10.z Assignee: Unassigned Components: Catalog Application, CLI Created: 2019/04/02 12:34 AM Priority: Major Reporter: Tanmeet Kaur Puppet Version: 4.10.0 Puppet Server Version: 7.1 OS Name/Version: RHEL 7.1 Puppet Agent server: Windows 2012 R2 I am trying to run 6 puppet manifests on 50 Windows servers to install Citrix, ms-office, winbeat, filebeat, uipath, and configure some system registry keys, but every time I run "puppet agent -t" cmd on the nodes, after running configuration from a few of manifests, it is opening internet explorer and asking to kill iexplore processes (running as the background processes in task manager), even though I have not mentioned any such cmd/rule/line in manifests - " Notice: /Stage[main]/Beats/Notify[Starting filebeat...]/message: Starting filebeat*...* Notice: /Stage[main]/Beats/Notify[Starting filebeat...]/message: defined 'message' as 'Starting filebeat*...'* Confirm All [N] No Are you sure you want to perform the Stop-Process operation on the following item: iexplore*(10192)? [Y] Yes [A] Yes to [L] No to All [S] Suspend [?] Help(default is "Y"): "* and the catalog fails to apply successfully when it gets no response for the killing of iexplore proc. If iexplore is running in the 'Apps' tab in task manager (i.e. when I manually run iexplore in the foreground to test), while manifests are running, iexplore proc is killed by itself and then the catalog is applied successfully. If no iexplore proc is running, the catalog is applied successfully on nodes. Can someone please help explain to me what is the reason for this automatic iexplore proc
