Jira (PUP-9307) Account for trailing slashes in mount resource titles
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-9307 Account for trailing slashes in mount resource titles Change By: Jarret Lavallee CS Priority: Needs Priority Priority: Minor Normal Method Found: Customer Feedback Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9409) Release puppetlabs-cron_core
Title: Message Title Melissa Stone commented on PUP-9409 Re: Release puppetlabs-cron_core There are currently outstanding PRs that need to be merged before cron_core is released 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-9419) Release puppetlabs-host_core
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9419 Release puppetlabs-host_core Change By: Melissa Stone 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-9422) Release puppetlabs-mount_core
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9422 Release puppetlabs-mount_core Change By: Melissa Stone 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-9420) Release puppetlabs-zone_core
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9420 Release puppetlabs-zone_core Change By: Melissa Stone 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-9421) Release puppetlabs-macdslocal_core
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9421 Release puppetlabs-macdslocal_core Change By: Melissa Stone 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-9412) Release puppetlabs-augeas_core
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9412 Release puppetlabs-augeas_core Change By: Melissa Stone 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-9416) Release puppetlabs-zfs_core
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9416 Release puppetlabs-zfs_core Change By: Melissa Stone 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-9423) Release puppetlabs-k5login_core
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9423 Release puppetlabs-k5login_core Change By: Melissa Stone 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-9415) Release puppetlabs-network_device_core
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9415 Release puppetlabs-network_device_core Change By: Melissa Stone 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-9417) Release puppetlabs-maillist_core
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9417 Release puppetlabs-maillist_core Change By: Melissa Stone 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-9414) Release puppetlabs-selinux_core
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9414 Release puppetlabs-selinux_core Change By: Melissa Stone 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-9413) Release puppetlabs-nagios_core
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9413 Release puppetlabs-nagios_core Change By: Melissa Stone 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-9411) Release puppetlabs-yumrepo_core
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9411 Release puppetlabs-yumrepo_core Change By: Melissa Stone 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-9410) Release puppetlabs-sshkeys_core
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9410 Release puppetlabs-sshkeys_core Change By: Melissa Stone 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-9418) Release puppetlabs-mailalias_core
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9418 Release puppetlabs-mailalias_core Change By: Melissa Stone 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-9408) Module release extravaganza 2019
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9408 Module release extravaganza 2019 Change By: Melissa Stone Team/s: 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 (PUP-9422) Release puppetlabs-mount_core
Title: Message Title Melissa Stone created an issue Puppet / PUP-9422 Release puppetlabs-mount_core Issue Type: Task Assignee: Unassigned Created: 2019/01/09 3:45 PM Priority: Normal Reporter: Melissa Stone https://confluence.puppetlabs.com/pages/viewpage.action?spaceKey=systemsEngineering=Module+Release+Process#ModuleReleaseProcess-UnsupportedReleasePreparation Create an Unsupported Release ticket with Kerminator. If Kerminator doesn't work, you can do it manually. In your own fork, make sure the branch that is going to be released is up to date, then create your own branch off of it for version preparation. Look at the pull requests to see if there are any easy, sensible merges. Update metadata.json appropriately; that is, bump the version number following semver. Update the CHANGELOG with a new section for this release. Update the README with all changes for this release. (necessary if features are added didn’t document the changes) Run acceptance tests to ensure they pass and are reasonable. Symlinks: make sure we don't have any (use `find . -type l`). Create your PR against the release branch. Get someone else to merge and review your PR. Release the module.
Jira (PUP-9423) Release puppetlabs-k5login_core
Title: Message Title Melissa Stone created an issue Puppet / PUP-9423 Release puppetlabs-k5login_core Issue Type: Task Assignee: Unassigned Created: 2019/01/09 3:45 PM Priority: Normal Reporter: Melissa Stone https://confluence.puppetlabs.com/pages/viewpage.action?spaceKey=systemsEngineering=Module+Release+Process#ModuleReleaseProcess-UnsupportedReleasePreparation Create an Unsupported Release ticket with Kerminator. If Kerminator doesn't work, you can do it manually. In your own fork, make sure the branch that is going to be released is up to date, then create your own branch off of it for version preparation. Look at the pull requests to see if there are any easy, sensible merges. Update metadata.json appropriately; that is, bump the version number following semver. Update the CHANGELOG with a new section for this release. Update the README with all changes for this release. (necessary if features are added didn’t document the changes) Run acceptance tests to ensure they pass and are reasonable. Symlinks: make sure we don't have any (use `find . -type l`). Create your PR against the release branch. Get someone else to merge and review your PR. Release the module.
Jira (PUP-9419) Release puppetlabs-host_core
Title: Message Title Melissa Stone created an issue Puppet / PUP-9419 Release puppetlabs-host_core Issue Type: Task Assignee: Unassigned Created: 2019/01/09 3:45 PM Priority: Normal Reporter: Melissa Stone https://confluence.puppetlabs.com/pages/viewpage.action?spaceKey=systemsEngineering=Module+Release+Process#ModuleReleaseProcess-UnsupportedReleasePreparation Create an Unsupported Release ticket with Kerminator. If Kerminator doesn't work, you can do it manually. In your own fork, make sure the branch that is going to be released is up to date, then create your own branch off of it for version preparation. Look at the pull requests to see if there are any easy, sensible merges. Update metadata.json appropriately; that is, bump the version number following semver. Update the CHANGELOG with a new section for this release. Update the README with all changes for this release. (necessary if features are added didn’t document the changes) Run acceptance tests to ensure they pass and are reasonable. Symlinks: make sure we don't have any (use `find . -type l`). Create your PR against the release branch. Get someone else to merge and review your PR. Release the module.
Jira (PUP-9421) Release puppetlabs-macdslocal_core
Title: Message Title Melissa Stone created an issue Puppet / PUP-9421 Release puppetlabs-macdslocal_core Issue Type: Task Assignee: Unassigned Created: 2019/01/09 3:45 PM Priority: Normal Reporter: Melissa Stone https://confluence.puppetlabs.com/pages/viewpage.action?spaceKey=systemsEngineering=Module+Release+Process#ModuleReleaseProcess-UnsupportedReleasePreparation Create an Unsupported Release ticket with Kerminator. If Kerminator doesn't work, you can do it manually. In your own fork, make sure the branch that is going to be released is up to date, then create your own branch off of it for version preparation. Look at the pull requests to see if there are any easy, sensible merges. Update metadata.json appropriately; that is, bump the version number following semver. Update the CHANGELOG with a new section for this release. Update the README with all changes for this release. (necessary if features are added didn’t document the changes) Run acceptance tests to ensure they pass and are reasonable. Symlinks: make sure we don't have any (use `find . -type l`). Create your PR against the release branch. Get someone else to merge and review your PR. Release the module.
Jira (PUP-9420) Release puppetlabs-zone_core
Title: Message Title Melissa Stone created an issue Puppet / PUP-9420 Release puppetlabs-zone_core Issue Type: Task Assignee: Unassigned Created: 2019/01/09 3:45 PM Priority: Normal Reporter: Melissa Stone https://confluence.puppetlabs.com/pages/viewpage.action?spaceKey=systemsEngineering=Module+Release+Process#ModuleReleaseProcess-UnsupportedReleasePreparation Create an Unsupported Release ticket with Kerminator. If Kerminator doesn't work, you can do it manually. In your own fork, make sure the branch that is going to be released is up to date, then create your own branch off of it for version preparation. Look at the pull requests to see if there are any easy, sensible merges. Update metadata.json appropriately; that is, bump the version number following semver. Update the CHANGELOG with a new section for this release. Update the README with all changes for this release. (necessary if features are added didn’t document the changes) Run acceptance tests to ensure they pass and are reasonable. Symlinks: make sure we don't have any (use `find . -type l`). Create your PR against the release branch. Get someone else to merge and review your PR. Release the module.
Jira (PUP-9417) Release puppetlabs-maillist_core
Title: Message Title Melissa Stone created an issue Puppet / PUP-9417 Release puppetlabs-maillist_core Issue Type: Task Assignee: Unassigned Created: 2019/01/09 3:44 PM Priority: Normal Reporter: Melissa Stone https://confluence.puppetlabs.com/pages/viewpage.action?spaceKey=systemsEngineering=Module+Release+Process#ModuleReleaseProcess-UnsupportedReleasePreparation Create an Unsupported Release ticket with Kerminator. If Kerminator doesn't work, you can do it manually. In your own fork, make sure the branch that is going to be released is up to date, then create your own branch off of it for version preparation. Look at the pull requests to see if there are any easy, sensible merges. Update metadata.json appropriately; that is, bump the version number following semver. Update the CHANGELOG with a new section for this release. Update the README with all changes for this release. (necessary if features are added didn’t document the changes) Run acceptance tests to ensure they pass and are reasonable. Symlinks: make sure we don't have any (use `find . -type l`). Create your PR against the release branch. Get someone else to merge and review your PR. Release the module.
Jira (PUP-9418) Release puppetlabs-mailalias_core
Title: Message Title Melissa Stone created an issue Puppet / PUP-9418 Release puppetlabs-mailalias_core Issue Type: Task Assignee: Unassigned Created: 2019/01/09 3:44 PM Priority: Normal Reporter: Melissa Stone https://confluence.puppetlabs.com/pages/viewpage.action?spaceKey=systemsEngineering=Module+Release+Process#ModuleReleaseProcess-UnsupportedReleasePreparation Create an Unsupported Release ticket with Kerminator. If Kerminator doesn't work, you can do it manually. In your own fork, make sure the branch that is going to be released is up to date, then create your own branch off of it for version preparation. Look at the pull requests to see if there are any easy, sensible merges. Update metadata.json appropriately; that is, bump the version number following semver. Update the CHANGELOG with a new section for this release. Update the README with all changes for this release. (necessary if features are added didn’t document the changes) Run acceptance tests to ensure they pass and are reasonable. Symlinks: make sure we don't have any (use `find . -type l`). Create your PR against the release branch. Get someone else to merge and review your PR. Release the module.
Jira (PUP-9416) Release puppetlabs-zfs_core
Title: Message Title Melissa Stone created an issue Puppet / PUP-9416 Release puppetlabs-zfs_core Issue Type: Task Assignee: Unassigned Created: 2019/01/09 3:44 PM Priority: Normal Reporter: Melissa Stone https://confluence.puppetlabs.com/pages/viewpage.action?spaceKey=systemsEngineering=Module+Release+Process#ModuleReleaseProcess-UnsupportedReleasePreparation Create an Unsupported Release ticket with Kerminator. If Kerminator doesn't work, you can do it manually. In your own fork, make sure the branch that is going to be released is up to date, then create your own branch off of it for version preparation. Look at the pull requests to see if there are any easy, sensible merges. Update metadata.json appropriately; that is, bump the version number following semver. Update the CHANGELOG with a new section for this release. Update the README with all changes for this release. (necessary if features are added didn’t document the changes) Run acceptance tests to ensure they pass and are reasonable. Symlinks: make sure we don't have any (use `find . -type l`). Create your PR against the release branch. Get someone else to merge and review your PR. Release the module.
Jira (PUP-9415) Release puppetlabs-network_device_core
Title: Message Title Melissa Stone created an issue Puppet / PUP-9415 Release puppetlabs-network_device_core Issue Type: Task Assignee: Unassigned Created: 2019/01/09 3:44 PM Priority: Normal Reporter: Melissa Stone https://confluence.puppetlabs.com/pages/viewpage.action?spaceKey=systemsEngineering=Module+Release+Process#ModuleReleaseProcess-UnsupportedReleasePreparation Create an Unsupported Release ticket with Kerminator. If Kerminator doesn't work, you can do it manually. In your own fork, make sure the branch that is going to be released is up to date, then create your own branch off of it for version preparation. Look at the pull requests to see if there are any easy, sensible merges. Update metadata.json appropriately; that is, bump the version number following semver. Update the CHANGELOG with a new section for this release. Update the README with all changes for this release. (necessary if features are added didn’t document the changes) Run acceptance tests to ensure they pass and are reasonable. Symlinks: make sure we don't have any (use `find . -type l`). Create your PR against the release branch. Get someone else to merge and review your PR. Release the module.
Jira (PUP-9412) Release puppetlabs-augeas_core
Title: Message Title Melissa Stone created an issue Puppet / PUP-9412 Release puppetlabs-augeas_core Issue Type: Task Assignee: Unassigned Created: 2019/01/09 3:43 PM Priority: Normal Reporter: Melissa Stone https://confluence.puppetlabs.com/pages/viewpage.action?spaceKey=systemsEngineering=Module+Release+Process#ModuleReleaseProcess-UnsupportedReleasePreparation Create an Unsupported Release ticket with Kerminator. If Kerminator doesn't work, you can do it manually. In your own fork, make sure the branch that is going to be released is up to date, then create your own branch off of it for version preparation. Look at the pull requests to see if there are any easy, sensible merges. Update metadata.json appropriately; that is, bump the version number following semver. Update the CHANGELOG with a new section for this release. Update the README with all changes for this release. (necessary if features are added didn’t document the changes) Run acceptance tests to ensure they pass and are reasonable. Symlinks: make sure we don't have any (use `find . -type l`). Create your PR against the release branch. Get someone else to merge and review your PR. Release the module.
Jira (PUP-9411) Release puppetlabs-yumrepo_core
Title: Message Title Melissa Stone created an issue Puppet / PUP-9411 Release puppetlabs-yumrepo_core Issue Type: Task Assignee: Unassigned Created: 2019/01/09 3:43 PM Priority: Normal Reporter: Melissa Stone https://confluence.puppetlabs.com/pages/viewpage.action?spaceKey=systemsEngineering=Module+Release+Process#ModuleReleaseProcess-UnsupportedReleasePreparation Create an Unsupported Release ticket with Kerminator. If Kerminator doesn't work, you can do it manually. In your own fork, make sure the branch that is going to be released is up to date, then create your own branch off of it for version preparation. Look at the pull requests to see if there are any easy, sensible merges. Update metadata.json appropriately; that is, bump the version number following semver. Update the CHANGELOG with a new section for this release. Update the README with all changes for this release. (necessary if features are added didn’t document the changes) Run acceptance tests to ensure they pass and are reasonable. Symlinks: make sure we don't have any (use `find . -type l`). Create your PR against the release branch. Get someone else to merge and review your PR. Release the module.
Jira (PUP-9414) Release puppetlabs-selinux_core
Title: Message Title Melissa Stone created an issue Puppet / PUP-9414 Release puppetlabs-selinux_core Issue Type: Task Assignee: Unassigned Created: 2019/01/09 3:43 PM Priority: Normal Reporter: Melissa Stone https://confluence.puppetlabs.com/pages/viewpage.action?spaceKey=systemsEngineering=Module+Release+Process#ModuleReleaseProcess-UnsupportedReleasePreparation Create an Unsupported Release ticket with Kerminator. If Kerminator doesn't work, you can do it manually. In your own fork, make sure the branch that is going to be released is up to date, then create your own branch off of it for version preparation. Look at the pull requests to see if there are any easy, sensible merges. Update metadata.json appropriately; that is, bump the version number following semver. Update the CHANGELOG with a new section for this release. Update the README with all changes for this release. (necessary if features are added didn’t document the changes) Run acceptance tests to ensure they pass and are reasonable. Symlinks: make sure we don't have any (use `find . -type l`). Create your PR against the release branch. Get someone else to merge and review your PR. Release the module.
Jira (PUP-9413) Release puppetlabs-nagios_core
Title: Message Title Melissa Stone created an issue Puppet / PUP-9413 Release puppetlabs-nagios_core Issue Type: Task Assignee: Unassigned Created: 2019/01/09 3:43 PM Priority: Normal Reporter: Melissa Stone https://confluence.puppetlabs.com/pages/viewpage.action?spaceKey=systemsEngineering=Module+Release+Process#ModuleReleaseProcess-UnsupportedReleasePreparation Create an Unsupported Release ticket with Kerminator. If Kerminator doesn't work, you can do it manually. In your own fork, make sure the branch that is going to be released is up to date, then create your own branch off of it for version preparation. Look at the pull requests to see if there are any easy, sensible merges. Update metadata.json appropriately; that is, bump the version number following semver. Update the CHANGELOG with a new section for this release. Update the README with all changes for this release. (necessary if features are added didn’t document the changes) Run acceptance tests to ensure they pass and are reasonable. Symlinks: make sure we don't have any (use `find . -type l`). Create your PR against the release branch. Get someone else to merge and review your PR. Release the module.
Jira (PUP-9409) Release puppetlabs-cron_core
Title: Message Title Melissa Stone created an issue Puppet / PUP-9409 Release puppetlabs-cron_core Issue Type: Task Assignee: Unassigned Created: 2019/01/09 3:42 PM Priority: Normal Reporter: Melissa Stone https://confluence.puppetlabs.com/pages/viewpage.action?spaceKey=systemsEngineering=Module+Release+Process#ModuleReleaseProcess-UnsupportedReleasePreparation Create an Unsupported Release ticket with Kerminator. If Kerminator doesn't work, you can do it manually. In your own fork, make sure the branch that is going to be released is up to date, then create your own branch off of it for version preparation. Look at the pull requests to see if there are any easy, sensible merges. Update metadata.json appropriately; that is, bump the version number following semver. Update the CHANGELOG with a new section for this release. Update the README with all changes for this release. (necessary if features are added didn’t document the changes) Run acceptance tests to ensure they pass and are reasonable. Symlinks: make sure we don't have any (use `find . -type l`). Create your PR against the release branch. Get someone else to merge and review your PR. Release the module.
Jira (PUP-9410) Release puppetlabs-sshkeys_core
Title: Message Title Melissa Stone created an issue Puppet / PUP-9410 Release puppetlabs-sshkeys_core Issue Type: Task Assignee: Unassigned Created: 2019/01/09 3:42 PM Priority: Normal Reporter: Melissa Stone https://confluence.puppetlabs.com/pages/viewpage.action?spaceKey=systemsEngineering=Module+Release+Process#ModuleReleaseProcess-UnsupportedReleasePreparation Create an Unsupported Release ticket with Kerminator. If Kerminator doesn't work, you can do it manually. In your own fork, make sure the branch that is going to be released is up to date, then create your own branch off of it for version preparation. Look at the pull requests to see if there are any easy, sensible merges. Update metadata.json appropriately; that is, bump the version number following semver. Update the CHANGELOG with a new section for this release. Update the README with all changes for this release. (necessary if features are added didn’t document the changes) Run acceptance tests to ensure they pass and are reasonable. Symlinks: make sure we don't have any (use `find . -type l`). Create your PR against the release branch. Get someone else to merge and review your PR. Release the module.
Jira (PUP-9408) Module release extravaganza 2019
Title: Message Title Melissa Stone created an issue Puppet / PUP-9408 Module release extravaganza 2019 Issue Type: Epic Assignee: Unassigned Created: 2019/01/09 3:35 PM Priority: Normal Reporter: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PDB-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title Robert Roland updated an issue PuppetDB / PDB-2487 Allow for a "resource-events-ttl" to reduce the number of days of events that are stored Change By: Robert Roland Fix Version/s: PDB 6.0.2 Fix Version/s: PDB 5.2.7 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-4245) Test merge master
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4245 Test merge master Issue Type: Bug Assignee: Unassigned Created: 2019/01/09 3:20 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs.
Jira (PDB-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-2487 Allow for a "resource-events-ttl" to reduce the number of days of events that are stored Change By: Austin Blatt Fix Version/s: PDB 5.2.7 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-4184) Add Kubernetes deployment descriptors
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4184 Add Kubernetes deployment descriptors Change By: Austin Blatt Fix Version/s: PDB 6.0.2 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-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-2487 Allow for a "resource-events-ttl" to reduce the number of days of events that are stored Change By: Austin Blatt Fix Version/s: PDB 6.0.2 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-4184) Add Kubernetes deployment descriptors
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4184 Add Kubernetes deployment descriptors Change By: Austin Blatt Fix Version/s: PDB 6.0.2 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-4184) Add Kubernetes deployment descriptors
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4184 Add Kubernetes deployment descriptors Change By: Austin Blatt Fix Version/s: PDB 6.0.2 Fix Version/s: PDB n/a 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-4184) Add Kubernetes deployment descriptors
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4184 Add Kubernetes deployment descriptors Change By: Austin Blatt Fix Version/s: PDB 6.0.2 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-1049) Provide better out-of-the-box task experience
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1049 Provide better out-of-the-box task experience Change By: Cas Donoghue Release Notes: New Feature Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1049) Provide better out-of-the-box task experience
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1049 Provide better out-of-the-box task experience Change By: Cas Donoghue Release Notes Summary: The `package` and `service` tasks now select task implementation based on available target features and their platform specific implementations are private. Release Notes: New Feature 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-9407) Don't backup to the local filebucket by default
Title: Message Title Josh Cooper created an issue Puppet / PUP-9407 Don't backup to the local filebucket by default Issue Type: Bug Assignee: Unassigned Created: 2019/01/09 3:03 PM Fix Versions: PUP 7.0.0 Priority: Normal Reporter: Josh Cooper Puppet agent's will backup any overwritten or deleted file to its local filebucket via the default backup parameter for the file type. It defaults to puppet which means to use the filebucket named puppet which is automatically created. Many users run into trouble because the filebucket will grow unbounded, such as PUP-1137. It has been proposed to use the tidy resource to clean up stale files, but can lead to memory issues with large numbers of file resources being created. See https://github.com/npwalker/pe_metric_curl_cron_jobs/issues/3 For this ticket we should change the default value of the bucket parameter from puppet to false, see https://github.com/puppetlabs/puppet/blob/6.1.0/lib/puppet/type/file.rb#L110, and update the file reference documentation to reflect the new behavior. Add Comment
Jira (PUP-9406) Manage space allocated to filebucket
Title: Message Title
Joel Weierman updated an issue
Puppet / PUP-9406
Manage space allocated to filebucket
Change By:
Joel Weierman
File backup is a helpful feature that by default is currently turned on in Puppet. (Note: that it can be manually configured to be turned off, via "File { backup => false }" .However, as the resource is not actively managed, over time, the filebucket directory eventually fills up and can eat up all the allocated disk space. As a Puppet user, I would like for the filebucket resource to be shipped with some "sane" defaults (e.g. 30 days or 500 MB) that could be further modified based on need. These settings should be easily overridable to configure the amount of data either by number of days or maximum size allocated to the Puppet filebucket. As a Puppet user managing a large amount of resources and machines, I also know that when there are lots of files being managed and backed up to filebucket so the management method should be performant for large numbers of files/directories.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9406) Manage space allocated to filebucket
Title: Message Title
Joel Weierman created an issue
Puppet / PUP-9406
Manage space allocated to filebucket
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2019/01/09 3:00 PM
Priority:
Normal
Reporter:
Joel Weierman
File backup is a helpful feature that by default is currently turned on in Puppet. (Note: that it can be manually configured to be turned off, via "File { backup => false } ". However, as the resource is not actively managed, over time, the filebucket directory eventually fills up and can eat up all the allocated disk space. As a Puppet user, I would like for the filebucket resource to be shipped with some "sane" defaults (e.g. 30 days or 500 MB) that could be further modified based on need. These settings should be easily overridable to configure the amount of data either by number of days or maximum size allocated to the Puppet filebucket. As a Puppet user managing a large amount of resources and machines, I also know that when there are lots of files being managed and backed up to filebucket so the management method should be performant for large numbers of files/directories.
Add Comment
Jira (PDB-4205) Upgrade 6.0.x clj-parent to at least 2.4.0
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-4205 Upgrade 6.0.x clj-parent to at least 2.4.0 Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4205) Upgrade 6.0.x clj-parent to at least 2.4.0
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-4205 Upgrade 6.0.x clj-parent to at least 2.4.0 Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To 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-57) Download a file
Title: Message Title Alex Dreyer commented on BOLT-57 Re: Download a file Another user has requested "file copy" rather then just file_download. 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-1074) Local transport returns incorrect exit status
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1074 Local transport returns incorrect exit status Change By: Melissa Amos Labels: docs_reviewed 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-938) Account for more than one entry in bolt.yaml puppetdb.server_urls parameter
Title: Message Title Melissa Amos commented on BOLT-938 Re: Account for more than one entry in bolt.yaml puppetdb.server_urls parameter Docs update: http://docs-internal.puppet.com/docs/bolt/dev/bolt_new_features.html#respect-multiple-puppetdb-server-urls-1-9-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 (BOLT-1074) Local transport returns incorrect exit status
Title: Message Title Melissa Amos commented on BOLT-1074 Re: Local transport returns incorrect exit status Docs update: http://docs-internal.puppet.com/docs/bolt/dev/bolt_resolved_issues.html#local-transport-returned-incorrect-exit-status-1-9-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 (BOLT-938) Account for more than one entry in bolt.yaml puppetdb.server_urls parameter
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-938 Account for more than one entry in bolt.yaml puppetdb.server_urls parameter Change By: Melissa Amos Labels: docs_reviewed 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-756) Bolt crashes with invalid puppetdb config
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-756 Bolt crashes with invalid puppetdb config Change By: Melissa Amos Labels: docs_reviewed 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-756) Bolt crashes with invalid puppetdb config
Title: Message Title Melissa Amos commented on BOLT-756 Re: Bolt crashes with invalid puppetdb config Docs update: http://docs-internal.puppet.com/docs/bolt/dev/bolt_resolved_issues.html#bolt-crashed-if-puppetdb-configuration-was-invalid-1-9-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 (BOLT-938) Account for more than one entry in bolt.yaml puppetdb.server_urls parameter
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-938 Account for more than one entry in bolt.yaml puppetdb.server_urls parameter Change By: Melissa Amos Release Notes: New Feature 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-1075) command : commands fail if in a remote session to Windows
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-1075 command : commands fail if in a remote session to Windows Change By: Melissa Amos Labels: bolt known-issue-added windows Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9317) Backport PUP-8002 to 5.5.x ("Attempt to redefine entity")
Title: Message Title
Jean Bond updated an issue
Puppet / PUP-9317
Backport PUP-8002 to 5.5.x ("Attempt to redefine entity")
Change By:
Jean Bond
Labels:
resolved-issue-added
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-8962) Type and provider info should be logged when prefetch fails
Title: Message Title Kris Bosland updated an issue Puppet / PUP-8962 Type and provider info should be logged when prefetch fails Change By: Kris Bosland Release Notes Summary: Puppet will now log exceptions that happen during prefetch. Also exception handling in prefetch was fixed to the correct set of exceptions. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9399) Puppet agent 6 ignores srv_domain config
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9399 Puppet agent 6 ignores srv_domain config Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1075) command : commands fail if in a remote session to Windows
Title: Message Title Michael Smith commented on BOLT-1075 Re: command : commands fail if in a remote session to Windows We could catch the error and provide a better error message. Might also be a method we can call on STDIN to determine whether it's usable. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4543) Document how to run AIO puppet acceptance in acceptance_tests.md
Title: Message Title Melissa Stone updated an issue Puppet / PUP-4543 Document how to run AIO puppet acceptance in acceptance_tests.md Change By: Melissa Stone 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-4543) Document how to run AIO puppet acceptance in acceptance_tests.md
Title: Message Title Melissa Stone assigned an issue to Melissa Stone Puppet / PUP-4543 Document how to run AIO puppet acceptance in acceptance_tests.md Change By: Melissa Stone Assignee: Melissa Stone 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-9399) Puppet agent 6 ignores srv_domain config
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9399 Puppet agent 6 ignores srv_domain config Change By: Josh Cooper Release Notes Summary: Puppet 6.0 and up ignored the srv_domain setting , which prevented it from connecting to the CA when using DNS SRV records . to connect to the `ca_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-9399) Puppet agent 6 ignores srv_domain config
Title: Message Title Josh Cooper commented on PUP-9399 Re: Puppet agent 6 ignores srv_domain config Merged to 6.0.x in https://github.com/puppetlabs/puppet/commit/acd3e15b99355339dfff5c8196ac65afe0428ab8 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-1075) command : commands fail if in a remote session to Windows
Title: Message Title Alex Dreyer commented on BOLT-1075 Re: command : commands fail if in a remote session to Windows Michael Smith is there a way we can detect this and refuse to accept input interactively? Would we want to do that anyway? 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-6165) it should not be possible to disable manifest ordering
Title: Message Title Christopher Wood commented on PUP-6165 Re: it should not be possible to disable manifest ordering As a post-hoc note, I do in fact have random ordering turned on. It is indeed an excellent fuzzer. However I think everybody at work here except for me will be delighted with this change. [root@puppetmaster1 ~]# grep ^order /etc/puppetlabs/puppet/puppet.conf ordering = random 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-1075) command : commands fail if in a remote session to Windows
Title: Message Title Michael Smith commented on BOLT-1075 Re: command : commands fail if in a remote session to Windows Melissa Amos let's add this as a known issue. The restriction seems to be in how PowerShell remoting is implemented, so this is something Microsoft would have to change to fix. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1075) command : commands fail if in a remote session to Windows
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-1075 command : commands fail if in a remote session to Windows Change By: Michael Smith Release Notes Summary: Interactive tools fail when run in a remote PowerShell session. As such, using `--password` to prompt for a password when running Bolt will trigger an error noting EBADF. Work-arounds include putting the password in bolt.yaml or an inventory file, passing the password on the command-line, or not running Bolt over a remote PowerShell session. Release Notes: Known Issue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (BOLT-1075) command : commands fail if in a remote session to Windows
Title: Message Title William Hurt commented on BOLT-1075 Re: command : commands fail if in a remote session to Windows That seems fair. I'll be happy when the improvements to Windows console infrastructure start landing, but I'm fine with that conclusion for now. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1075) command : commands fail if in a remote session to Windows
Title: Message Title Michael Smith commented on BOLT-1075 Re: command : commands fail if in a remote session to Windows Also yes, I'd suggest running Bolt locally and using its ability to connect via winrm, or using -n local:// to run truly run the command locally if you've already connected via a remote powershell session. 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-1075) command : commands fail if in a remote session to Windows
Title: Message Title Michael Smith commented on BOLT-1075 Re: command : commands fail if in a remote session to Windows I searched a bit longer for better workarounds, but https://stackoverflow.com/a/21466434/2048059 suggests there aren't any. 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-1075) command : commands fail if in a remote session to Windows
Title: Message Title Michael Smith commented on BOLT-1075 Re: command : commands fail if in a remote session to Windows You can use an inventory file or bolt.yaml to provide the password. We don't have password-less login on Windows yet. 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-1075) command : commands fail if in a remote session to Windows
Title: Message Title Michael Smith commented on BOLT-1075 Re: command : commands fail if in a remote session to Windows Repro steps: Install Bolt Open Powershell Run 'Enter-PSSession localhost' Run 'bolt command run hostname -n localhost -p' 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-1075) command : commands fail if in a remote session to Windows
Title: Message Title William Hurt commented on BOLT-1075 Re: command : commands fail if in a remote session to Windows You could make an argument that the workaround is the use bolts native ability to run these command remotely and not try to remote into a machine and run it 'locally' I guess. I do wonder if this will just magically work properly though if someone tried this in a domain environment where you don't need --no-ssl and --password and --user, which is how 99% of Windows users would do this anyway. 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-1078) Reconcile git commits, JIRA tickets, and versions (Bolt 1.9.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1078 Reconcile git commits, JIRA tickets, and versions (Bolt 1.9.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/01/09 10:06 AM Due Date: 2019/01/10 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-01-10) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=Bolt and fixVersion="Bolt x.y.z"' in JIRA. Add Comment
Jira (BOLT-1079) Kick off release pipeline (Bolt 1.9.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1079 Kick off release pipeline (Bolt 1.9.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/01/09 10:06 AM Due Date: 2019/01/10 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-01-10) With our shiny new automated builds pipeline, all you have to do is Go to https://jenkins-master-prod-1.delivery.puppetlabs.net/view/bolt/job/platform_bolt-vanagon_bolt-release-init_bolt-release/ Click "Build with Parameters" Check the PUBLIC checkbox Enter the version in the NEW_TAG box (x.y.z format) Click build! And make sure the pipeline is green! Add Comment
Jira (BOLT-1081) Docs for bolt release (Bolt 1.9.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1081 Docs for bolt release (Bolt 1.9.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/01/09 10:06 AM Due Date: 2019/01/10 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-01-10) Release notes and docs changes for bolt 1.9.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1080) Update homebrew-puppet (Bolt 1.9.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1080 Update homebrew-puppet (Bolt 1.9.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/01/09 10:06 AM Due Date: 2019/01/10 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-01-10) Until we automate this, you'll also need to update the version and SHA hashes of https://github.com/puppetlabs/homebrew-puppet/blob/master/Casks/puppet-bolt.rb. To do this please Create a fork of the homebrew-puppet repo Create a new branch on that fork Run "rake 'brew:cask[puppet-bolt]'" Verify Casks/puppet-bolt.rb was updated to the correct version Put up a PR to homebrew-puppet and request review Add Comment
Jira (BOLT-1082) Send release announcements (Bolt 1.9.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1082 Send release announcements (Bolt 1.9.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/01/09 10:06 AM Due Date: 2019/01/10 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-01-10) Once docs have finished building (check that all links resolve appropriately) - Create an e-mail announcement with the subject "Bolt 1.9.0 now available". Include a summary of the release and links to the installation instructions and release notes. In the From: field, enter the Google account Puppet Product Updates (puppet-product-upda...@puppet.com). In the Bcc: field, enter the following addresses. Send a separate message to each: internal-puppet-product-upda...@puppet.com, puppet-us...@googlegroups.com, puppet-...@googlegroups.com, and puppet-annou...@googlegroups.com. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. If you want, make a PSA on IRC and/or Slack, something along the lines of "PSA: Bolt 1.9.0 is now available".
Jira (BOLT-1077) Bolt 1.9.0 2019-01-10 Release
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1077 Bolt 1.9.0 2019-01-10 Release Issue Type: Task Assignee: Cas Donoghue Created: 2019/01/09 10:05 AM Priority: Normal Reporter: Cas Donoghue Bolt 1.9.0 2019-01-10 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8319) Win-2012r2 FR Puppet Acceptance showing 4 test failures (localisation)
Title: Message Title John O'Connor updated an issue Puppet / PUP-8319 Win-2012r2 FR Puppet Acceptance showing 4 test failures (localisation) Change By: John O'Connor Sprint: Images Hopper 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-1075) command : commands fail if in a remote session to Windows
Title: Message Title Michael Smith commented on BOLT-1075 Re: command : commands fail if in a remote session to Windows Maybe this is yet another case where Ruby falls over. If you're not using Cygwin or MinGW, I don't see a reason they'd be involved; Bolt doesn't include either. 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-1075) command : commands fail if in a remote session to Windows
Title: Message Title William Hurt commented on BOLT-1075 Re: command : commands fail if in a remote session to Windows It's not clear to me how either of those would be getting dragged into this, but maybe just because I don't know enough about how bolt is working under the hood here. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1075) command : commands fail if in a remote session to Windows
Title: Message Title Michael Smith commented on BOLT-1075 Re: command : commands fail if in a remote session to Windows A similar report at https://github.com/TerribleDev/zanzibar/issues/19 suggests this is an issue with Ruby when Cygwin or MinGW is involved. 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-1075) command : commands fail if in a remote session to Windows
Title: Message Title William Hurt commented on BOLT-1075 Re: command : commands fail if in a remote session to Windows Ok, I see the work around. If I provide the password in the commandline call then it works. The issue seems to be that if you are in a remote session to the computer, the prompt to enter a password doesn't work if you leave the password blank. If you are in a local session the prompt to enter the password works as expected. 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-1075) command : commands fail if in a remote session to Windows
Title: Message Title Michael Smith commented on BOLT-1075 Re: command : commands fail if in a remote session to Windows It looks like you were using Enter-PSSession to connect to another machine, then running Bolt there? 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-1049) Provide better out-of-the-box task experience
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1049 Provide better out-of-the-box task experience Change By: Cas Donoghue Fix Version/s: BOLT Next 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-1075) command : commands fail if in a remote session to Windows
Title: Message Title Michael Smith commented on BOLT-1075 Re: command : commands fail if in a remote session to Windows The error is specifically if you use --password without including the password after, triggering Bolt to prompt you for it. This is identical to BOLT-627. 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-4244) Fix travis homebrew failures (started 2019-09)
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4244 Fix travis homebrew failures (started 2019-09) Change By: Austin Blatt Summary: @Jira Bot create issue Fix travis homebrew failures (started 2019-09) 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-4244) @Jira Bot create issue Fix travis homebrew failures (started 2019-09)
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4244 @Jira Bot create issue Fix travis homebrew failures (started 2019-09) Issue Type: Bug Assignee: Unassigned Created: 2019/01/09 9:46 AM Priority: Normal Reporter: Austin Blatt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this
Jira (FACT-1903) facter doesn't recognize EC2 i3.metal instances
Title: Message Title
Ryan McKern updated an issue
Facter / FACT-1903
facter doesn't recognize EC2 i3.metal instances
Change By:
Ryan McKern
i3.metal instances aren’t {{$virtual}} as far as puppet is concerned, so there is a problem where facter doesn’t populate {{ec2_metadata}} on i3.metal instances as a result. If we force the facter {{virtual}} fact to be kvm, then puppet can run just fine on that instance type.An example of the logic involved in determining if an instance is on EC2 is here:https://github.com/puppetlabs/facter/blob/master/lib/src/facts/resolvers/ec2_resolver.cc#L117 (Credit to [~coneill] for finding this -- I'm just the messenger.)
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to
Jira (FACT-1903) facter doesn't recognize EC2 i3.metal instances
Title: Message Title Ryan McKern created an issue Facter / FACT-1903 facter doesn't recognize EC2 i3.metal instances Issue Type: Bug Assignee: Unassigned Created: 2019/01/09 8:45 AM Environment: AWS EC2, i3.metal instance Debian Jessie or Stretch Labels: aws ec2 Priority: Normal Reporter: Ryan McKern i3.metal instances aren’t $virtual as far as puppet is concerned, so there is a problem where facter doesn’t populate ec2_metadata on i3.metal instances as a result. If we force the facter virtual fact to be kvm, then puppet can run just fine on that instance type. An example of the logic involved in determining if an instance is on EC2 is here: https://github.com/puppetlabs/facter/blob/master/lib/src/facts/resolvers/ec2_resolver.cc#L117 Add Comment
Jira (PUP-9399) Puppet agent 6 ignores srv_domain config
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9399 Puppet agent 6 ignores srv_domain config Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9294) Raise Error when a legacy function illegally defines methods
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9294 Raise Error when a legacy function illegally defines methods Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4205) Upgrade 6.0.x clj-parent to at least 2.4.0
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-4205 Upgrade 6.0.x clj-parent to at least 2.4.0 Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9150) cwd option in Puppet::Util::Execution.execute should work with different Windows path types
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9150 cwd option in Puppet::Util::Execution.execute should work with different Windows path types Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9303) A heredoc with interpolation containing [ ] in the expression can cause syntax error
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9303 A heredoc with interpolation containing [ ] in the _expression_ can cause syntax error Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
