Jira (FACT-2886) networking.interfaces fact not appearing
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2886 networking.interfaces fact not appearing Change By: Bogdan Irimie Sprint: ghost-9.12 Sub-team: ghost Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379783.1606999223000.91371.1607068440038%40Atlassian.JIRA.
Jira (PUP-10792) How to set token for https url when using puppet file resource
Title: Message Title liuwenhe commented on PUP-10792 Re: How to set token for https url when using puppet file resource hi Josh Thanks for your reply, I tried to install puppet7-agent on the client,Then I run puppet agent -t --http_debug But the error still occurs, the following is a screenshot, the attachment is the error content (My puppet server is still 5.3.14) error.txt Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379148.1606203494000.91354.1607047740029%40Atlassian.JIRA.
Jira (PUP-10792) How to set token for https url when using puppet file resource
Title: Message Title liuwenhe updated an issue Puppet / PUP-10792 How to set token for https url when using puppet file resource Change By: liuwenhe Attachment: error.txt Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379148.1606203494000.91353.1607047680126%40Atlassian.JIRA.
Jira (PUP-10792) How to set token for https url when using puppet file resource
Title: Message Title liuwenhe updated an issue Puppet / PUP-10792 How to set token for https url when using puppet file resource Change By: liuwenhe Attachment: image-2020-12-04-10-06-11-639.png Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379148.1606203494000.91352.1607047620030%40Atlassian.JIRA.
Jira (PDB-4978) Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.0.1)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-4978 Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.0.1) Change By: Morgan Rhodes Epic Link: PUP-10801 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379914.1607039535000.91149.1607039580747%40Atlassian.JIRA.
Jira (PDB-4980) Bump versions, push directly, and tag (PuppetDB 7.0.1)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-4980 Bump versions, push directly, and tag (PuppetDB 7.0.1) Change By: Morgan Rhodes Epic Link: PUP-10801 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379916.1607039541000.91153.1607039580923%40Atlassian.JIRA.
Jira (PDB-4982) Update winston (PuppetDB 7.0.1)
Title: Message Title Morgan Rhodes created an issue PuppetDB / PDB-4982 Update winston (PuppetDB 7.0.1) Issue Type: Task Assignee: Zachary Kent Created: 2020/12/03 3:52 PM Due Date: 2020/12/16 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-12-15) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4979) Draft release notes (PuppetDB 7.0.1)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-4979 Draft release notes (PuppetDB 7.0.1) Change By: Morgan Rhodes Epic Link: PUP-10801 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379915.1607039538000.91151.1607039580835%40Atlassian.JIRA.
Jira (PDB-4978) Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.0.1)
Title: Message Title Morgan Rhodes created an issue PuppetDB / PDB-4978 Reconcile git commits, JIRA tickets, and versions (PuppetDB 7.0.1) Issue Type: Task Assignee: Zachary Kent Created: 2020/12/03 3:52 PM Due Date: 2020/12/08 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-12-15) Ensure all tickets referenced in the commit log have a the release's fixVersion, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by checking out the branches you will be releasing, ensuring they are in sync with the upstream puppetlabs repo and running the rake task bundle install; bundle exec rake release:reconcile[NEXT_VER,LAST_VER] This assumes you have the puppetdb repo as the cwd and the pe repo at ../pe-puppetdb-extensions. These can be overridden by the PDB_PATH and PDB_PE_PATH environment variables. The rake task will explain any mismatches that exist between Jira and the repos and ask you to investigate any tickets that do not start with a PDB ticket, (maint), (docs), or (i18n) Add Comment
Jira (PDB-4980) Bump versions, push directly, and tag (PuppetDB 7.0.1)
Title: Message Title Morgan Rhodes created an issue PuppetDB / PDB-4980 Bump versions, push directly, and tag (PuppetDB 7.0.1) Issue Type: Task Assignee: Zachary Kent Created: 2020/12/03 3:52 PM Due Date: 2020/12/11 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-12-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. Check that puppetdb and pe-puppetdb-extensions are on the same version of clj-parent, and that is the same clj-parent version that puppetserver will release with. Disable automatic promotions: If a PE release branch has not been cut, 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.
Jira (PDB-4981) Check builds, promote to PE (PuppetDB 7.0.1)
Title: Message Title Morgan Rhodes created an issue PuppetDB / PDB-4981 Check builds, promote to PE (PuppetDB 7.0.1) Issue Type: Task Assignee: Zachary Kent Created: 2020/12/03 3:52 PM Due Date: 2020/12/11 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-12-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. If a release branch has already been cut Rebuild the pacakge promotion job with the release branch set instead of master or 2018.1.x. Once it's promoted to the release branch checkout the release branch of enterprise-dist locally and verify that all platforms have the same tagged version of pe-puppetdb bundle exec rake report:packages If there were any important dependency bumps, such as to fix a bug or CVE, verify that they were updated by navigating to the release and then to the pe-puppetdb package on [pebuildinfo|pebuildinfo.slice.puppetlabs.net/].
Jira (PDB-4979) Draft release notes (PuppetDB 7.0.1)
Title: Message Title Morgan Rhodes created an issue PuppetDB / PDB-4979 Draft release notes (PuppetDB 7.0.1) Issue Type: Task Assignee: Zachary Kent Created: 2020/12/03 3:52 PM Due Date: 2020/12/13 Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-12-15) Write release notes for the release based on the tickets found in the previous step. Check any tickets for a docs tab with desired information. The release notes go in puppetdb\/documentation\/release_notes.markdown. Request review from the docs team by pinging @clairecadman in the opened PR, at least one day before Ready to Ship The opened PR should be approved prior to a go\/no-go. Release notes must be ready before a go. Docs are built daily and at release time. If notes need to be published out of band ask in `#prod-docs`.
Jira (PDB-4977) Merge-up, branch, and create pipelines (PuppetDB 7.0.1)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-4977 Merge-up, branch, and create pipelines (PuppetDB 7.0.1) Change By: Morgan Rhodes Epic Link: PUP-10801 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379913.1607039532000.91147.1607039580660%40Atlassian.JIRA.
Jira (PDB-4981) Check builds, promote to PE (PuppetDB 7.0.1)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-4981 Check builds, promote to PE (PuppetDB 7.0.1) Change By: Morgan Rhodes Epic Link: PUP-10801 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379917.1607039544000.91155.1607039581011%40Atlassian.JIRA.
Jira (PDB-4977) Merge-up, branch, and create pipelines (PuppetDB 7.0.1)
Title: Message Title
Morgan Rhodes created an issue
PuppetDB / PDB-4977
Merge-up, branch, and create pipelines (PuppetDB 7.0.1)
Issue Type:
Task
Assignee:
Zachary Kent
Created:
2020/12/03 3:52 PM
Due Date:
2020/12/08
Priority:
Normal
Reporter:
Morgan Rhodes
(Initial planned release date: 2020-12-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
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 -> master
Important: Do this for both the core puppetdb repo and the pe-puppetdb-extensions repo! These should be submitted as PRs and merged after tests pass, if there's anything remotely interesting about the merges. If the merges are boring, then direct push is fine. Then, prepare the branch for release:
Jira (PDB-4982) Update winston (PuppetDB 7.0.1)
Title: Message Title Morgan Rhodes updated an issue PuppetDB / PDB-4982 Update winston (PuppetDB 7.0.1) Change By: Morgan Rhodes Epic Link: PUP-10801 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379919.1607039551000.91157.1607039581099%40Atlassian.JIRA.
Jira (PUP-10809) Update Confluence and JIRA based on release (Puppet Platform 7.1.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10809 Update Confluence and JIRA based on release (Puppet Platform 7.1.0) Change By: Morgan Rhodes Epic Link: PUP-10801 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379894.1607039223000.91119.1607039280223%40Atlassian.JIRA.
Jira (PUP-10809) Update Confluence and JIRA based on release (Puppet Platform 7.1.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10809 Update Confluence and JIRA based on release (Puppet Platform 7.1.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/12/03 3:47 PM Due Date: 2020/12/16 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-12-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 the
Jira (PUP-10810) Communicate scope and timeline of next release (Puppet Platform 7.1.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10810 Communicate scope and timeline of next release (Puppet Platform 7.1.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/12/03 3:47 PM Due Date: 2020/12/16 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-12-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-10810) Communicate scope and timeline of next release (Puppet Platform 7.1.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10810 Communicate scope and timeline of next release (Puppet Platform 7.1.0) Change By: Morgan Rhodes Epic Link: PUP-10801 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379895.1607039226000.91121.1607039280311%40Atlassian.JIRA.
Jira (PUP-10808) Send release announcement (Puppet Platform 7.1.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10808 Send release announcement (Puppet Platform 7.1.0) Change By: Morgan Rhodes Epic Link: PUP-10801 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379893.1607039219000.91117.1607039280136%40Atlassian.JIRA.
Jira (PUP-10806) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.1.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10806 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.1.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/12/03 3:46 PM Due Date: 2020/12/14 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-12-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-10805) Prepare release announcement (Puppet Platform 7.1.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10805 Prepare release announcement (Puppet Platform 7.1.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/12/03 3:46 PM Due Date: 2020/12/14 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-12-15) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Claire Cadman 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-10803) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.1.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10803 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.1.0) Change By: Morgan Rhodes Epic Link: PUP-10801 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379886.1607039197000.91105.1607039220524%40Atlassian.JIRA.
Jira (PDB-4972) puppetdb-7.0.0 still requires java-1.8.0-openjdk-headless
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4972 puppetdb-7.0.0 still requires java-1.8.0-openjdk-headless Change By: Zachary Kent Fix Version/s: PDB 7.0.1 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379070.160597919.91112.1607039220719%40Atlassian.JIRA.
Jira (PUP-10804) Prepare documentation updates and release notes (Puppet Platform 7.1.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10804 Prepare documentation updates and release notes (Puppet Platform 7.1.0) Change By: Morgan Rhodes Epic Link: PUP-10801 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379887.160703920.91107.1607039220571%40Atlassian.JIRA.
Jira (PUP-10802) Prepare JIRA and Confluence for release (Puppet Platform 7.1.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10802 Prepare JIRA and Confluence for release (Puppet Platform 7.1.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/12/03 3:46 PM Due Date: 2020/12/09 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-12-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 7.1.0 and puppet-agent 7.1.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to
Jira (PUP-10806) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.1.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10806 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.1.0) Change By: Morgan Rhodes Epic Link: PUP-10801 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379890.1607039209000.9.1607039220676%40Atlassian.JIRA.
Jira (PUP-10807) Publish documentation and updates and release notes (Puppet Platform 7.1.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10807 Publish documentation and updates and release notes (Puppet Platform 7.1.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/12/03 3:46 PM Due Date: 2020/12/15 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-12-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-10802) Prepare JIRA and Confluence for release (Puppet Platform 7.1.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10802 Prepare JIRA and Confluence for release (Puppet Platform 7.1.0) Change By: Morgan Rhodes Epic Link: PUP-10801 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379885.1607039194000.91103.1607039220463%40Atlassian.JIRA.
Jira (PUP-10801) Puppet Platform 7.1.0 Release - 2020-12-15
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10801 Puppet Platform 7.1.0 Release - 2020-12-15 Issue Type: Epic Assignee: Nirupama Mantha Created: 2020/12/03 3:46 PM Due Date: 2020/12/15 Priority: Normal Reporter: Morgan Rhodes Puppet Platform 7.1.0 Release - 2020-12-15 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10804) Prepare documentation updates and release notes (Puppet Platform 7.1.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10804 Prepare documentation updates and release notes (Puppet Platform 7.1.0) Issue Type: Task Assignee: Claire Cadman Created: 2020/12/03 3:46 PM Due Date: 2020/12/11 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-12-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 (PUP-10805) Prepare release announcement (Puppet Platform 7.1.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10805 Prepare release announcement (Puppet Platform 7.1.0) Change By: Morgan Rhodes Epic Link: PUP-10801 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379888.1607039203000.91109.1607039220583%40Atlassian.JIRA.
Jira (PDB-4971) PDB terminus generates a warning on ruby 2.7
Title: Message Title Zachary Kent updated an issue PuppetDB / PDB-4971 PDB terminus generates a warning on ruby 2.7 Change By: Zachary Kent Fix Version/s: PDB 7.0.1 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.378969.1605830582000.91100.1607039220322%40Atlassian.JIRA.
Jira (PUP-10808) Send release announcement (Puppet Platform 7.1.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10808 Send release announcement (Puppet Platform 7.1.0) Issue Type: Task Assignee: Morgan Rhodes Created: 2020/12/03 3:46 PM Due Date: 2020/12/15 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-12-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 7.1.0 is now available".
Jira (PUP-10803) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.1.0)
Title: Message Title Morgan Rhodes created an issue Puppet / PUP-10803 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.1.0) Issue Type: Task Assignee: Nirupama Mantha Created: 2020/12/03 3:46 PM Due Date: 2020/12/09 Labels: release Priority: Normal Reporter: Morgan Rhodes (Initial planned release date: 2020-12-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-10807) Publish documentation and updates and release notes (Puppet Platform 7.1.0)
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-10807 Publish documentation and updates and release notes (Puppet Platform 7.1.0) Change By: Morgan Rhodes Epic Link: PUP-10801 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379891.1607039212000.91114.1607039220730%40Atlassian.JIRA.
Jira (PDB-4975) PDB will not start when sync is configured and garbage collection is disabled
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4975 PDB will not start when sync is configured and garbage collection is disabled Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379880.1607038552000.91091.1607038920034%40Atlassian.JIRA.
Jira (PDB-4975) PDB will not start when sync is configured and garbage collection is disabled
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-4975
PDB will not start when sync is configured and garbage collection is disabled
Change By:
Austin Blatt
This only affects {{pe-puppetdb}}.PuppetDB hangs indefinately when starting in 6.13.1 when sync is enabled and garbage collection is disabled. This looks to have been caused by https://tickets.puppetlabs.com/browse/PDB-4938. In that ticket, in order to prevent deadlocks between initial garbage collection and initial sync on startup, we serialized the initial garbage collection and sync with a promise. When the initial garbage collection completes it delivers on a promise and the initial sync can start. If gc is disabled, the promise is never delivered and sync can never run. The startup process hangs with puppetdb in maintenance mode and nothing more in the logs. PuppetDB stops logging and stays in maintenance mode. The last logs output are as follows.{code}2020-12-03T13:03:26.752-06:00 INFO [c.z.h.HikariDataSource] PDBReadPool - Start completed.2020-12-03T13:03:26.850-06:00 INFO [c.z.h.HikariDataSource] PDBWritePool - Starting...2020-12-03T13:03:26.851-06:00 INFO [c.z.h.HikariDataSource] PDBWritePool - Start completed.{code}The workaround is to enable garbage collection or disable sync. We enabled garbage collection by setting {{gc-interval = 20160}} in {{database.ini}}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4975) PDB will not start when sync is configured and garbage collection is disabled
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-4975
PDB will not start when sync is configured and garbage collection is disabled
Change By:
Austin Blatt
This only affects {{pe-puppetdb}}. PuppetDB hangs indefinately when starting in 6.13.1 when sync is enabled and garbage collection is disabled. This looks to have been caused by https://tickets.puppetlabs.com/browse/PDB-4938. In that ticket, in order to prevent deadlocks between initial garbage collection and initial sync on startup, we serialized the initial garbage collection and sync with a promise. When the initial garbage collection completes it delivers on a promise and the initial sync can start. If gc is disabled, the promise is never delivered and sync can never run. The startup process hangs with puppetdb in maintenance mode and nothing more in the logs. PuppetDB stops logging and stays in maintenance mode. The last logs output are as follows.{code}2020-12-03T13:03:26.752-06:00 INFO [c.z.h.HikariDataSource] PDBReadPool - Start completed.2020-12-03T13:03:26.850-06:00 INFO [c.z.h.HikariDataSource] PDBWritePool - Starting...2020-12-03T13:03:26.851-06:00 INFO [c.z.h.HikariDataSource] PDBWritePool - Start completed.{code}The workaround is to enable garbage collection or disable sync. We enabled garbage collection by setting {{gc-interval = 20160}} in {{database.ini}}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PDB-4975) PDB will not start when sync is configured and garbage collection is disabled
Title: Message Title zendesk.jira updated an issue PuppetDB / PDB-4975 PDB will not start when sync is configured and garbage collection is disabled Change By: zendesk.jira Labels: jira_escalated Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379880.1607038552000.91086.1607038680036%40Atlassian.JIRA.
Jira (PDB-4976) Disabling garbage collection will prevent startup with sync enabled
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4976 Disabling garbage collection will prevent startup with sync enabled Issue Type: Bug Affects Versions: PDB 6.13.1 Assignee: Austin Blatt Created: 2020/12/03 3:36 PM Priority: Normal Reporter: Austin Blatt This only affects pe-puppetdb. In order to prevent deadlocks between initial garbage collection and initial sync on startup, we serialized the two with a promise. When the initial garbage collection completes it delivers on a promise and the initial sync can start. If gc is disabled, the promise is never delivered and sync can never run. The startup process hangs with puppetdb in maintenance mode and nothing in the logs. Add Comment
Jira (PDB-4975) PDB will not start when sync is configured and garbage collection is disabled
Title: Message Title zendesk.jira updated an issue PuppetDB / PDB-4975 PDB will not start when sync is configured and garbage collection is disabled Change By: zendesk.jira Zendesk Ticket Count: 1 Zendesk Ticket IDs: 42226 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379880.1607038552000.91085.1607038620100%40Atlassian.JIRA.
Jira (PDB-4975) PDB will not start when sync is configured and garbage collection is disabled
Title: Message Title Jarret Lavallee created an issue PuppetDB / PDB-4975 PDB will not start when sync is configured and garbage collection is disabled Issue Type: Bug Affects Versions: PDB 6.13.1 Assignee: Unassigned Components: PuppetDB Created: 2020/12/03 3:35 PM Priority: Normal Reporter: Jarret Lavallee PuppetDB hangs indefinately when starting in 6.13.1 when sync is enabled and garbage collection is disabled. This looks to have been caused by https://tickets.puppetlabs.com/browse/PDB-4938. PuppetDB stops logging and stays in maintenance mode. The last logs output are as follows. 2020-12-03T13:03:26.752-06:00 INFO [c.z.h.HikariDataSource] PDBReadPool - Start completed. 2020-12-03T13:03:26.850-06:00 INFO [c.z.h.HikariDataSource] PDBWritePool - Starting... 2020-12-03T13:03:26.851-06:00 INFO [c.z.h.HikariDataSource] PDBWritePool - Start completed.
Jira (FACT-2886) networking.interfaces fact not appearing
Title: Message Title Josh Cooper commented on FACT-2886 Re: networking.interfaces fact not appearing Moved to facter project Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379783.1606999223000.91074.1607038200063%40Atlassian.JIRA.
Jira (PUP-10799) networking.interfaces fact not appearing
Title: Message Title Josh Cooper commented on PUP-10799 Re: networking.interfaces fact not appearing The facter-networking-interfaces.log shows: 167 │ [2020-12-03 12:38:53.226174 ] DEBUG Facter::Resolvers::NetworkingLinux - fill_ip_v4_info! 168 │ [2020-12-03 12:38:53.226538 ] DEBUG Facter::Util::FileHelper - File at: /run/systemd/netif/leases/53 is not accessible. 169 │ [2020-12-03 12:38:53.228884 ] DEBUG Facter::Core::Execution::Posix - Executing command: ip route get 1 170 │ [2020-12-03 12:38:53.243479 ] DEBUG Facter::Resolvers::NetworkingLinux - resolving fact interfaces, but undefined method `each' for nil:NilClass The ip route get 1 is coming from https://github.com/puppetlabs/facter/blob/fd9beb8e809e3c6ef5f43af409d77e20396a5044/lib/facter/resolvers/networking_linux_resolver.rb#L145. Something goes wrong after that happens. It doesn't appear --trace works for core facts, so I'm not sure how to get a backtrace... Add Comment
Jira (FACT-2886) networking.interfaces fact not appearing
Title: Message Title Josh Cooper moved an issue Facter / FACT-2886 networking.interfaces fact not appearing Change By: Josh Cooper Key: PUP FACT - 10799 2886 Affects Version/s: PUP 7.0.0 Affects Version/s: FACT 4.0.46 Project: Puppet Facter Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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-10799) networking.interfaces fact not appearing
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10799 networking.interfaces fact not appearing Change By: Josh Cooper Labels: platform_7.1 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379783.1606999223000.91053.1607036880771%40Atlassian.JIRA.
Jira (PDB-4627) Docs are unclear about supported postgres/java versions
Title: Message Title Zachary Kent assigned an issue to Zachary Kent PuppetDB / PDB-4627 Docs are unclear about supported postgres/java versions Change By: Zachary Kent Assignee: Zachary Kent Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.342654.1579514884000.91000.1607034600067%40Atlassian.JIRA.
Jira (PDB-4627) Docs are unclear about supported postgres/java versions
Title: Message Title Zachary Kent commented on PDB-4627 Re: Docs are unclear about supported postgres/java versions Hi Tim Meusel, apologies for the very long delay. For PuppetDB 7 we support/recommend PostgreSQL 11 and java 11. We test against PostgreSQL 11,12,13 but don't claim official support for PostgreSQL 12/13. I put a pr up to update the overview page. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.342654.1579514884000.90998.1607034540038%40Atlassian.JIRA.
Jira (PUP-7522) Add the ability to view trusted fact values from an agent
Title: Message Title Josh Cooper commented on PUP-7522 Re: Add the ability to view trusted fact values from an agent So one issue with using the ruby bindings for openssl is that OpenSSL::X509::Certificate#to_text will print the long friendly name for the extension (assuming the puppet ssl application registers the puppet extensions). So you'll see something like: Puppet Node Role Name: ..ci But when writing a manifest, the trusted hash is keyed by the short friendly name: $trusted['pp_role'] So I'm thinking it would be most helpful if the command printed the short friendly name, with perhaps an option to show the full OID (in this example "1.3.6.1.4.1.34380.1.1.13"). What about something like? $ bundle exec puppet ssl show Subject: CN=localhost Issuer: CN=Puppet CA: localhost Serial: 3 Validity: '2020-12-02 19:23:06 UTC' to '2025-12-02 19:23:06 UTC'
Jira (FACT-2884) How to disable Querying Ec2 metadata
Title: Message Title Sanjay Tripathi commented on FACT-2884 Re: How to disable Querying Ec2 metadata Yes, this will definitely help! Thanks for proposing this solution. Can it be possible to get it into the next Facter 4.x release? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379602.1606876774000.90730.1607017200023%40Atlassian.JIRA.
Jira (PUP-1289) Ability to manage a windows service's user account and password
Title: Message Title Josh Cooper commented on PUP-1289 Re: Ability to manage a windows service's user account and password Thanks for that Darren Gipson, I filed PUP-10800 to follow up. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.22659.138842866.90724.1607016960025%40Atlassian.JIRA.
Jira (PUP-10800) Add logonaccount and logonpassword to windows service provider example
Title: Message Title
Josh Cooper created an issue
Puppet / PUP-10800
Add logonaccount and logonpassword to windows service provider example
Issue Type:
Task
Assignee:
Claire Cadman
Components:
Docs
Created:
2020/12/03 9:34 AM
Priority:
Normal
Reporter:
Josh Cooper
We added support for managing the logon user and password to the windows service provider, but it's not reflected in the documentation for the provider. We should add an example to the description: https://github.com/puppetlabs/puppet/blob/96029b003cfbb5303426cbc110f350a0d4b6af06/lib/puppet/provider/service/windows.rb#L5-L12
service { 'name-of-service':
ensure => 'running',
enable => 'true',
logonaccount => 'domain\\user',
logonpassword => $password,
Jira (FACT-2883) Gem-based Facter 4.0.x does not log the facts in debug mode
Title: Message Title Bogdan Irimie commented on FACT-2883 Re: Gem-based Facter 4.0.x does not log the facts in debug mode Sanjay Tripathi great, glad you like the new debug messages. They should get in the next release https://github.com/puppetlabs/facter/pull/2203 Regarding the other debug messages we don't plan to remove them as they help us debug complex use cases. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379599.1606874914000.90721.1607016720177%40Atlassian.JIRA.
Jira (PUP-1289) Ability to manage a windows service's user account and password
Title: Message Title
Darren Gipson commented on PUP-1289
Re: Ability to manage a windows service's user account and password
Hi Puppet, I have been testing this out and really struggled to find any documentation that specified the changes here. I worked it out; please can you update your documentation here and here? Anyone else reading, something like this works:
// this worked for me:
service { 'name-of-service':
logonaccount => 'domain\\user',
logonpassword => $secret, #sensitive
ensure => 'running',
enable => 'true',
}
Add Comment
Jira (FACT-2884) How to disable Querying Ec2 metadata
Title: Message Title Bogdan Irimie commented on FACT-2884 Re: How to disable Querying Ec2 metadata Sanjay Tripathi Unfortunately `facter.conf` path cannot be passed to puppet. Would it help you if we made it possible to override the EC2 facts with FACTER_ec2_metadata= generic FACTER_ec2_userdata= generic and these facts would not make the API calls anymore, they will return the `generic` value? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379602.1606876774000.90706.1607016120182%40Atlassian.JIRA.
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title Tim Meusel commented on FACT-2880 Re: facter 4 differing output from facter 3 for service_provider fact thanks for the feedback. I fixed it in master for puppet-prometheus. I agree with Josh Cooper that a puppet-lint plugin might be really good here (although I think puppet-lint at the moment only checks actual Puppet DSL) Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379364.1606744776000.90699.1607015820025%40Atlassian.JIRA.
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title Bogdan Irimie commented on FACT-2880 Re: facter 4 differing output from facter 3 for service_provider fact Tim Meusel thanks for testing this! After digging a little deeper we found that Facter 3 does not even load the custom fact files if no custom fact is requested. Facter 4 on the other hand always loads the custom facts, even if no custom fact was requested (we do this for multiple reasons, one of them is you might have a custom fact with the same name as a core facts but with a higher weight). Because of this difference Facter 3 was not loading the custom fact file and Facter 4 was loading it when we were executing `puppet resource service sshd`. When we forced Facter 3 to load the file, we got the same behaviour as with Facter 4. Regarding the placement of the code in custom fact, it should always be inside the `setcode` block. Currently we are evaluating how we want to move forward, but once we reach a conclusion I will let you know. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379364.1606744776000.90697.1607015580136%40Atlassian.JIRA.
Jira (PUP-10798) Unable to install rpm packages via provides of the package
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10798 Unable to install rpm packages via provides of the package Change By: Josh Cooper Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379779.1606993694000.90672.1607013780134%40Atlassian.JIRA.
Jira (FACT-2885) adapt test for Ubuntu AARCH64
Title: Message Title Ciprian Badescu created an issue Facter / FACT-2885 adapt test for Ubuntu AARCH64 Issue Type: Task Assignee: Unassigned Created: 2020/12/03 4:49 AM Priority: Normal Reporter: Ciprian Badescu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 (FACT-2885) adapt test for Ubuntu AARCH64
Title: Message Title Ciprian Badescu assigned an issue to Ciprian Badescu Facter / FACT-2885 adapt test for Ubuntu AARCH64 Change By: Ciprian Badescu Assignee: Ciprian Badescu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379785.1606999764000.90551.1606999800065%40Atlassian.JIRA.
Jira (PUP-10799) networking.interfaces fact not appearing
Title: Message Title Chris Boot created an issue Puppet / PUP-10799 networking.interfaces fact not appearing Issue Type: Bug Affects Versions: PUP 7.0.0 Assignee: Unassigned Attachments: facter-networking-interfaces.log, facter-networking-primary.log, facter-networking.log Created: 2020/12/03 4:40 AM Priority: Normal Reporter: Chris Boot Puppet Version: 7.0.0 Puppet Server Version: 6.14.1 OS Name/Version: Debian testing (bullseye) On one of my nodes, Puppet does not pick up the networking.interfaces fact. The fact is visible when querying Facter directly for the top-level fact (e.g. facter networking) but does not show up through Puppet (e.g. puppet facts show networking) or when querying the sub-fact value (e.g. facter networking.interfaces). Add Comment
Jira (PUP-10773) Add a server alias for routes.yaml
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-10773 Add a server alias for routes.yaml Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.376905.1604419718000.90532.1606994400036%40Atlassian.JIRA.
Jira (PUP-10798) Unable to install rpm packages via provides of the package
Title: Message Title
Frank created an issue
Puppet / PUP-10798
Unable to install rpm packages via provides of the package
Issue Type:
Bug
Affects Versions:
PUP 6.14.0
Assignee:
Unassigned
Created:
2020/12/03 3:08 AM
Priority:
Critical
Reporter:
Frank
Puppet Version: 6.14 OS Name/Version: CentOS 8.2 It is not possible to install an rpm package via an provides name of the package. Sample:
package { 'dnf-plugin-post-transaction-actions': ensure => installed}
it will fails with:
Error: Execution of '/usr/bin/dnf -d 0 -e 1 -y list dnf-plugin-post-transaction-actions' returned 1: Error: No matching Packages to list
because dnf list only work with real package names, not with package provides. But an blind dnf call will work:
Jira (FACT-2872) Regressions: secondary interfaces are not anymore reported
Title: Message Title Peter Meier commented on FACT-2872 Re: Regressions: secondary interfaces are not anymore reported Yes that works to get it over bindings, although a bit clumsy: https://code.immerda.ch/immerda/ibox/puppet-modules/-/blob/76e4586bbd6184af6d6df2c57058a709843ff8e0/ib_unbound/manifests/init.pp#L13-19 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379058.1605915439000.90526.1606993020034%40Atlassian.JIRA.
Jira (FACT-2870) Can't run puppet on machines with VLANs as facts are failing
Title: Message Title Peter Meier commented on FACT-2870 Re: Can't run puppet on machines with VLANs as facts are failing I can confirm that with puppet-agent-7.0.0.103.gf0655d02-1.el7.x86_64 I was able to run puppet again. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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.379053.1605909534000.90494.1606986001862%40Atlassian.JIRA.
