Jira (PUP-8419) Puppet-Run WARNING after upgrading to 5.3.4
Title: Message Title Josh Cooper commented on PUP-8419 Re: Puppet-Run WARNING after upgrading to 5.3.4 This seems to work for me, but need to research more: diff --git a/lib/puppet/configurer.rb b/lib/puppet/configurer.rb index 98ddecdb0b..1feaffd9c9 100644 --- a/lib/puppet/configurer.rb +++ b/lib/puppet/configurer.rb @@ -275,12 +275,6 @@ class Puppet::Configurer :transaction_uuid => @transaction_uuid, :fail_on_404 => true) -# If we have deserialized a node from a rest call, we want to set -# an environment instance as a simple 'remote' environment reference. -if !node.has_environment_instance? && node.environment_name - node.environment = Puppet::Node::Environment.remote(node.environment_name)
Jira (PUP-8432) Remove gettext-setup as a runtime gem dependency
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8432 Remove gettext-setup as a runtime gem dependency Change By: Josh Cooper Fix Version/s: PUP 5.4.0 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8349) SPIKE scheduled_task : should we deprecate scheduled_task resource?
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8349 SPIKE scheduled_task : should we deprecate scheduled_task resource? Change By: Josh Cooper Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.y Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8041) Replace FACTER_url with --target for puppet resource with devices
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8041 Replace FACTER_url with --target for puppet resource with devices Change By: Josh Cooper Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.y Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8394) cache/locales/config.yaml not stable across runs
Title: Message Title Josh Cooper commented on PUP-8394 Re: cache/locales/config.yaml not stable across runs It looks like puppet already excludes config.yaml when making the locales request. While not the perfect solution, I don't think this specific issue is present in the released version of 5.3.4. That said, I think we need to remove *.pot from the default pluginsignore setting, since that applies to all plugin related mounts, and instead add that to the locales specific mount. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-7510) FIPS-Enabled Puppet
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7510 FIPS-Enabled Puppet Change By: Geoff Nichols Team/s: Platform Core ,Platform OS Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-2717) Unable to confine NetworkDevice using facter values
Title: Message Title Justin Stoller updated an issue Puppet / PUP-2717 Unable to confine NetworkDevice using facter values Change By: Justin Stoller Component/s: Server Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1597) "Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug." on AIX
Title: Message Title Halim Wijaya updated an issue Facter / FACT-1597 "Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug." on AIX Change By: Halim Wijaya Priority: Normal Major Running Puppet Enterprise 2017.1.1Previous facter: 3.5.0 (commit 872c5707799c1c30925b632f20eab763ec03b5a4)New facter: 3.6.2 (commit 36e4f036cfab9e283f6b47bd5e3890a4de54c5ff)After upgrading AIX Client with puppet-agent-1.9.3-1.aix7.1.ppc.rpm, new version of facter returns warning below.# facter 2017-03-28 13:10:48.912233 WARN puppetlabs.facter - Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug. Please report it, and include this error message. 2017-03-28 13:10:48.912822 WARN puppetlabs.facter - Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug. Please report it, and include this error message. 2017-03-28 13:10:48.913030 WARN puppetlabs.facter - Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug. Please report it, and include this error message. 2017-03-28 13:10:48.913236 WARN puppetlabs.facter - Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug. Please report it, and include this error message. 2017-03-28 13:10:48.913441 WARN puppetlabs.facter - Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug. Please report it, and include this error message. 2017-03-28 13:10:48.914954 WARN puppetlabs.facter - Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug. Please report it, and include this error message. 2017-03-28 13:10:48.915236 WARN puppetlabs.facter - Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug. Please report it, and include this error message. 2017-03-28 13:10:48.915448 WARN puppetlabs.facter - Expected a Disk or SCSI disk device, got device code ' '. This is probably a Facter bug. Please report it, and include this error message. Add Comment
Jira (PUP-3127) LDAP - introduce LDAP-Certificat Directory
Title: Message Title Justin Stoller updated an issue Puppet / PUP-3127 LDAP - introduce LDAP-Certificat Directory Change By: Justin Stoller Component/s: Server Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-1974) Theme: Sensitive Data in Catalogs
Title: Message Title Justin Stoller updated an issue Puppet / PUP-1974 Theme: Sensitive Data in Catalogs Change By: Justin Stoller Sub-team: Emerald Jade Language emerald jade Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-3834) remove webrick/rack support from Puppet
Title: Message Title Justin Stoller updated an issue Puppet / PUP-3834 remove webrick/rack support from Puppet Change By: Justin Stoller Sub-team: Server Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-7877) Future Work for Intermediate CA Improvements
Title: Message Title Justin Stoller updated an issue Puppet / PUP-7877 Future Work for Intermediate CA Improvements Change By: Justin Stoller Epic Colour: ghx-label- 7 9 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8419) Puppet-Run WARNING after upgrading to 5.3.4
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8419 Puppet-Run WARNING after upgrading to 5.3.4 Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-7537) Agent/Master Separation
Title: Message Title Justin Stoller updated an issue Puppet / PUP-7537 Agent/Master Separation Change By: Justin Stoller Component/s: Puppet Server Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-7877) Future Work for Intermediate CA Improvements
Title: Message Title Justin Stoller updated an issue Puppet / PUP-7877 Future Work for Intermediate CA Improvements Change By: Justin Stoller Sub-team: Server Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8423) FIPS-Enabled Puppet Server Side
Title: Message Title Justin Stoller updated an issue Puppet / PUP-8423 FIPS-Enabled Puppet Server Side Change By: Justin Stoller Component/s: Puppet Server Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-4885) Master and Agent should not share libdir
Title: Message Title Justin Stoller updated an issue Puppet / PUP-4885 Master and Agent should not share libdir Change By: Justin Stoller Sub-team: Emerald Jade emerald jade Server Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-7564) augeas fixes
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7564 augeas fixes Change By: Geoff Nichols Team/s: Platform OS Core Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-7266) SPIKE: Master and Agent should not share a libdir
Title: Message Title Justin Stoller updated an issue Puppet / PUP-7266 SPIKE: Master and Agent should not share a libdir Change By: Justin Stoller Sub-team: Server Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8419) Puppet-Run WARNING after upgrading to 5.3.4
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8419 Puppet-Run WARNING after upgrading to 5.3.4 Change By: Josh Cooper Fix Version/s: PUP 5.3.5 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8419) Puppet-Run WARNING after upgrading to 5.3.4
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8419 Puppet-Run WARNING after upgrading to 5.3.4 Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8419) Puppet-Run WARNING after upgrading to 5.3.4
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8419 Puppet-Run WARNING after upgrading to 5.3.4 Change By: Josh Cooper Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8419) Puppet-Run WARNING after upgrading to 5.3.4
Title: Message Title Josh Cooper commented on PUP-8419 Re: Puppet-Run WARNING after upgrading to 5.3.4 Ok I can reproduce: $ git checkout 5.3.3 $ bundle exec puppet agent -t --environment foobar Info: Using configured environment 'foobar' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Caching catalog for localhost Info: Applying configuration version '1517981703' Notice: hello Notice: /Stage[main]/Main/Notify[hello]/message: defined 'message' as 'hello' Notice: Applied catalog in 0.02 seconds $ git checkout 5.3.4 $ bundle exec bx puppet agent -t --environment foobar Warning: Unable to fetch my node definition, but the agent run will continue:
Jira (PUP-1829) Define PCore - the Puppet Meta Meta Model
Title: Message Title Justin Stoller updated an issue Puppet / PUP-1829 Define PCore - the Puppet Meta Meta Model Change By: Justin Stoller Component/s: Server Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8419) Puppet-Run WARNING after upgrading to 5.3.4
Title: Message Title Ben Hines commented on PUP-8419 Re: Puppet-Run WARNING after upgrading to 5.3.4 Josh Cooper same issue here: 'puppet agent -t --trace' does not add a stacktrace or any additional output than has been included above. (perhaps because it's a warning rather than error?) Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8393) Standard Array conversions do not work on return value from tree_each function
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8393 Standard Array conversions do not work on return value from tree_each function Change By: Josh Cooper Fix Version/s: PUP 5.3.z Fix Version/s: PUP 5.3.5 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8267) Rewrite acceptance rake tasks to leverage beaker subcommand support
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8267 Rewrite acceptance rake tasks to leverage beaker subcommand support Change By: Josh Cooper Fix Version/s: PUP 4.10.z Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.3.5 Fix Version/s: PUP 4.10.11 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-7349) resource type tidy does not honor metaparameter noop
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7349 resource type tidy does not honor metaparameter noop Change By: Josh Cooper Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.3.5 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8412) In the puppet report, provide details of which provider was used for each resource
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8412 In the puppet report, provide details of which provider was used for each resource Change By: Josh Cooper Sub-team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8412) In the puppet report, provide details of which provider was used for each resource
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8412 In the puppet report, provide details of which provider was used for each resource Change By: Josh Cooper Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency
Title: Message Title Josh Cooper commented on PUP-6964 Re: Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency Revert merged to master in https://github.com/puppetlabs/puppet/commit/3d6023bde9a55081e57ddaec35c4db5e01ec0f87. Removing 5.4.0 fix version. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6964 Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency Change By: Josh Cooper Sub-team: Language Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-6964) Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6964 Puppet 4.x functions should be available to all modules not just those that declare the containing module as a dependency Change By: Josh Cooper Fix Version/s: PUP 5.4.0 Fix Version/s: PUP 5.y Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8433) PXP fails to start after a Puppet Agent upgrade with SSL library errors
Title: Message Title Glenn Sarti commented on PUP-8433 Re: PXP fails to start after a Puppet Agent upgrade with SSL library errors I don't think https://puppetlabs.zendesk.com/agent/tickets/26386 is relevant for this ticket Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8433) PXP fails to start after a Puppet Agent upgrade with SSL library errors
Title: Message Title Glenn Sarti commented on PUP-8433 Re: PXP fails to start after a Puppet Agent upgrade with SSL library errors Repro'd the issue. Some steps may not be required but it's how I did it. Spin up a Puppet Master and Windows 2012R2 client. Fully connect them and ensure the "Run Puppet" functionality is working (Use your own tools for this. For my repro I used the Learning VM from SLICE and a Windows 2012R2 client with the Puppet 5.3.1 x64 Agent Stop the PXP-Agent Service copy the C:\Windows\System32\lltdapi.dll to C:\Windows\System32\libeay32.dll (This is basically using a valid DLL file but it does not have the same functions exported etc. so it should break if used) Start the PXP-Agent Service It Should error and then NSSM will put the service into a Pause state Delete the "bad" C:\Windows\System32\libeay32.dll file and restart the PXP agent service and it will run correctly. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-8433) PXP fails to start after a Puppet Agent upgrade with SSL library errors
Title: Message Title Glenn Sarti commented on PUP-8433 Re: PXP fails to start after a Puppet Agent upgrade with SSL library errors Interesting - https://community.ivanti.com/docs/DOC-61035 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1814) Mountpoints Fact available space does not accurately reflect disk usage
Title: Message Title Branan Riley commented on FACT-1814 Re: Mountpoints Fact available space does not accurately reflect disk usage Agreed this could be a breaking change - but that can be said for every fact change. We sort of have to evaluate the risk on a case-by-case basis. In this situation I think this might be worth going for. I'm not entirely sure what the reasons for choosing f_bfree instead of f_bavail were, and I suspect that f_bavail is more correct in more cases, since most files written on a node are gonna be owned by not-root (one hopes, anyway). I don't have as much insight into how customers use this fact as folks in CS do, though - I very much value your input in evaluating the risk of changing things here. Worst case, we're coming up on Platform 6 and could schedule this for Facter 4. We should at the very least fix Facter to not use the deprecated API (as long as the not-deprecated version is available on all the kernel/libc versions we care about). That sounds like it's probably a different ticket, though. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8419) Puppet-Run WARNING after upgrading to 5.3.4
Title: Message Title Josh Cooper commented on PUP-8419 Re: Puppet-Run WARNING after upgrading to 5.3.4 Thanks Ellison Marks makes sense. Can you provide the output of puppet agent -t --trace? Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8432) Remove gettext-setup as a runtime gem dependency
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8432 Remove gettext-setup as a runtime gem dependency Change By: Josh Cooper Fix Version/s: PUP 4.10.11 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8433) PXP fails to start after a Puppet Agent upgrade with SSL library errors
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-8433 PXP fails to start after a Puppet Agent upgrade with SSL library errors Change By: Glenn Sarti This issue was created from PUP-6702 --- — Steps to reproduce;Unknown at this stage. Looks like it could be made to happen after the puppet_agent module does an agent upgrade. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-6702) Windows service in Paused state cannot be managed
Title: Message Title Glenn Sarti commented on PUP-6702 Re: Windows service in Paused state cannot be managed Created PUP-8433 for the DLL issue. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8433) PXP fails to start after a Puppet Agent upgrade with SSL library errors
Title: Message Title
Glenn Sarti updated an issue
Puppet / PUP-8433
PXP fails to start after a Puppet Agent upgrade with SSL library errors
Change By:
Glenn Sarti
When a service is in the Paused state; it's 'ensure' property cannot be managed by Puppet Note that for our own services that use nssm; nssm has a characteristic that it uses the "Paused" service state for a service that has reached a fault state (see https://nssm.cc/usage )*To reproduce:* * Install puppet-agent * Ensure pxp-agent service is stopped in services.msc * Ensure the ProgramData/PuppetLabs/pxp-agent/etc/pxp-agent.conf file is renamed or deleted * Run _puppet resource service pxp-agent ensure=running_The service will now be in the paused state. Attempting _puppet resource service pxp-agent ensure=stopped_ will echo back ensure=stopped , but services.msc will show the service as still paused. Attempting _puppet resource service pxp-agent ensure=running_ will return an error:{noformat}C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Puppet>puppet resource service pxp-agent ensure=runningError: Cannot start pxp-agent, error This issue was : Execution of 'C:/Windows/system32/net.exe start pxp created from PUP - agent' returned 2: The requested service has already been started. 6702 More help is available by typing NET HELPMSG 2182.Wrapped exception:Execution of 'C:/Windows/system32/net.exe start pxp - agent' returned 2: The requested service has already been started.More help is available by typing NET HELPMSG 2182.Error: /Service[pxp - agent]/ensure: change from stopped to running failed: Cannot start pxp - agent, error was: Execution of 'C:/Windows/system32/net.exe start pxp -agent' returned 2: The requested service has already been started. More help is available by typing NET HELPMSG 2182.{noformat}Outside of Puppet, the service can be stopped by simply using the Stop option in services.msc*Expected behaviour:* * The "Paused" state should be understood by Puppet for a Windows service resource. Or at least; Puppet should actually stop a service in the "Paused" state when ensure=stopped is applied.
Add Comment
Jira (PUP-8433) PXP fails to start after a Puppet Agent upgrade with SSL library errors
Title: Message Title James Stocks created an issue Puppet / PUP-8433 PXP fails to start after a Puppet Agent upgrade with SSL library errors Issue Type: Bug Affects Versions: PUP 4.10.4 Assignee: Glenn Sarti Attachments: screenshot-1.png Components: Windows Created: 2018/02/06 5:46 PM Environment: TEST_TARGET=windows2008r2-64a SUITE_VERSION=1.6.2.135.g8a48f21 SUITE_COMMIT=8a48f210f6901be0edba16eb49c1bfbfb07d338b Labels: manage-service Priority: Major Reporter: James Stocks When a service is in the Paused state; it's 'ensure' property cannot be managed by Puppet Note that for our own services that use nssm; nssm has a characteristic that it uses the "Paused" service state for a service that has reached a fault state (see https://nssm.cc/usage ) To reproduce: Install puppet-agent Ensure pxp-agent service is stopped in services.msc Ensure the ProgramData/PuppetLabs/pxp-agent/etc/pxp-agent.conf file is renamed or deleted
Jira (PUP-8432) Remove gettext-setup as a runtime gem dependency
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8432 Remove gettext-setup as a runtime gem dependency Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8432) Remove gettext-setup as a runtime gem dependency
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8432 Remove gettext-setup as a runtime gem dependency Change By: Josh Cooper Acceptance Criteria: If you build puppet as a gem and install it on a clean VM, gettext-setup should not be instaslled installed as a dependency. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8432) Remove gettext-setup as a runtime gem dependency
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-8432 Remove gettext-setup as a runtime gem dependency Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8418) TypeError no implicit conversion of nil into String in puppet 5.3.4
<<< text/html; charset="UTF-8": Unrecognized >>>
Jira (PUP-8432) Remove gettext-setup as a runtime gem dependency
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8432 Remove gettext-setup as a runtime gem dependency Change By: Josh Cooper Fix Version/s: PUP 5.3.5 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8432) Remove gettext-setup as a runtime gem dependency
Title: Message Title Josh Cooper commented on PUP-8432 Re: Remove gettext-setup as a runtime gem dependency /cc Maggie Dreyer, Eric Putnam Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8231) Group resource - unable to add new member if there is existing IIS AppPool\user
Title: Message Title Ethan Brown commented on PUP-8231 Re: Group resource - unable to add new member if there is existing IIS AppPool\user The error is being raised from https://github.com/puppetlabs/puppet/blob/3a5dfed0fef8fc5cb1b6ec168766115de3e8f23b/lib/puppet/util/windows/adsi.rb#L156 I'm a little confused why this would resolve the first time, but not the second. Have you run just the first manifest in isolation (outside of any other resource management with IIS for instance)? What happens when you run puppet resource group after the manifest runs for the first time? What happens if you run the same manifest again without modification? Does it error then? The addition of admnistrator seems to be a red herring, so I'd like to get a better understanding of what is actually happening in the systems environment. Thanks! Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8230) Puppet Platform Release Process Improvements
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8230 Puppet Platform Release Process Improvements Change By: Geoff Nichols Team/s: Data Platform,Platform Core, Platform OS, Release Engineering Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8432) Remove gettext-setup as a runtime gem dependency
Title: Message Title Josh Cooper created an issue Puppet / PUP-8432 Remove gettext-setup as a runtime gem dependency Issue Type: Bug Assignee: Unassigned Created: 2018/02/06 5:25 PM Priority: Normal Reporter: Josh Cooper Puppet version: 5.3.4 We meant to remove gettext-setup as a puppet runtime dependency, but we store gem dependencies in 3 different places for different use cases, so it was missed. See https://github.com/puppetlabs/puppet/commit/53aa50aaf6347ac166620f08224d072552e57dc3#diff-8b7db4d5cc4b8f6dc8feb7030baa2478. This is a problem because it increases the chances of running into PUP-8418 (if gettext-setup is ever required). Add Comment This message was sent by Atlassian JIRA
Jira (PUP-8422) warning messages while puppet agent running on nodes.
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8422 warning messages while puppet agent running on nodes. Change By: Josh Cooper Fix Version/s: None Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8422) warning messages while puppet agent running on nodes.
Title: Message Title Josh Cooper commented on PUP-8422 Re: warning messages while puppet agent running on nodes. We need more information to go on. Closing this ticket. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8378) Intercept use of any prohibited algorithms/operations in FIPS mode to provide graceful error messages
Title: Message Title Josh Cooper commented on PUP-8378 Re: Intercept use of any prohibited algorithms/operations in FIPS mode to provide graceful error messages Merged to master in https://github.com/puppetlabs/puppet/commit/5e35d043ae0458e38a0aa3cf749113b0b8e5433b Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-316) Orchestrator transport should batch run_* commands
Title: Message Title Nick Lewis assigned an issue to Nick Lewis Puppet Task Runner / BOLT-316 Orchestrator transport should batch run_* commands Change By: Nick Lewis Assignee: Nick Lewis Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8419) Puppet-Run WARNING after upgrading to 5.3.4
Title: Message Title Ellison Marks commented on PUP-8419 Re: Puppet-Run WARNING after upgrading to 5.3.4 Permissions are correct, yes, though I think I wasn't clear. The error message does not occur on the master server, either in any logs or when running puppet agent --test. The error message only occurs when running puppet agent --test on a client machine. The client machines do not have the directory environments installed on them and never have, the master does have the directory environments. Regardless of the warning, the run proceeds as normal with all appropriate classes applied as verified with --debug. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-6702) Windows service in Paused state cannot be managed
Title: Message Title Craig Gomes assigned an issue to Glenn Sarti Puppet / PUP-6702 Windows service in Paused state cannot be managed Change By: Craig Gomes Assignee: Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8419) Puppet-Run WARNING after upgrading to 5.3.4
Title: Message Title Josh Cooper commented on PUP-8419 Re: Puppet-Run WARNING after upgrading to 5.3.4 Ellison Marks Can you verify that the puppet user has the correct permissions on all ancestor directories of $codedir? Are you seeing the same error message on the agent? Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-326) Bolt --run-as fails when sudo lecture is printed
Title: Message Title Nick Lewis commented on BOLT-326 Re: Bolt --run-as fails when sudo lecture is printed This can be easily reproduced by creating a file /etc/sudoers.d/privacy with content Defaults lecture = always Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-326) Bolt --run-as fails when sudo lecture is printed
Title: Message Title
Reid Vandewiele updated an issue
Puppet Task Runner / BOLT-326
Bolt --run-as fails when sudo lecture is printed
Change By:
Reid Vandewiele
Bolt will fail when running with {{--run-as}} if sudo prints a lecture. For example:{code}bolt command run "/opt/puppetlabs/bin/puppet agent -t --noop" -n @node --run-as root --sudo-password -c 50{code}Might fail with output such as the following:{code} Failed on ip-10-12-233-161. va2 example . b2c.nike. com: The command failed with exit code 1 STDERR:We trust you have received the usual lecture from the local SystemAdministrator. It usually boils down to these three things:#1) Respect the privacy of others.#2) Think before you type.#3) With great power comes great responsibility.[sudo] Bolt needs to run as another user, password: {code}It might have something to do with this comparison: https://github.com/puppetlabs/bolt/blob/bc7a9577471de0b8398d3c99602aad242a171331/lib/bolt/node/ssh.rb#L138Sudo sometimes or always prints a "lecture" when invoked. It seems that when it does, Bolt will fail.
Add Comment
This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (BOLT-326) Bolt --run-as fails when sudo lecture is printed
Title: Message Title Reid Vandewiele created an issue Puppet Task Runner / BOLT-326 Bolt --run-as fails when sudo lecture is printed Issue Type: Bug Assignee: Unassigned Created: 2018/02/06 3:44 PM Priority: Normal Reporter: Reid Vandewiele Bolt will fail when running with --run-as if sudo prints a lecture. For example: bolt command run "/opt/puppetlabs/bin/puppet agent -t --noop" -n @node --run-as root --sudo-password -c 50 Might fail with output such as the following: Failed on ip-10-12-233-161.va2.b2c.nike.com: The command failed with exit code 1 STDERR:
Jira (PDB-3835) Bump versions, push directly, and tag (PuppetDB 5.2.0)
Title: Message Title Molly Waggett created an issue PuppetDB / PDB-3835 Bump versions, push directly, and tag (PuppetDB 5.2.0) Issue Type: Task Assignee: russ Created: 2018/02/06 3:23 PM Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2018-02-13) (if you're making the first release off a new branch you may already have done some of this) Remove the -SNASPHOT portion of the verison in project.clj in both puppetdb and pe-puppetdb-extensions. Push each repo directly to the branch you're releasing (making a PR will break things horribly) Go into the 'release-new' hipchat room to make yourself some tags ! tag puppetdb at with ! tag pe-puppetdb-extensions at with Add Comment
Jira (PDB-3837) Update winston (PuppetDB 5.2.0)
Title: Message Title Molly Waggett created an issue PuppetDB / PDB-3837 Update winston (PuppetDB 5.2.0) Issue Type: Task Assignee: russ Created: 2018/02/06 3:23 PM Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2018-02-13) Update https://github.com/puppetlabs/winston/blob/master/lib/tickets/puppetdb.rb to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PDB-3836) Check builds, promote to PE (PuppetDB 5.2.0)
Title: Message Title Molly Waggett created an issue PuppetDB / PDB-3836 Check builds, promote to PE (PuppetDB 5.2.0) Issue Type: Task Assignee: russ Created: 2018/02/06 3:23 PM Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2018-02-13) 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. Add Comment
Jira (PDB-3834) Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.0)
Title: Message Title Molly Waggett created an issue PuppetDB / PDB-3834 Reconcile git commits, JIRA tickets, and versions (PuppetDB 5.2.0) Issue Type: Task Assignee: russ Created: 2018/02/06 3:23 PM Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2018-02-13) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Add Comment This message was sent by Atlassian JIRA
Jira (PUP-8419) Puppet-Run WARNING after upgrading to 5.3.4
Title: Message Title Ellison Marks commented on PUP-8419 Re: Puppet-Run WARNING after upgrading to 5.3.4 Getting the same thing, though our codedir is in the default location, so the directory that it says it can't find definitely exists on the master. Not on the agent though. puppetserver has been restarted, and trace shows nothing extra. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-3833) Merge-up, branch, and create pipelines (PuppetDB 5.2.0)
Title: Message Title
Molly Waggett created an issue
PuppetDB / PDB-3833
Merge-up, branch, and create pipelines (PuppetDB 5.2.0)
Issue Type:
Task
Assignee:
russ
Created:
2018/02/06 3:22 PM
Priority:
Normal
Reporter:
Molly Waggett
(Initial planned release date: 2018-02-13) Is the code ready for release? Check that the latest nightly ("Periodic") build was green.
master: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/master
5.1.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.1.x/
4.4.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/4.4.x/
4.2.3.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/4.2.3.x/
Do merge-ups:
Merge 4.4.x -> 5.1.x
Merge 5.1.x -> master
4.2.3.x is the LTS branch; bugfixes should be backported to it where possible, but it doesn't participate in merge-ups.
Important:
Jira (PUP-8426) Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.4.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-8426 Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.4.0) Issue Type: Task Assignee: Kenn Hussey Created: 2018/02/06 3:21 PM Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2018-02-13) Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8424) Puppet Platform 5.4.0 Release - 2018-02-13
Title: Message Title Molly Waggett created an issue Puppet / PUP-8424 Puppet Platform 5.4.0 Release - 2018-02-13 Issue Type: Epic Assignee: Kenn Hussey Created: 2018/02/06 3:21 PM Due Date: 2018/02/13 Priority: Normal Reporter: Molly Waggett Puppet Platform 5.4.0 Release - 2018-02-13 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8425) Prepare JIRA for release (Puppet Platform 5.4.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-8425 Prepare JIRA for release (Puppet Platform 5.4.0) Issue Type: Task Assignee: Kenn Hussey Created: 2018/02/06 3:21 PM Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2018-02-13) Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8431) Communicate scope and timeline of next release (Puppet Platform 5.4.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-8431 Communicate scope and timeline of next release (Puppet Platform 5.4.0) Issue Type: Task Assignee: Kenn Hussey Created: 2018/02/06 3:22 PM Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2018-02-13) Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8429) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.4.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-8429 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.4.0) Issue Type: Task Assignee: Kenn Hussey Created: 2018/02/06 3:21 PM Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2018-02-13) Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8430) Update Confluence and JIRA based on release (Puppet Platform 5.4.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-8430 Update Confluence and JIRA based on release (Puppet Platform 5.4.0) Issue Type: Task Assignee: Kenn Hussey Created: 2018/02/06 3:21 PM Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2018-02-13) Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8428) Manually smoke test all artifacts (Puppet Platform 5.4.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-8428 Manually smoke test all artifacts (Puppet Platform 5.4.0) Issue Type: Task Assignee: Casey Williams Created: 2018/02/06 3:21 PM Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2018-02-13) Walk through smoke testing all Platform components, installing it from packages as a user would. See https://confluence.puppetlabs.com/display/systemsEngineering/Test+platform+5+package+artifacts+template and https://confluence.puppetlabs.com/display/systemsEngineering/Test+platform+5+repository+template for examples. Add Comment
Jira (PUP-8427) Prepare release announcement (Puppet Platform 5.4.0)
Title: Message Title Molly Waggett created an issue Puppet / PUP-8427 Prepare release announcement (Puppet Platform 5.4.0) Issue Type: Task Assignee: Eric Sorenson Created: 2018/02/06 3:21 PM Labels: release Priority: Normal Reporter: Molly Waggett (Initial planned release date: 2018-02-13) Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574)
Jira (PUP-8420) Regression: puppet apply does not decompress response bodies for http file sources
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8420 Regression: puppet apply does not decompress response bodies for http file sources Change By: Josh Cooper Summary: Regression: puppet apply does not decompress response body bodies for http file sources Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-3820) Destroy release branches, pipelines, and update winston (PuppetDB 5.1.4)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3820 Destroy release branches, pipelines, and update winston (PuppetDB 5.1.4) Change By: Russell Mull Fix Version/s: PDB 5.1.4 Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-3820) Destroy release branches, pipelines, and update winston (PuppetDB 5.1.4)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3820 Destroy release branches, pipelines, and update winston (PuppetDB 5.1.4) Change By: Russell Mull Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1783) processors['count'] wrong for LXC containers
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1783 processors['count'] wrong for LXC containers Change By: Geoff Nichols Sprint: Platform OS Grooming/Triage Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1772) libfacter install should support other directories than /lib
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1772 libfacter install should support other directories than /lib Change By: Geoff Nichols Sprint: Platform OS Grooming/Triage Ready for Eng. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1769) Ruby API for command execution with status code in result
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1769 Ruby API for command execution with status code in result Change By: Geoff Nichols Sprint: Platform OS Grooming/Triage Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1768) libwhereami uses deprecated syntax
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1768 libwhereami uses deprecated syntax Change By: Geoff Nichols Sprint: Platform OS Grooming/Triage Ready for Eng. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1768) libwhereami uses deprecated syntax
Title: Message Title Geoff Nichols assigned an issue to Casey Williams Facter / FACT-1768 libwhereami uses deprecated syntax Change By: Geoff Nichols Assignee: Casey Williams Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-5334) Puppet can't remove users from groups in OSX.
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-5334 Puppet can't remove users from groups in OSX. Change By: Geoff Nichols Sprint: Platform OS Grooming/Triage Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1761) Infiniband's mac (hardware) address not provided
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1761 Infiniband's mac (hardware) address not provided Change By: Geoff Nichols Sprint: Platform OS Grooming/Triage Community PR Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8089) Pluginsync locale files
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8089 Pluginsync locale files Change By: Maggie Dreyer Release Notes Summary: During pluginsync, the agent will now download module translation files along with the rest of the module data. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8090) Load module translation files
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8090 Load module translation files Change By: Maggie Dreyer Release Notes Summary: Puppet will now correctly load module translations on both the agent and the server. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-6504) Targeted Filebucket Improvements
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6504 Targeted Filebucket Improvements Change By: Josh Cooper Release Notes Summary: A collection of bug fixes to puppet's filebucket functionality. Includes documentation updates, fixing the "--local" option, and ensuring files are written to the filebucket atomically. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1814) Mountpoints Fact available space does not accurately reflect disk usage
Title: Message Title Scott McClellan updated an issue Facter / FACT-1814 Mountpoints Fact available space does not accurately reflect disk usage Change By: Scott McClellan Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1808) Incorrectly detects OS in docker container
Title: Message Title Branan Riley commented on FACT-1808 Re: Incorrectly detects OS in docker container We currently rely on the lsb-release package (specifically the lsb_release command) to identify various Debian derivatives. Probably we need to switch to the os-release file, since that appears to have filtered into most modern versions of various distros at this point. For now, you should be able to install the lsb-release package in your container images to get Facter to behave correctly. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1808) Incorrectly detects OS in docker container
Title: Message Title Branan Riley updated an issue Facter / FACT-1808 Incorrectly detects OS in docker container Change By: Branan Riley Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8423) FIPS-Enabled Puppet Server Side
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8423 FIPS-Enabled Puppet Server Side Change By: Josh Cooper Fix Version/s: PUP 5.y Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1813) Windows virtual machines on QEMU/KVM servers not detected as virtual
Title: Message Title Scott McClellan assigned an issue to Casey Williams Facter / FACT-1813 Windows virtual machines on QEMU/KVM servers not detected as virtual Change By: Scott McClellan Assignee: Casey Williams Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8423) FIPS-Enabled Puppet Server Side
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8423 FIPS-Enabled Puppet Server Side Change By: Josh Cooper Team/s: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1813) Windows virtual machines on QEMU/KVM servers not detected as virtual
Title: Message Title Scott McClellan updated an issue Facter / FACT-1813 Windows virtual machines on QEMU/KVM servers not detected as virtual Change By: Scott McClellan Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-7510) FIPS-Enabled Puppet
Title: Message Title Josh Cooper commented on PUP-7510 Re: FIPS-Enabled Puppet FYI, I moved all of the server-side tickets to PUP-8423 as we're getting close to wrapping up 5.4.0 with the necessary puppet-agent changes. Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-7510) FIPS-Enabled Puppet
Title: Message Title Trevor Vaughan commented on PUP-7510 Re: FIPS-Enabled Puppet Jayant Sane It's awesome that this is almost done. Is there an ETA at this point? Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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-8423) FIPS-Enabled Puppet Server Side
Title: Message Title Josh Cooper created an issue Puppet / PUP-8423 FIPS-Enabled Puppet Server Side Issue Type: Epic Assignee: Unassigned Created: 2018/02/06 2:19 PM Priority: Normal Reporter: Josh Cooper The problem is that customers using our Puppet and Puppet Enterprise packages cannot meet the FIPS 140-2 requirements because we roll our own OpenSSL and do not link against the OpenSSL provided with RHEL. This causes them to fail "FISMA High" compliance standards. This epic is the place to gather the stream of work required to remediate this issue, although some implications (such as for puppet-server) will require tickets outside the PUP jira project. See also PUP-7510 for FIPS-Enabled Puppet Agent Add Comment
Jira (PUP-7510) FIPS-Enabled Puppet
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7510 FIPS-Enabled Puppet Change By: Josh Cooper Release Notes Summary: We are adding a new puppet-agent package intended to be deployed on FIPS enabled hosts. The new package is linked against system OpenSSL instead of the vendored version in the puppet-agent package. On FIPS enabled hosts, puppet will not use MD5 for file checksums or digital signature algorithms, and will gracefully error if configured to use MD5, e.g. Puppet[:digest_algorithm] = 'md5'. This only affect the puppet-agent package. Future releases will provide FIPS compliance for puppetserver and CA. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v7.5.1#75006-sha1:7df2574) -- You received this message because you are subscribed to the Google Groups "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
