Jira (PUP-6339) Hiera Data in Module give bad results when environment_timeout is unlimited
Title: Message Title
Chuck Schweizer updated an issue
Puppet / PUP-6339
Hiera Data in Module give bad results when environment_timeout is unlimited
Change By:
Chuck Schweizer
1) Set environment_timeout to unlimited (this does not occur if set to 0)2) Setup hiera data in a module that use a FACT to determine what it should do.3) Set the fact differently on two or more clients4) Run puppet from each of the clients at the same timeAfter a few puppet runs they will stop getting the correct hiera data in module values from the PuppetServer.eg. server1 could see the server2 value or server2 could see the server1 value.SAMPLE module:{code:java}./test_module./test_module/hieradata./test_module/hieradata/common.yaml./test_module/hieradata/server1.yaml./test_module/hieradata/server2.yaml./test_module/manifests./test_module/manifests/init.pp./test_module/metadata.json./test_module/hiera.yaml{code}*init.pp*{code:java}class test_module ( $my_var = 'not from hiera',){ notify{"The variable is $my_var":}}{code} ./test_module/hieradata/common.yaml{code:java}---test_module::my_var: 'In common.yaml'{code} hiera.yaml{code:java}---version: 4datadir: hieradatahierarchy: - name: "%{my_fact}"backend: yaml - name: "common"backend: yaml{code}./test_module/hieradata/ common.yaml{code:java}---test_module::my_var: 'In common.yaml'{code}./test_module/hieradata/ server1.yaml{code:java}---test_module::my_var: 'server1'{code}./test_module/hieradata/server2.yaml{code:java}---test_module::my_var: 'server2'{code}SERVER1/etc/puppetlabs/facter/facts.d/my_fact.txt my_fact=server1SERVER2/etc/puppetlabs/facter/facts.d/my_fact.txt my_fact=server2Error seen in Puppetserver logs{code:java}[puppetserver] Puppet Caching node for server1.mydomain[puppetserver] Puppet Class 'settings' is already defined; cannot redefine at :[puppetserver] Puppet Compiled catalog for server1.mydomain in environment production in 0.04 seconds{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6339) Hiera Data in Module give bad results when environment_timeout is unlimited
Title: Message Title
Chuck Schweizer updated an issue
Puppet / PUP-6339
Hiera Data in Module give bad results when environment_timeout is unlimited
Change By:
Chuck Schweizer
1) Set environment_timeout to unlimited (this does not occur if set to 0)2) Setup hiera data in a module that use a FACT to determine what it should do.3) Set the fact differently on two or more clients4) Run puppet from each of the clients at the same timeAfter a few puppet runs they will stop getting the correct hiera data in module values from the PuppetServer.eg. server1 could see the server2 value or server2 could see the server1 value.SAMPLE module:{code:java}./test_module./test_module/hieradata./test_module/hieradata/common.yaml./test_module/hieradata/server1.yaml./test_module/hieradata/server2.yaml./test_module/manifests./test_module/manifests/init.pp./test_module/metadata.json./test_module/hiera.yaml{code}*init.pp*{code:java}class test_module ( $my_var = 'not from hiera',){ notify{"The variable is $my_var":}}{code}./test_module/hieradata/common.yaml{code:java}---test_module::my_var: 'In common.yaml'{code} ./test_module/hieradata/server1.yaml hiera.yaml{code:java}---version: 4datadir: hieradatahierarchy: - name: "%{my_fact}"backend: yaml - name: "common"backend: yaml{code} ./test_module/hieradata/server1.yaml {code:java}---test_module::my_var: 'server1'{code}./test_module/hieradata/server2.yaml {code:java}---test_module::my_var: 'server2'{code}SERVER1/etc/puppetlabs/facter/facts.d/my_fact.txt my_fact=server1SERVER2/etc/puppetlabs/facter/facts.d/my_fact.txt my_fact=server2Error seen in Puppetserver logs{code:java}[puppetserver] Puppet Caching node for server1.mydomain[puppetserver] Puppet Class 'settings' is already defined; cannot redefine at :[puppetserver] Puppet Compiled catalog for server1.mydomain in environment production in 0.04 seconds{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6339) Hiera Data in Module give bad results when environment_timeout is unlimited
Title: Message Title Chuck Schweizer created an issue Puppet / PUP-6339 Hiera Data in Module give bad results when environment_timeout is unlimited Issue Type: Bug Affects Versions: PUP 4.5.0, PUP 4.4.2 Assignee: Unassigned Components: Puppet Server Created: 2016/05/21 6:28 PM Environment: Puppet Server is running on RHEL 7.2 Puppet Clients are RHEL 6.8 and 7.2 puppet-agent-1.5.0-1.el7.x86_64 puppetdb-termini-4.1.0-1.el7.noarch puppetserver-2.4.0-1.el7.noarch Priority: Normal Reporter: Chuck Schweizer 1) Set environment_timeout to unlimited (this does not occur if set to 0) 2) Setup hiera data in a module that use a FACT to determine what it should do. 3) Set the fact differently on two or more clients 4) Run puppet from each of the clients at the same time After a few puppet runs they will stop getting the correct hiera data in module values from the PuppetServer. eg. server1
Jira (PUP-6321) undef in custom type autorequire value causes error in Puppet 4.5.0
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6321
undef in custom type autorequire value causes error in Puppet 4.5.0
Change By:
Henrik Lindberg
Acceptance Criteria:
That the reproducer does not error:{code}# sudo rpm -ivh https://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm# yum install puppet-agent# /opt/puppetlabs/puppet/bin/puppet --version4.5.0# /opt/puppetlabs/puppet/bin/puppet module install puppet/archive --version 0.5.1# # cat > foo.pp < 'https://updates.jenkins-ci.org/download/plugins/git-client/1.19.6/git-client.hpi', path => '/tmp/git-client.hpi', checksum_verify => false, checksum => undef, checksum_type => 'sha1', proxy_server => undef, cleanup => false, extract => false,}EOF# puppet apply ./foo.pp{code}
Release Notes Summary:
A regression from Puppet 4.4 caused types that used autorequire to fail when the referenced set contained undef entries. This could also be the cause of other errors (although none have been reported at this time).
Release Notes:
Bug Fix
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6125) verbose agent runs result data being sent console and syslog
Title: Message Title Matthew Gyurgyik commented on PUP-6125 Re: verbose agent runs result data being sent console and syslog Submitted a new pull request https://github.com/puppetlabs/puppet/pull/4982 which follows the implementation Michael Smith described. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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-1394) Warning printed when 'ip route show' output contains "linkdown"
Title: Message Title Chris Boot commented on FACT-1394 Re: Warning printed when 'ip route show' output contains "linkdown" FACT-1405 is possibly a duplicate of this bug. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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-1405) Facter does not like next hop flags in ip route output
Title: Message Title Chris Boot commented on FACT-1405 Re: Facter does not like next hop flags in ip route output This is a possible duplicate of FACT-1394. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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-1405) Facter does not like next hop flags in ip route output
Title: Message Title Chris Boot commented on FACT-1405 Re: Facter does not like next hop flags in ip route output This also occurs on Debian Stretch (testing), but not on Debian Jessie (stable) even with a back-ported kernel. I suspect this is due to the former using iproute2_4.3.0-1 rather than 3.16.0-2. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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-6338) Allow arrow syntax on the contain keyword
Title: Message Title
Jesús M. Navarro created an issue
Puppet / PUP-6338
Allow arrow syntax on the contain keyword
Issue Type:
New Feature
Assignee:
Unassigned
Components:
Language
Created:
2016/05/21 12:21 PM
Priority:
Minor
Reporter:
Jesús M. Navarro
Given the following declaration:
class { 'someclass': } ~> Resource['some::resource']
contain 'someclass'
Allow for this shortcut:
Jira (PUP-6328) Parsing of strings changes with puppet 4.5.0
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6328 Parsing of strings changes with puppet 4.5.0 Change By: Kylo Ginsberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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-6324) DNF provider cannot update packages (install command will not update)
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6324 DNF provider cannot update packages (install command will not update) Change By: Kylo Ginsberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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-6303) Acceptance: nim_package_provider test fails on AIX 5.3
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6303 Acceptance: nim_package_provider test fails on AIX 5.3 Change By: Kylo Ginsberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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-6326) mount native type use systemd mount units rather than fstab entry
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6326 mount native type use systemd mount units rather than fstab entry Change By: Kylo Ginsberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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-6326) mount native type use systemd mount units rather than fstab entry
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-6326 mount native type use systemd mount units rather than fstab entry Change By: Kylo Ginsberg Assignee: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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-6325) mount native type support /etc/fstab.d/
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6325 mount native type support /etc/fstab.d/ Change By: Kylo Ginsberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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-6325) mount native type support /etc/fstab.d/
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-6325 mount native type support /etc/fstab.d/ Change By: Kylo Ginsberg Assignee: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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-6235) build_should_not_allow_symlinks acceptance test failing on posix platforms
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6235 build_should_not_allow_symlinks acceptance test failing on posix platforms Change By: Kylo Ginsberg Affects Version/s: PUP 4.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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-6270) tests/environment/environment_scenario-bad.rb fails on all master platforms
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6270 tests/environment/environment_scenario-bad.rb fails on all master platforms Change By: Kylo Ginsberg Fix Version/s: PUP 4.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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-6270) tests/environment/environment_scenario-bad.rb fails on all master platforms
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6270 tests/environment/environment_scenario-bad.rb fails on all master platforms Change By: Kylo Ginsberg Affects Version/s: PUP 4.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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-6329) puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename
Title: Message Title Henrik Lindberg commented on PUP-6329 Re: puppet apply fails with "Error: Could not set 'file' on ensure: invalid byte sequence in US-ASCII" with non-ASCII filename ping @kylo and Chris Price Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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-6331) Hiera interpolations are interpreted in the data() function
Title: Message Title Henrik Lindberg commented on PUP-6331 Re: Hiera interpolations are interpreted in the data() function Ping Thomas Hallgren, I forgot how the discussion went on this, I suspect I accepted the change that led to this. The % interpolation syntax is unfortunate, would be much better to use the existing puppet language interpolation and do real calls to lookup IMO. In general the % syntax in hiera is seen as 'yet another confusing syntax to learn' (besides being neither very good nor powerful). Is it possible to have this be different per provider type? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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-6333) Mount creates 0600 /etc/fstab
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6333 Mount creates 0600 /etc/fstab Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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-6332) Ability to mount as specific user
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6332 Ability to mount as specific user Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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-5973) Remove Symbol monkey patch
Title: Message Title Henrik Lindberg commented on PUP-5973 Re: Remove Symbol monkey patch Note: test carefully on JRuby since String#==(other) is implemented as other#<=> == 0 in JRuby. This means that every String/Symbol equality check will be affected. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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-6334) ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x)
Title: Message Title Henrik Lindberg assigned an issue to Brian Conner Puppet / PUP-6334 ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x) Change By: Henrik Lindberg Assignee: Brian Conner Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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-6334) ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x)
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6334 ProviderInit returns false with Puppet 4.5; on the same system it returns true with Puppet 4.4.2 (CentOS 6.x) Change By: Henrik Lindberg Priority: Critical Normal Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "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.
