Jira (PUP-6993) Puppet acceptance test failures for Japanese Windows
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6993 Puppet acceptance test failures for Japanese Windows Change By: Ethan Brown Sprint: AP Triage 2016-12-28 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-6993) Puppet acceptance test failures for Japanese Windows
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6993 Puppet acceptance test failures for Japanese Windows Change By: Ethan Brown Summary: Acceptance Puppet acceptance test failures for Japanese Windows 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-6993) Acceptance test failures for Japanese Windows
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-6993
Acceptance test failures for Japanese Windows
Change By:
Ethan Brown
Noted in IMAGES-390 at https://tickets.puppetlabs.com/browse/IMAGES-390?focusedCommentId=374916=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-374916 there were issues running the full acceptance suite for Puppet against the Japanese Windows 2012R2 template {{win-2012r2-ja-x86_64}}This ticket tracks failures in the Puppet suite that do not properly accommodate non-ASCII output during tests (where https://gist.github.com/Iristyle/771b6ec052570e34f02009da531aed4a has all the test failures in detail). The identified problems are:* BKR-1008 - user_get failure - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/user/should_modify.rb* BKR-1008 - user_get failure - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/user/should_create.rb* BKR-1011 - group_get failure - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/group/should_create.rb* This ticket - failure in test code - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/windows/eventlog.rb* This ticket - failure in test heleprs - Not yet triaged - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/modules/install/with_version.rb* This ticket - failure in test heleprs - Not yet triaged - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/modules/install/basic_install.rb* Likely a point in time failure - unrelated to UTF-8 work - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/parser_functions/puppet_lookup_cmd.rb#L2385-L2389To reproduce the failures, using the following {{hosts.yaml}}:{code}---HOSTS: centos6-64-1:pe_dir:pe_ver:pe_upgrade_dir:pe_upgrade_ver:hypervisor: vmpoolerplatform: el-6-x86_64template: centos-6-x86_64roles:- agent- master- database- dashboard windows2012r2-64-1:pe_dir:pe_ver:pe_upgrade_dir:pe_upgrade_ver:hypervisor: vmpoolerplatform: windows-2012r2-64ruby_arch: x64template: win-2012r2-ja-x86_64# template: win-2012r2-x86_64roles:- agentCONFIG: nfs_server: none consoleport: 443 pooling_api: http://vmpooler.delivery.puppetlabs.net/{code}And execute:{code}GEM_SOURCE=http://rubygems.delivery.puppetlabs.net/ bundle exec rake ci:test:aio BEAKER_HOSTS=hosts.yaml SHA='1.8.1' SERVER_VERSION='2.7.1'{code}
Add Comment
Jira (PUP-6993) Acceptance test failures for Japanese Windows
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-6993
Acceptance test failures for Japanese Windows
Change By:
Ethan Brown
Noted in IMAGES-390 at https://tickets.puppetlabs.com/browse/IMAGES-390?focusedCommentId=374916=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-374916 there were issues running the full acceptance suite for Puppet against the Japanese Windows 2012R2 template {{win-2012r2-ja-x86_64}}This ticket tracks failures in the Puppet suite that do not properly accommodate non-ASCII output during tests (where https://gist.github.com/Iristyle/771b6ec052570e34f02009da531aed4a has all the test failures in detail). The identified problems are:* BKR-1008 - user_get failure - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/user/should_modify.rb* BKR-1008 - user_get failure - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/user/should_create.rb* BKR-1011 - group_get failure - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/group/should_create.rb* This ticket - failure in test code - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/windows/eventlog.rb* This ticket - failure in test heleprs - Not yet triaged - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/modules/install/with_version.rb* This ticket - failure in test heleprs - Not yet triaged - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/modules/install/basic_install.rb* Not yet triaged Likely a point in time failure - unrelated to UTF-8 work - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/parser_functions/puppet_lookup_cmd.rb#L2385-L2389To reproduce the failures, using the following {{hosts.yaml}}:{code}---HOSTS: centos6-64-1:pe_dir:pe_ver:pe_upgrade_dir:pe_upgrade_ver:hypervisor: vmpoolerplatform: el-6-x86_64template: centos-6-x86_64roles:- agent- master- database- dashboard windows2012r2-64-1:pe_dir:pe_ver:pe_upgrade_dir:pe_upgrade_ver:hypervisor: vmpoolerplatform: windows-2012r2-64ruby_arch: x64template: win-2012r2-ja-x86_64# template: win-2012r2-x86_64roles:- agentCONFIG: nfs_server: none consoleport: 443 pooling_api: http://vmpooler.delivery.puppetlabs.net/{code}And execute:{code}GEM_SOURCE=http://rubygems.delivery.puppetlabs.net/ bundle exec rake ci:test:aio BEAKER_HOSTS=hosts.yaml SHA='1.8.1' SERVER_VERSION='2.7.1'{code}
Add Comment
Jira (PUP-6993) Acceptance test failures for Japanese Windows
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6993 Acceptance test failures for Japanese Windows Change By: Ethan Brown Story Points: 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-6777) regression: incompatible character encodings: UTF-8 and ASCII-8BIT
Title: Message Title Moses Mendoza commented on PUP-6777 Re: regression: incompatible character encodings: UTF-8 and ASCII-8BIT PR raised, but I think we're going to want acceptance tests added. Working on those. 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-6777) regression: incompatible character encodings: UTF-8 and ASCII-8BIT
Title: Message Title Moses Mendoza assigned an issue to Unassigned Puppet / PUP-6777 regression: incompatible character encodings: UTF-8 and ASCII-8BIT 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 (PUP-6994) acceptance: no_exception_in_reduce_with_bignum doesn't test anything
Title: Message Title Josh Cooper commented on PUP-6994 Re: acceptance: no_exception_in_reduce_with_bignum doesn't test anything When you're running Puppet WEBrick, do you run the process as the "puppet" user? Yep, we switch to puppet user and group. 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-6994) acceptance: no_exception_in_reduce_with_bignum doesn't test anything
Title: Message Title Jeremy Barlow commented on PUP-6994 Re: acceptance: no_exception_in_reduce_with_bignum doesn't test anything Hmmm, that's interesting. When you're running Puppet WEBrick, do you run the process as the "puppet" user. Can't immediately explain what the difference might be. Not sure if there are some differences in the behavior of the underlying file enumeration logic used which returns errors when run under MRI but not under JRuby. If we can pinpoint differences at that level, we could submit defects to the JRuby project. 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-6995) Running "puppet master --compile" as root will cause future compiles for that node to fail
Title: Message Title Jeremy Barlow commented on PUP-6995 Re: Running "puppet master --compile" as root will cause future compiles for that node to fail Josh Cooper It would make sense to me (based on feasibility) to have the user be switched to Puppet during compilation (since that's what the master would be doing when run as a daemon anyway). 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-6995) Running "puppet master --compile" as root will cause future compiles for that node to fail
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6995 Running "puppet master --compile" as root will cause future compiles for that node to fail Change By: Josh Cooper Summary: Running "puppet master --compile" as root will prevent puppetserver from updating the file cause future compiles for that node to fail 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-6995) Running "puppet master --compile" as root will prevent puppetserver from updating the file
Title: Message Title Josh Cooper created an issue Puppet / PUP-6995 Running "puppet master --compile" as root will prevent puppetserver from updating the file Issue Type: Bug Assignee: Unassigned Created: 2016/12/09 3:50 PM Priority: Normal Reporter: Josh Cooper Normally the puppet master (webrick and puppetserver) run as the puppet user, and during a compilation, the master saves the most recent Puppet::Node object containing facts to /opt/puppetlabs/puppet/cache/yaml/node/.yaml. If you run puppet master --compile as root, then the above file will have permissions root:root:644 (depending on umask). The next time the real puppet master (running as puppet) tries to compile a catalog for that node, it will fail, and the client will receive the following error: Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Failed when searching for node lc7iuwd73thlc02.delivery.puppetlabs.net: Operation not permitted - /opt/puppetlabs/puppet/cache/yaml/node/lc7iuwd73thlc02.delivery.puppetlabs.net.yaml20161209-26698-xwr45p Puppet lookup may also have this issue, because it sets the node_cache_terminus to write_only_yaml as well. I think the master
Jira (PUP-6993) Acceptance test failures for Japanese Windows
Title: Message Title
Ethan Brown updated an issue
Puppet / PUP-6993
Acceptance test failures for Japanese Windows
Change By:
Ethan Brown
Noted in IMAGES-390 at https://tickets.puppetlabs.com/browse/IMAGES-390?focusedCommentId=374916=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-374916 there were issues running the full acceptance suite for Puppet against the Japanese Windows 2012R2 template {{win-2012r2-ja-x86_64}}This ticket tracks failures in the Puppet suite that do not properly accommodate non-ASCII output during tests (where https://gist.github.com/Iristyle/771b6ec052570e34f02009da531aed4a has all the test failures in detail). The identified problems are:* BKR-1008 - user_get failure - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/user/should_modify.rb* BKR-1008 - user_get failure - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/user/should_create.rb* BKR-1011 - group_get failure - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/group/should_create.rb* This ticket - failure in test code - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/windows/eventlog.rb* This ticket - failure in test heleprs - Not yet triaged - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/modules/install/with_version.rb* This ticket - failure in test heleprs - Not yet triaged - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/modules/install/basic_install.rb* Not yet triaged - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/parser_functions/puppet_lookup_cmd.rb#L2385-L2389To reproduce the failures, using the following {{hosts.yaml}}:{code}---HOSTS: centos6-64-1:pe_dir:pe_ver:pe_upgrade_dir:pe_upgrade_ver:hypervisor: vmpoolerplatform: el-6-x86_64template: centos-6-x86_64roles:- agent- master- database- dashboard windows2012r2-64-1:pe_dir:pe_ver:pe_upgrade_dir:pe_upgrade_ver:hypervisor: vmpoolerplatform: windows-2012r2-64ruby_arch: x64template: win-2012r2-ja-x86_64# template: win-2012r2-x86_64roles:- agentCONFIG: nfs_server: none consoleport: 443 pooling_api: http://vmpooler.delivery.puppetlabs.net/{code}And execute:{code}GEM_SOURCE=http://rubygems.delivery.puppetlabs.net/ bundle exec rake ci:test:aio BEAKER_HOSTS=hosts.yaml SHA='1.8.1' SERVER_VERSION='2.7.1'{code}
Add Comment
Jira (FACT-1551) WSA not initalized before loading custom facts
Title: Message Title Rob Reynolds updated an issue Facter / FACT-1551 WSA not initalized before loading custom facts Change By: Rob Reynolds Labels: maintenance windows Team: Agent & Platform Sprint: AP Triage 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-1551) WSA not initalized before loading custom facts
Title: Message Title Rob Reynolds updated an issue Facter / FACT-1551 WSA not initalized before loading custom facts Change By: Rob Reynolds Labels: maintenance pe windows 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-1551) WSA not initalized before loading custom facts
Title: Message Title Rob Reynolds updated an issue Facter / FACT-1551 WSA not initalized before loading custom facts Change By: Rob Reynolds Labels: windows 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-1476) Puppet agent should supply an informative user agent
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1476 Puppet agent should supply an informative user agent Change By: Josh Cooper Release Notes Summary: Puppet will now send a useful User-Agent header when making HTTP requests (of the form User-Agent: Puppet/4.8.2 Ruby/2.1.9-p353 (x86_64-linux). Previously it just sent "Ruby" which wasn't very helpful. 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-6993) Acceptance test failures for Japanese Windows
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6993 Acceptance test failures for Japanese Windows Change By: Ethan Brown Priority: Normal Blocker 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-1551) WSA not initalized before loading custom facts
Title: Message Title Thomas Kishel created an issue Facter / FACT-1551 WSA not initalized before loading custom facts Issue Type: Bug Affects Versions: FACT 3.4.1 Assignee: Unassigned Components: Windows Created: 2016/12/09 2:07 PM Environment: Windows Server 2012R2 with facter 3.4.1 Priority: Normal Reporter: Thomas Kishel Customer reports: I have implemented a custom fact using net/http to query a service on the local host, however when the code is run from facter on Windows Server 2012R2/2016 the following error is received: ERROR puppetlabs.facter - error while resolving custom fact "testy": getaddrinfo: Either the application has not called WSAStartup, or WSAStartup failed. Simplified example code:
Jira (PUP-6781) support 'verbatim' lookup option
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6781 support 'verbatim' lookup option Change By: Josh Cooper Fix Version/s: PUP 4.9.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-6781) support 'verbatim' lookup option
Title: Message Title Josh Cooper assigned an issue to qa Puppet / PUP-6781 support 'verbatim' lookup option Change By: Josh Cooper 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-6973) Make Hiera v5 configuration sensitive to changes of interpolated values
Title: Message Title Josh Cooper assigned an issue to qa Puppet / PUP-6973 Make Hiera v5 configuration sensitive to changes of interpolated values Change By: Josh Cooper 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-6942) Modify lookup to always use hiera.yaml.
Title: Message Title Josh Cooper assigned an issue to qa Puppet / PUP-6942 Modify lookup to always use hiera.yaml. Change By: Josh Cooper 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-6918) SSL - Improve CSR to local public key mismatch handling
Title: Message Title Josh Cooper assigned an issue to qa Puppet / PUP-6918 SSL - Improve CSR to local public key mismatch handling Change By: Josh Cooper 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-6918) SSL - Improve CSR to local public key mismatch handling
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6918 SSL - Improve CSR to local public key mismatch handling Change By: Josh Cooper Fix Version/s: PUP 4.9.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-6974) Looking up a 'false' value in hiera.yaml when using data in modules does not return a result.
Title: Message Title Josh Cooper assigned an issue to qa Puppet / PUP-6974 Looking up a 'false' value in hiera.yaml when using data in modules does not return a result. Change By: Josh Cooper 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-6758) Fix pkgng provider
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6758 Fix pkgng provider Change By: Josh Cooper Release Notes Summary: Gracefully fail if the pkg fails to enumerate installed packages. 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-6831) Change reverse.each to more efficient reverse_each
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6831 Change reverse.each to more efficient reverse_each Change By: Josh Cooper 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-6840) Establish revert policy for failing changes
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6840 Establish revert policy for failing changes Change By: Josh Cooper 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-6758) Fix pkgng provider
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6758 Fix pkgng provider Change By: Josh Cooper Fix Version/s: PUP 4.9.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-6758) Fix pkgng provider
Title: Message Title Josh Cooper assigned an issue to qa Puppet / PUP-6758 Fix pkgng provider Change By: Josh Cooper Status: Ready for CI Test Assignee: Adrien Thebo 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-1476) Puppet agent should supply an informative user agent
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1476 Puppet agent should supply an informative user agent Change By: Josh Cooper Fix Version/s: PUP 4.9.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-1476) Puppet agent should supply an informative user agent
Title: Message Title Josh Cooper assigned an issue to qa Puppet / PUP-1476 Puppet agent should supply an informative user agent Change By: Josh Cooper Status: Ready for CI Test Assignee: Moses Mendoza 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-6994) acceptance: no_exception_in_reduce_with_bignum doesn't test anything
Title: Message Title
Josh Cooper created an issue
Puppet / PUP-6994
acceptance: no_exception_in_reduce_with_bignum doesn't test anything
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/12/09 12:24 PM
Priority:
Normal
Reporter:
Josh Cooper
The acceptance test defines a function which relies on a merge function:
https://github.com/puppetlabs/puppet/blob/9dda0a424b5067cabdfd70f72b286fa7f29f604a/acceptance/tests/parser_functions/no_exception_in_reduce_with_bignum.rb#L51
The merge function is defined by stdlib, but isn't in puppet. If you try to run webrick against the site.pp manifest from the test, you'll get two problems.
First, the quotes in site.pp are not escaped (they're escaped in beaker, but it needs an additional set of escapes).
"keyname1"=>{
"key"=>"ABCDEF",
"options"=>["from="10.0.0.0/8""]
Jira (PUP-6993) Acceptance test failures for Japanese Windows
Title: Message Title Ethan Brown created an issue Puppet / PUP-6993 Acceptance test failures for Japanese Windows Issue Type: Bug Assignee: Unassigned Components: Windows Created: 2016/12/09 11:23 AM Labels: utf-8 i18n Priority: Normal Reporter: Ethan Brown Noted in IMAGES-390 at https://tickets.puppetlabs.com/browse/IMAGES-390?focusedCommentId=374916=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-374916 there were issues running the full acceptance suite for Puppet against the Japanese Windows 2012R2 template win-2012r2-ja-x86_64 This ticket tracks failures in the Puppet suite that do not properly accommodate non-ASCII output during tests (where https://gist.github.com/Iristyle/771b6ec052570e34f02009da531aed4a has all the test failures in detail). The identified problems are: BKR-1008 - user_get failure - https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/user/should_modify.rb BKR-1008 - user_get failure -
Jira (PUP-2849) When using a proxy the Puppet Agent should use an FQDN for the Puppet Master.
Title: Message Title Josh Cooper commented on PUP-2849 Re: When using a proxy the Puppet Agent should use an FQDN for the Puppet Master. Puppet agents don't know the fqdn of the puppet master, which is why it defaults server to puppet regardless of proxy settings. There's no way around configuring the server property on the agent, unless you setup DNS or use SRV records. Closing this. 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-6739) If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Title: Message Title Jeremy Adams commented on PUP-6739 Re: If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command Also affects puppet module command: [root@pup-vra7-0444 ~]# puppet module list /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/environments.rb:38:in `get!': Could not find a directory environment named 'dev' anywhere in the path: /etc/puppetlabs/code/environments. Does the directory exist? (Puppet::Environments::EnvironmentNotFound) from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application_support.rb:29:in `push_application_context' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:337:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run' from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' from /usr/local/bin/puppet:5:in `' [root@pup-vra7-0444 ~]# puppet module install stahnma-epel
Jira (PUP-6739) If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command
Title: Message Title Jeremy Adams updated an issue Puppet / PUP-6739 If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command Change By: Jeremy Adams Summary: If no matching local $environment folder on agent, error when running any 'puppet config' or 'puppet module' command 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-6983) File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0.
Title: Message Title Sean Griffin commented on PUP-6983 Re: File resource drift correction fails for files named with utf-8 chars on ubuntu 1604, windows. Exit status = 0. On the ubuntu 16 VM, the LANG env variable was set to en_US. On the ubuntu 14 VM, it is en_US-UTF-8. Changing that to en_US-UTF-8 on the ubuntu 16 system fixes the problem. 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-6956) Pin puppet CI LTS-1.7 => server 2.5.0 and stable/master => server 2.7.0
Title: Message Title Moses Mendoza commented on PUP-6956 Re: Pin puppet CI LTS-1.7 => server 2.5.0 and stable/master => server 2.7.0 this has run through the affected puppet agent pipelines 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-3223) (maint) USe the clj-parent project (version 0.2.5) for dependencies
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3223 (maint) USe the clj-parent project (version 0.2.5) for dependencies Issue Type: Bug Assignee: Unassigned Created: 2016/12/09 9:57 AM Priority: Normal Reporter: gepetto-bot This commit updates the PE PuppetDB dependencies and adds support for the clj-parent project in pe-puppetdb-extensions. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6990) Unable to specify RPM with architecture in tag
Title: Message Title Moses Mendoza commented on PUP-6990 Re: Unable to specify RPM with architecture in tag thanks for filing this Jesse Hanley. any chance you could add the rpm you're using and maybe the output of your puppet run with --debug to the description? 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-6976) Scope effort to externalize Puppet report strings for translation
Title: Message Title Maggie Dreyer commented on PUP-6976 Re: Scope effort to externalize Puppet report strings for translation The next step is to identify which areas of the code base we should focus on in order to catch strings that are going to wind up in the report. I will use this doc to assemble the answer: https://docs.google.com/a/puppet.com/document/d/1aFtTMFp4tyvHMwVqG-3_33XgzTHtxOO1pVTBrJ4FFcg/edit?usp=sharing. 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-6980) Make the new lookup logic understand Hiera v3 configurations
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-6980 Make the new lookup logic understand Hiera v3 configurations 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-6992) Fix inconsistent autoload of environment functions and pcore types.
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-6992 Fix inconsistent autoload of environment functions and pcore types. Issue Type: Bug Affects Versions: PUP 4.8.1 Assignee: Unassigned Created: 2016/12/09 3:12 AM Fix Versions: PUP 4.9.0 Priority: Normal Reporter: Thomas Hallgren When a ruby function is declared in a func_name.rb file under the directory /lib/puppet/functions, the auto-loader makes it accessible using the global name "func_name". Declaring a puppet function in func_name.pp under /functions does however not work. The function is not found unless the name of the function is prefixed with "environment::". In contrast, if the ruby function is prefixed the same way, the function is no longer found unless it is also moved to /lib/puppet/functions/environment. For the sake of consistency, functions using global names should reside under: /lib/puppet/functions # ruby /functions # puppet and functions prefixed with "environment::" should reside under: /lib/puppet/functions/environment # ruby /functions/environment # puppet The same scheme should be used for auto-loading pcore types that are declared in the environment (but beneath the types directory instead of functions).
Jira (PDB-3222) stop testing multiple hosts/cell in PDB acceptance tests
Title: Message Title Wayne Warren commented on PDB-3222 Re: stop testing multiple hosts/cell in PDB acceptance tests Wyatt Alt this would be very helpful, yes... However I think converting the puppetdb pipeline to CI.Next directly from AWS, which we want to do anyway but keep getting slammed by infrastructure fires or the need to do important strategic work like working up estimates for our CI.Next mesos master needs, will allow y'all to begin using vmpooler templates even with PR testing. In CI.Next we pre-provision vmpooler nodes before the jenkins job that uses them actually leaves the queue and we use a more or less "capacity aware" resource allocator layer on top of vmpooler to do this so even relatively high-cadence pipelines like puppetdb's will not be able to "tip" vmpooler over...instead, jobs will sit in the queue waiting for vmpooler capacity to free up before being allowed to run. We already have work ticketed to do this migration; see QENG-4282 and QENG-4303 Because this is a busy PTO time of year and we have challenging WIP, it's hard to predicted exactly when we'll get to this work. For an idea of the magnitude of remaining CI.Next migration work done/notdone and how we've mapped it out, please see http://grafana.ops.puppetlabs.net/dashboard/db/cinext-jira-graph-and-progress 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-6951) No remount when mount transistions from “absent” or “unmounted”, respectively to “mounted”
Title: Message Title
Jens Offenbach commented on PUP-6951
Re: No remount when mount transistions from “absent” or “unmounted”, respectively to “mounted”
Sorry for the delay, I was in trouble with migrating our test cloud to OpenStack Newton. Now everything seems to be up and running. The problem is that the mountpoint resource in the puppetlabs-mount_providers module cannot handle the fstype property. It must be specified in the mounttab resource. Replacing the mount resource by this:
mounttab{ "ceph::mounttab::${mountpoint}":
ensure => $ensure,
device => $device,
name => $mountpoint,
fstype => $fstype,
options => $options,
dump => $dump,
pass => $pass,
}
~>
