Jira (PUP-7528) Add Ruby 2.4 builds to puppet-win32-ruby to support ci:test:git workflows
Title: Message Title Ethan Brown created an issue Puppet / PUP-7528 Add Ruby 2.4 builds to puppet-win32-ruby to support ci:test:git workflows Issue Type: Task Assignee: Unassigned Created: 2017/05/12 10:56 PM Fix Versions: PUP 5.0.0 Priority: Normal Reporter: Ethan Brown 32-bit and 64-bit builds of Ruby 2.4.1 should be added to puppet-win32-ruby, and pre-suite setup steps should be updated at https://github.com/puppetlabs/puppet/blob/master/acceptance/setup/git/pre-suite/000_EnvSetup.rb#L109-L113 Add Comment
Jira (PUP-7527) Insufficient error message when erroneously passing a Collection containing non-Data values for a Data parameter
Title: Message Title
Ryan Whitehurst created an issue
Puppet / PUP-7527
Insufficient error message when erroneously passing a Collection containing non-Data values for a Data parameter
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/05/12 10:42 PM
Priority:
Normal
Reporter:
Ryan Whitehurst
Sample code:
function foo (
Data $var,
) {
notice($var)
}
Jira (PDB-3515) Clean up orphaned edges
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3515 Clean up orphaned edges Issue Type: Bug Assignee: Unassigned Created: 2017/05/12 7:03 PM Priority: Normal Reporter: Rob Browning If this is what it looks like (not deleting edges when a node is purged), then we'll probably want to make sure to call delete-edges! during purge, and add a migration to handle existing orphans. We'll also want to add a test to make sure that the addition and deletion of a set of nodes leaves no trace (perhaps via dump, or via "all table" traversal). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-1542) Puppet::Util::Log requires a message
Title: Message Title Russell Mull commented on PUP-1542 Re: Puppet::Util::Log requires a message Was just reading some of this code with Rob Browning. It looks like there must be an exception being thrown in ResourceHarness.sync_if_needed, sometime after the event object was created but before its status was set. Then, if that exception manages to have a nil message, the Puppet.log_exception(detail) will throw an exception. Then the ensure block happens, which records the event which doesn't yet have a status. Finally, the logger exception bubbles up to the rescue block in ResourceHarness.evaluate, which writes down the "requires a message" text into a newly created event via "failed_because". Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7383) Puppet with openssl 1.1 fails
Title: Message Title Tim Meusel commented on PUP-7383 Re: Puppet with openssl 1.1 fails Hi, this is a really annoying bug, I can't develop on Arch Linux without monkey patching the monkey patch. Can we do something to get this fixed sooner than later? The Arch Linux packages are fixed, but the gem version of puppet doesn't work out of the box Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-6675) Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-6675 Puppet::Util::Execution.execute 'hostname' returns nothing as daemon Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-6675) Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Title: Message Title Michael Smith commented on PUP-6675 Re: Puppet::Util::Execution.execute 'hostname' returns nothing as daemon Failed on Solaris in https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/ticket_2455_on_solaris_init_provider_should_start_service_in_own_smf_contract.rb. For some reason reader.eof? doesn't return when executing /usr/bin/ctrun as part of starting an init script. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-1627) Facter should just use oslevel for AIX kernel release
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Facter / FACT-1627 Facter should just use oslevel for AIX kernel release Change By: Maggie Dreyer Assignee: Branan Riley Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-1627) Facter should just use oslevel for AIX kernel release
Title: Message Title Maggie Dreyer commented on FACT-1627 Re: Facter should just use oslevel for AIX kernel release Merged to stable at https://github.com/puppetlabs/facter/commit/00b89e79d7565762897f2705247c3c72f815c547 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-3489) Match pdb version of clj-parent in pdbext (and update both to 0.8.0)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3489 Match pdb version of clj-parent in pdbext (and update both to 0.8.0) Change By: Russell Mull Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-3506) Install openjdk8 on jessie acceptance test hosts
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3506 Install openjdk8 on jessie acceptance test hosts Change By: Russell Mull Fix Version/s: PDB 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-3461) Update PG clients on Jenkins test machines
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3461 Update PG clients on Jenkins test machines Change By: Russell Mull Fix Version/s: PDB 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-3489) Match pdb version of clj-parent in pdbext (and update both to 0.8.0)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3489 Match pdb version of clj-parent in pdbext (and update both to 0.8.0) Change By: Russell Mull Fix Version/s: PDB 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-3491) Remove platforms obsoleted by move to JDK8 from acceptance tests
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3491 Remove platforms obsoleted by move to JDK8 from acceptance tests Change By: Russell Mull Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-3461) Update PG clients on Jenkins test machines
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3461 Update PG clients on Jenkins test machines Change By: Russell Mull Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-3503) Add jruby dev dep; puppetserver no longer includes it
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3503 Add jruby dev dep; puppetserver no longer includes it Change By: Russell Mull Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-3498) Fix rspec resource-related failures wrt puppet master
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3498 Fix rspec resource-related failures wrt puppet master Change By: Russell Mull Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-3505) (maint) Use a real scope object for terminus testing
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3505 (maint) Use a real scope object for terminus testing Change By: Russell Mull Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-3506) Install openjdk8 on jessie acceptance test hosts
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3506 Install openjdk8 on jessie acceptance test hosts Change By: Russell Mull Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-3488) Update to tk-jetty9 (2.0)
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3488 Update to tk-jetty9 (2.0) Change By: Russell Mull Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7525) Move Hocon gem from development dependency in Gemfile to runtime .gemspec dependency
Title: Message Title Ethan Brown commented on PUP-7525 Re: Move Hocon gem from development dependency in Gemfile to runtime .gemspec dependency A question raised on the PR is ... as a result of including hocon in all circumstances - do we need the hocon feature / guards anymore? See: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/feature/hocon.rb#L3 https://github.com/puppetlabs/puppet/blob/master/lib/puppet/functions/hocon_data.rb#L4-L6 I suggest we do a follow-up PR with that change if we deem it necessary, and stick with just the inclusion of Hocon in .gemspec for now. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-4080) support S3 URL as the file type 'source'
Title: Message Title Jeff Adams commented on PUP-4080 Re: support S3 URL as the file type 'source' This would help us out a lot as well. We're masterless, so we're storing secrets in S3. Use case is to specify the file resource source via hiera, using local puppet urls for local development/testing (secrets that aren't really secret and for systems that may not have access to S3), s3 urls for ci/uat/production (for the real secrets, and systems that can access S3) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-6675) Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Title: Message Title
Michael Smith updated an issue
Puppet / PUP-6675
Puppet::Util::Execution.execute 'hostname' returns nothing as daemon
Change By:
Michael Smith
Release Notes Summary:
An issue where some commands run via {{exec}} or in providers would be prevented from running by selinux - because Puppet would redirect their output to a file in /tmp - should be addressed. Puppet now uses a pipe to get stdout from the executed process. This has one known side effect: on Windows if a Puppet agent run is killed, a new agent run will be prevented from starting by Puppet's lockfile until any subprocesses started by the previous agent run have completed.
Release Notes:
Bug Fix
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "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-7383) Puppet with openssl 1.1 fails
Title: Message Title Shawn Bohrer commented on PUP-7383 Re: Puppet with openssl 1.1 fails I'm running into this on Fedora 26 and based on the description above the following fixes the problem for me: --- /tmp/monkey_patches.rb 2017-05-12 14:19:07.438741496 -0500 +++ /usr/share/ruby/vendor_ruby/puppet/util/monkey_patches.rb 2017-05-11 13:04:41.510885324 -0500 @@ -101,7 +101,9 @@ else DEFAULT_PARAMS[:options] = OpenSSL::SSL::OP_NO_SSLv2 | OpenSSL::SSL::OP_NO_SSLv3 end - DEFAULT_PARAMS[:ciphers] << ':!SSLv2' + if DEFAULT_PARAMS[:ciphers] +DEFAULT_PARAMS[:ciphers] << ':!SSLv2' + end
Jira (PUP-7497) puppet resource package command fails to list all packages
Title: Message Title Thomas Kishel updated an issue Puppet / PUP-7497 puppet resource package command fails to list all packages Change By: Thomas Kishel Labels: discovery Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7497) puppet resource package command fails to list all packages
Title: Message Title
Thomas Kishel updated an issue
Puppet / PUP-7497
puppet resource package command fails to list all packages
Change By:
Thomas Kishel
h4. Issue:h4. The {{puppet resource package}} command used to list packages de-duplicates identically named resources managed by multiple providers.This results in an incomplete list of installed packages , including in the Package Inspector feature released in Puppet Enterprise 2017 . 2. h4. Test:h4. {code}# SYSTEM RUBY[root@pe-20172nightly-master ~]# gem list*** LOCAL GEMS ***geocoder (1.4.3)trollop (2.0)# PUPPET RUBY[root@pe-2017-master ~]# /opt/puppetlabs/puppet/bin/gem list*** LOCAL GEMS ***geocoder (1.3.3)typhoeus (1.0.2){code}Result:{code}[root@pe-2017-master ~]# puppet resource package --param providerpackage { 'geocoder': ensure => ['1.4.3'], provider => 'gem',}package { 'trollop': ensure => ['2.0'], provider => 'gem',}package { 'typhoeus': ensure => ['1.0.2'], provider => 'puppet_gem',}{code}typhoeus gem is only installed in puppet ruby and is listedtrollop gem is only installed in system ruby and is listedgeocoder gem is installed in puppet and system ruby and only system ruby is listed
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-7497) puppet resource package command fails to list all packages
Title: Message Title Thomas Kishel commented on PUP-7497 Re: puppet resource package command fails to list all packages This issue isn't specific to gem vs puppet_gem providers, it also occurs with gem vs yum providers. [root@pe-201721-master ~]# gem install zip [root@pe-201721-master ~]# gem list | grep zip zip (2.0.2) [root@pe-201721-master ~]# yum install zip [root@pe-201721-master ~]# yum list installed | grep zip zip.x86_64 3.0-11.el7 @base
Jira (PUP-7497) puppet resource package command fails to list all packages
Title: Message Title
Thomas Kishel updated an issue
Puppet / PUP-7497
puppet resource package command fails to list all packages
Change By:
Thomas Kishel
h4. Issue:h4. The {{puppet resource package}} command used to list packages discards de-duplicates identically named resources managed by multiple providers.This results in an inaccurate incomplete list of installed packages.h4. Test:h4. {code}# SYSTEM RUBY[root@pe-20172nightly-master ~]# gem list*** LOCAL GEMS ***geocoder (1.4.3)trollop (2.0)# PUPPET RUBY[root@pe-2017-master ~]# /opt/puppetlabs/puppet/bin/gem list*** LOCAL GEMS ***geocoder (1.3.3)typhoeus (1.0.2){code}Result:{code}[root@pe-2017-master ~]# puppet resource package --param providerpackage { 'geocoder': ensure => ['1.4.3'], provider => 'gem',}package { 'trollop': ensure => ['2.0'], provider => 'gem',}package { 'typhoeus': ensure => ['1.0.2'], provider => 'puppet_gem',}{code}typhoeus gem is only installed in puppet ruby and is listedtrollop gem is only installed in system ruby and is listedgeocoder gem is installed in puppet and system ruby and only system ruby is listed
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "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 (PUP-3552) Use application/json Content-Type/Accepts instead of PSON
Title: Message Title Josh Cooper commented on PUP-3552 Re: Use application/json Content-Type/Accepts instead of PSON Merged to master in https://github.com/puppetlabs/puppet/commit/e5d6a9f Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7526) no pip2 package provider when pip3 is system default
Title: Message Title
Alex Page updated an issue
Puppet / PUP-7526
no pip2 package provider when pip3 is system default
Change By:
Alex Page
If the {{pip}} command on a puppet client points to the {{pip3}} binary (instead of the more typical {{pip2}}), then there is no difference between installing packages with puppet's {{pip}} provider vs. the {{pip3}} provider. Consequently, there isn't a clean way to force using {{pip2}} install Python 2 packages on such a client. To resolve this, I would suggest adding a {{pip2}} package provider.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "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-7526) no pip2 package provider when pip3 is system default
Title: Message Title Alex Page created an issue Puppet / PUP-7526 no pip2 package provider when pip3 is system default Issue Type: Improvement Assignee: Unassigned Created: 2017/05/12 11:48 AM Priority: Minor Reporter: Alex Page If the pip command on a puppet client points to the pip3 binary (instead of the more typical pip2), then there is no difference between installing packages with puppet's pip provider vs. the pip3 provider. Consequently, there isn't a clean way to force using pip2 on such a client. To resolve this, I would suggest adding a pip2 package provider. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-3486) Update jetty_external_root_ca acceptance test to use disabled CA service
Title: Message Title John Duarte updated an issue Puppet / PUP-3486 Update jetty_external_root_ca acceptance test to use disabled CA service Change By: John Duarte Labels: maintenance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-3486) Update jetty_external_root_ca acceptance test to use disabled CA service
Title: Message Title John Duarte updated an issue Puppet / PUP-3486 Update jetty_external_root_ca acceptance test to use disabled CA service Change By: John Duarte Sprint: Agent 2017-05-31 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-3486) Update jetty_external_root_ca acceptance test to use disabled CA service
Title: Message Title John Duarte updated an issue Puppet / PUP-3486 Update jetty_external_root_ca acceptance test to use disabled CA service Change By: John Duarte Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7503) helpful_error_message_when_hostname_not_match_server_certificate test fails with Ruby 2.4
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7503 helpful_error_message_when_hostname_not_match_server_certificate test fails with Ruby 2.4 Change By: Josh Cooper Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-6660) cached catalogs setting not respected when --test is specified
Title: Message Title Josh Cooper commented on PUP-6660 Re: cached catalogs setting not respected when --test is specified Merged to master in github.com/puppetlabs/puppet/commit/7a699df Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7381) Consistently use encode_with for YAML serialization
Title: Message Title Josh Cooper commented on PUP-7381 Re: Consistently use encode_with for YAML serialization My assumption is that what's intended is that the two methods reference the same set of attributes. Yes that is much better way of stating that! However based on some of our recent conversations, I'm thinking we should drop to_yaml_properties methods, so we only have a single implementation, otherwise we'll get out of sync again in the future. But I don't know if we can drop to_yaml_properties? I assume it's only used if we were using Syck or if we were using Psych and the object didn't implement encode_with. Since we only support ruby 1.9.3, I think that is safe to assume, but not entirely sure? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Moses Mendoza assigned an issue to Unassigned Puppet / PUP-7198 Puppet Server uses facts from the previous run (n-1) after agent switches masters Change By: Moses Mendoza Assignee: Moses Mendoza Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-3511) Invalid commands prevent KahaDB GC
Title: Message Title Rob Browning assigned an issue to Russell Mull PuppetDB / PDB-3511 Invalid commands prevent KahaDB GC Change By: Rob Browning Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7198) Puppet Server uses facts from the previous run (n-1) after agent switches masters
Title: Message Title Moses Mendoza commented on PUP-7198 Re: Puppet Server uses facts from the previous run (n-1) after agent switches masters Puppet PR: https://github.com/puppetlabs/puppet/pull/5866 Classifier PR: https://github.com/puppetlabs/classifier/pull/584 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-3514) Switch master branch travis tests to 9.6
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3514 Switch master branch travis tests to 9.6 Issue Type: Improvement Assignee: Rob Browning Created: 2017/05/12 11:27 AM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7521) Puppet Acceptance Test Failure in Imaging Acceptance Tests
Title: Message Title Adrien Thebo commented on PUP-7521 Re: Puppet Acceptance Test Failure in Imaging Acceptance Tests I investigated this test against Puppetserver master and I don't see anything that looks too unreasonable. My best guess is that there is a bug in the tests themselves; I suspect that the generated site.pp is not being generated with all of the configuration needed, but I can't directly tell. In order to do more investigation I'll need to be able to reproduce the failing build. I suspect that this is a bug in the test itself as opposed to a bug in Puppet or Puppetserver, but it seems that every time I say that I'm completely wrong. To move forward on this I'll either need a way to reproduce this failure via instructions for running this environment on my system, or a copy of the generated site.pp as it exists immediately before the failing tests are run. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7521) Puppet Acceptance Test Failure in Imaging Acceptance Tests
Title: Message Title Adrien Thebo assigned an issue to John O'Connor Puppet / PUP-7521 Puppet Acceptance Test Failure in Imaging Acceptance Tests Change By: Adrien Thebo Assignee: Adrien Thebo John O'Connor Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7525) Move Hocon gem from development dependency in Gemfile to runtime .gemspec dependency
Title: Message Title Ethan Brown created an issue Puppet / PUP-7525 Move Hocon gem from development dependency in Gemfile to runtime .gemspec dependency Issue Type: Task Affects Versions: PUP 5.0.0 Assignee: Unassigned Created: 2017/05/12 11:04 AM Priority: Normal Reporter: Ethan Brown Thomas Hallgren has run into an issue with executing tests against Fedora with ci:test:git given the environment does not include the hocon gem. Puppet already ships Hocon in the agent package (https://github.com/puppetlabs/puppet-agent/blob/7970f50df4544cd637c7dc7b2d895913fae3b2f4/configs/projects/puppet-agent.rb#L225), and puppet server also installs it (https://github.com/puppetlabs/puppetserver/blob/master/resources/ext/build-scripts/gem-list.txt) While the dependency supports an optional Hiera backend, given that it ships in the agent and server already - it makes sense to include it officially in the .gemspec so that it's also available in the ci:test:git scenario. This is also made simpler given hocon is a pure Ruby implementation with no native code or platform specific dependencies.
Jira (PUP-7149) Puppet should include job id in reports and catalogs
Title: Message Title Michael Smith updated an issue Puppet / PUP-7149 Puppet should include job id in reports and catalogs Change By: Michael Smith Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7149) Puppet should include job id in reports and catalogs
Title: Message Title Michael Smith updated an issue Puppet / PUP-7149 Puppet should include job id in reports and catalogs Change By: Michael Smith Release Notes Summary: A job id field has been added to the report, and is passed in the catalog request. Release Notes: New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7149) Puppet should include job id in reports and catalogs
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-7149 Puppet should include job id in reports and catalogs Change By: Michael Smith Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7149) Puppet should include job id in reports and catalogs
Title: Message Title Alex Dreyer assigned an issue to Unassigned Puppet / PUP-7149 Puppet should include job id in reports and catalogs Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7503) helpful_error_message_when_hostname_not_match_server_certificate test fails with Ruby 2.4
Title: Message Title Maggie Dreyer commented on PUP-7503 Re: helpful_error_message_when_hostname_not_match_server_certificate test fails with Ruby 2.4 Merged to master at https://github.com/puppetlabs/puppet/commit/d973bdedb510cc1648e739ccfe28d4d9bcffa6de Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-3511) Invalid commands prevent KahaDB GC
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3511 Invalid commands prevent KahaDB GC Change By: Russell Mull Team: Systems Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-3511) Invalid commands prevent KahaDB GC
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3511 Invalid commands prevent KahaDB GC Change By: Russell Mull Summary: Invalid commands prevent KahaDB GC doesn't happen, sometimes Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-1916) puppet cert clean cannot remove signing requests
Title: Message Title David Hollinger commented on PUP-1916 Re: puppet cert clean cannot remove signing requests Can we get this ticket updated to show that this effects puppetserver <= 2.7.2 and puppet <= 4.10.1? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7523) Can't gem install puppet with some versions of bundler and ruby 1.9.3
Title: Message Title Ethan Brown commented on PUP-7523 Re: Can't gem install puppet with some versions of bundler and ruby 1.9.3 Merged to stable in https://github.com/puppetlabs/puppet/commit/0c4efdc2d1f708391b0c9146daaa0b4d8f4bf5ba Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7010) Allow usage of .te files in selmodule
Title: Message Title Eric Seynaeve commented on PUP-7010 Re: Allow usage of .te files in selmodule This got fixed with version 1.0 of https://github.com/voxpupuli/puppet-selinux/ Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-677) user type accepts numeric usernames, but ssh_authorized_key does not
Title: Message Title Bowie Bartels commented on PUP-677 Re: user type accepts numeric usernames, but ssh_authorized_key does not I found a "solution". I used the numeric username for UID and GID as well, and now it works fine! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7515) data-in-modules: lookup() and automatic class parameter lookup result in different values
Title: Message Title Henrik Lindberg commented on PUP-7515 Re: data-in-modules: lookup() and automatic class parameter lookup result in different values Robert Heinzmann Hm, that requires quite a lot of words to explain. Unfortunately there is no succinct specification of all variable resolution, and there are bugs that have been fixed along the way. It is also quite complex, and in parts probably not even desired as puppet once had "dynamic scoping" with very strange rules (and some of those remain for the sake of backwards compatibility). First, there is a big difference if a name is qualified or not (qualified == the name has '::' somewhere inside it). A qualified name is always absolute (absolute == starts from top scope). A qualified variable always resolves directly (no search) except when the name refers to a class variable (class parameter or introduced in a class scope as a local variable) and where the class inherits from another. Example - $b::x where 'b' inherits 'a', will search for 'b::x', and then 'a::x'. (To make this quite confusing; there is a bug (PUP-5635, fixed in Puppet 5.0.0) that makes the search continue with a non qualified search for 'x'). You can view a qualified variable resolution as an external "being outside looking in" kind of resolution. A non qualified variable (there are no '::' in the name) is searched for as a relative name; first in the scope where the resolution originates (the reference to the variable), then the parent scopes of the local scope until hitting a class or resource scope, then the inherited class' scope (if any) else the enclosing scope (the scope where the class was included). Unless an inherited class is already included, it will be included in the same scope as the inheriting class. Note that the relative resolution searches inherited, and then the inherited's class enclosing scope (it skips the class' enclosing scope all together in the search!). You can think of a relative name resolution as an "ascending search through the 'parent/enclosing' chain" on the formula (Here -> (Inherited || Enclosing) -> Enclosing) until topscope is reached. Resolutions that take place in Parameter Scope are somewhat special - as the parameters are evaluated as part of creating a class / resource and the thing being created does not quite yet exist. This part is specified https://github.com/puppetlabs/puppet-specifications/blob/master/language/parameter_scope.md The the complicated resolution of variable references in Puppet creates many to scratch their heads as it is difficult to reason about what will happen. Therefore the recommendations (to avoid the problems) are: Do not use class inheritance Use APL to set values for missing parameters Refer to all facts using $facts Use ENC instead of node expressions if using node expressions, do not rely on node scope level variables
Jira (PUP-7381) Consistently use encode_with for YAML serialization
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-7381 Consistently use encode_with for YAML serialization Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7524) Deprecate Ruby 2.1.0 as Ruby 2.1 EOL 1.4.2017
Title: Message Title Robert Heinzmann updated an issue Puppet / PUP-7524 Deprecate Ruby 2.1.0 as Ruby 2.1 EOL 1.4.2017 Change By: Robert Heinzmann Acceptance Criteria: * AIO comes with supported ruby version (2.4) * All tests are ok (including hiera5) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7524) Deprecate Ruby 2.1.0 as Ruby 2.1 EOL 1.4.2017
Title: Message Title Robert Heinzmann created an issue Puppet / PUP-7524 Deprecate Ruby 2.1.0 as Ruby 2.1 EOL 1.4.2017 Issue Type: Bug Affects Versions: PUP 4.10.0 Assignee: Unassigned Components: AIO Created: 2017/05/12 2:35 AM Environment: Puppet 4.10, Centos7 Priority: Major Reporter: Robert Heinzmann As posted here https://www.ruby-lang.org/en/news/2017/04/01/support-of-ruby-2-1-has-ended/ Ruby has EOL'd at 1.4.2017. So no more security fixes for included AIO Ruby root@SERVER # puppet -V
Jira (PUP-7524) Deprecate Ruby 2.1.0 as Ruby 2.1 EOL 1.4.2017
Title: Message Title Robert Heinzmann updated an issue Puppet / PUP-7524 Deprecate Ruby 2.1.0 as Ruby 2.1 EOL 1.4.2017 Change By: Robert Heinzmann Acceptance Criteria: * AIO comes with supported ruby version * All tests are ok (including hiera5) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7515) data-in-modules: lookup() and automatic class parameter lookup result in different values
Title: Message Title Robert Heinzmann commented on PUP-7515 Re: data-in-modules: lookup() and automatic class parameter lookup result in different values So much text ... so what is the question to the Puppet Team ? Q1) Is all the described here expected behaviour of puppet (part of spec) and can module developers and puppetmaster operators rely on this behaviour to be stable as of Puppet 4.10.0++ (and write test against it) ? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7515) data-in-modules: lookup() and automatic class parameter lookup result in different values
Title: Message Title Robert Heinzmann commented on PUP-7515 Re: data-in-modules: lookup() and automatic class parameter lookup result in different values Regarding 1) - for others who might read this Q: Now how to fix the hiera_* calls? A: With global: hiera3/hiera5 and environment: hiera5 all three parameters are the same, also for hiera_* calls: Global Layers: Global Layer Hiera3: SERVER mymodule # cat global_hiera_3.yaml --- :backends: - yaml :hierarchy: - "common" :yaml: :datadir: /data/hiera
Jira (PUP-7515) data-in-modules: lookup() and automatic class parameter lookup result in different values
Title: Message Title Robert Heinzmann commented on PUP-7515 Re: data-in-modules: lookup() and automatic class parameter lookup result in different values For others who might read this thread: I tested with lookup_options and it makes the behaviour of lookup and APL (Automatic Parameter Lookup) consistent: SERVER mymodule # bash enc.sh --- parameters: role: - role1 Without lookup_options: SERVER mymodule # FACTER_role_txt=role2 puppet apply --node_terminus=exec --external_nodes=$(pwd)/enc.sh --modulepath ../ -e 'include mymodule' --strict off --hiera_config=../devnull Warning: The node parameter 'role' for node 'SERVER' was already set to '["role1"]'. It could not be set to '["role2"]' Notice: Scope(Class[Mymodule]): === Config ==
Jira (PUP-7523) Can't gem install puppet with some versions of bundler and ruby 1.9.3
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-7523 Can't gem install puppet with some versions of bundler and ruby 1.9.3 Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7523) Can't gem install puppet with some versions of bundler and ruby 1.9.3
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7523 Can't gem install puppet with some versions of bundler and ruby 1.9.3 Change By: Josh Cooper Fix Version/s: PUP 4.10.2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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-7523) Can't gem install puppet with some versions of bundler and ruby 1.9.3
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7523 Can't gem install puppet with some versions of bundler and ruby 1.9.3 Change By: Josh Cooper Team: Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "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.
