Jira (PUP-6545) Ruby 2.3 fails spec tests on Appveyor in Windows
Title: Message Title Glenn Sarti commented on PUP-6545 Re: Ruby 2.3 fails spec tests on Appveyor in Windows QA demo performed for Erick 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-6459) puppet resource service fails on Windows 10 Pro (x64)
Title: Message Title Moses Mendoza commented on PUP-6459 Re: puppet resource service fails on Windows 10 Pro (x64) Took a quick look at CI tonight and it appears this hasn't made it through the puppet-agent pipeline yet. As of this comment the last green run of https://jenkins.puppetlabs.com/view/puppet-agent/view/master/view/puppet-agent/job/platform_puppet-agent_intn-van-sys_suite-daily-puppet-master/ was 7/28 and this landed on 7/29 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-6483) "puppet resource user", when run in Windows creates a login attempt.
Title: Message Title Moses Mendoza assigned an issue to Ethan Brown Puppet / PUP-6483 "puppet resource user", when run in Windows creates a login attempt. Change By: Moses Mendoza Assignee: Ethan Brown 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-6483) "puppet resource user", when run in Windows creates a login attempt.
Title: Message Title Moses Mendoza commented on PUP-6483 Re: "puppet resource user", when run in Windows creates a login attempt. PR opened against Ethan Brown's branch: https://github.com/Iristyle/puppet/pull/4/files 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-6524) The shell used with exec resource provider=shell should be configurable
Title: Message Title
Adam Bottchen updated an issue
Puppet / PUP-6524
The shell used with exec resource provider=shell should be configurable
Change By:
Adam Bottchen
Customer found that when creating an exec resource, they are unable to run commands with bash builtins process substitions . For example:{code:java}class exectest { exec{'run if different':provider => 'shell',command => '/bin/echo "they are different" > test.log',onlyif => "/usr/bin/test `/usr/bin/diff <(printf 'abc') <(printf 'xyz') | grep '' -c` -gt 0", }}{code}will fail to parse:{code:java}# puppet apply -td -e "include exectest"...Debug: Exec[run if different](provider=shell): Executing check '["/bin/sh", "-c", "/usr/bin/test `/usr/bin/diff <(printf 'abc') <(printf 'xyz') | grep '' -c` -gt 0"]'Debug: Executing '/bin/sh -c /usr/bin/test `/usr/bin/diff <(printf 'abc') <(printf 'xyz') | grep '' -c` -gt 0'Debug: /Stage[main]/Exectest/Exec[run if different]/onlyif: /bin/sh: command substitution: line 0: syntax error near unexpected token `('Debug: /Stage[main]/Exectest/Exec[run if different]/onlyif: /bin/sh: command substitution: line 0: `/usr/bin/diff <(printf 'abc') <(printf 'xyz') | grep '' -c'Debug: /Stage[main]/Exectest/Exec[run if different]/onlyif: /usr/bin/test: missing argument after `0'...{code}This is due to the fact that https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/exec/shell.rb#L19 forces the /bin/sh shell, which cannot parse the bash builtins process substitutions . This is true even on EL systems where /bin/sh is linked to /bin/bash.Customer would like to see the shell used by provider=shell be configurable instead of hardcoded to avoid this issue.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (FACT-1361) Create networking fact acceptance test
Title: Message Title Michael Smith commented on FACT-1361 Re: Create networking fact acceptance test I created this ticket because I figured the networking tests were pretty much the same across all platforms. https://github.com/puppetlabs/facter/blob/master/acceptance/tests/facts/ubuntu.rb#L87-L97 and https://github.com/puppetlabs/facter/blob/master/acceptance/tests/facts/el.rb#L89-L98 are pretty much identical. If we need to special case a few (I'm not sure why dhcp is missing on el), that's fine, but it should mostly be platform-agnostic. 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-1361) Create networking fact acceptance test
Title: Message Title Phong Ly commented on FACT-1361 Re: Create networking fact acceptance test Sorry my question above wasn't clear, yes, that was what I meant, a single test file, for example facter/acceptance/tests/ticket_13651_networking_fact_tests.rb or facter/acceptancetests/facts/networking_facts.rb, will have test for all platforms. In that single acceptance test, there will be something like: agents.each do |agent| if agent['platform'] =~ /debian/ run all networking fact tests for debian if agent['platfrom']=~/ubuntu/ run all networking fact tests for ubuntu end 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-1271) Generate message catalogs, review and mark translatable strings
Title: Message Title Andrew Henroid assigned an issue to Andrew Henroid Facter / FACT-1271 Generate message catalogs, review and mark translatable strings Change By: Andrew Henroid Assignee: Andrew Henroid 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-1361) Create networking fact acceptance test
Title: Message Title Michael Smith commented on FACT-1361 Re: Create networking fact acceptance test Kind of; we should pull out the networking portion of all the tests in acceptance/tests/facts into a single acceptance test (rather than duplicating it in all the platform-specific tests). We did something similar for Ruby facts. 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 (PDOC-86) Make Markdown the default format
Title: Message Title Trevor Vaughan commented on PDOC-86 Re: Make Markdown the default format I'd just like to ask if this is a good idea. The main reason is that approx 2 years ago, Strings was going to be the new hotness so we all started converting our code to something that was YARD/Strings compatible. Now, we're going back to Markdown (which is abysmal by the way). The @param and @example functionality of YARD is good and I don't replacing this with Markdown in a way that is not going to be more trouble than it is worth. 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-1361) Create networking fact acceptance test
Title: Message Title Phong Ly commented on FACT-1361 Re: Create networking fact acceptance test Michael Smith I am trying to understand this ticket, did you mean that we should have only one test file, for example 'facter/acceptance/tests/ticket_13651_networking_fact_tests.rb', to replace all tests under https://github.com/puppetlabs/facter/tree/master/acceptance/tests/facts? 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-6530) create_resources() doesn't include the file or line reference in resources it creates
Title: Message Title Henrik Lindberg commented on PUP-6530 Re: create_resources() doesn't include the file or line reference in resources it creates I confirmed manually that create_resources after the changes made in PUP-5949 that the catalog now has file/line information for resources created via create_resources (the file/line where the call to create_resources is made is used for all resources created by that call). Will now write some tests. 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 Michael Smith updated an issue Facter / FACT-1405 Facter does not like next hop flags in ip route output Change By: Michael Smith Fix Version/s: FACT 3.4.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-6570) pe_acceptance tests fail in Non-English Windows
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-6570 pe_acceptance tests fail in Non-English Windows Change By: Glenn Sarti Sprint: Windows 2016-08-10 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-6570) pe_acceptance tests fail in Non-English Windows
Title: Message Title Glenn Sarti created an issue Puppet / PUP-6570 pe_acceptance tests fail in Non-English Windows Issue Type: Bug Assignee: Glenn Sarti Components: Windows Created: 2016/08/01 2:20 PM Priority: Normal Reporter: Glenn Sarti During the validation of MODULES-3636 it was found that some tests have hardcoded english-only tests e.g. assert_match(/The Marionette Collective Server service was stopped successfully/, result.stdout, "Failed to stop MCollective service") https://github.com/puppetlabs/pe_acceptance_tests/blob/2016.3.x/acceptance/tests/pe_checks/QA-563_windows_exit_mcollective.rb#L13 https://github.com/puppetlabs/pe_acceptance_tests/blob/2016.3.x/acceptance/tests/pe_checks/QA-563_windows_exit_mcollective.rb#L13 This results in failures on French windows;
Jira (PUP-6570) pe_acceptance tests fail in Non-English Windows
Title: Message Title Glenn Sarti commented on PUP-6570 Re: pe_acceptance tests fail in Non-English Windows Cloning from PE ticket for Puppet fix. These test were migrated to Puppet but had not yet been deleted from PE 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-6558) Regression: Puppet unable to load PE Trapperkeeper::Orchestrator type, breaking PE installation
Title: Message Title David Kramer updated an issue Puppet / PUP-6558 Regression: Puppet unable to load PE Trapperkeeper::Orchestrator type, breaking PE installation Change By: David Kramer Fix Version/s: PUP 4.6.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-6397) File autorequire in Mount causes dependency loops
Title: Message Title Paul Anderson commented on PUP-6397 Re: File autorequire in Mount causes dependency loops I like Matt's Proposal because it would allow someone to describe the proper state of a mounted filesystem and have it implemented in a single puppet run. I don't want to overthink the issue, but there's one potentially unresolved issue: Should it be possible to set the permissions of the directory BEFORE it is mounted and the final permissions are set? For instance, an admin may want to make sure that a directory has very restrictive permissions before it is mounted so that if the mounting were to fail, or if there were an unexpected ordering issue, files wouldn't get written to the local file system. Only after the mount happened would less restrictive permissions be set. 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-6569) Improve error messaging for Windows user management
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-6569 Improve error messaging for Windows user management Change By: Rob Reynolds Labels: type_user windows 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-6569) Improve error messaging for Windows user management
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-6569 Improve error messaging for Windows user management Change By: Rob Reynolds Component/s: Windows Component/s: Types and Providers 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-6568) launchd service provider crashes if a non-text or binary plist file in {System,}/Library/Launch{Daemons,Agents} directory exists
Title: Message Title
Clay Caviness commented on PUP-6568
Re: launchd service provider crashes if a non-text or binary plist file in {System,}/Library/Launch{Daemons,Agents} directory exists
I think this PR fixes it
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-6569) Improve error messaging for Windows user management
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6569 Improve error messaging for Windows user management Change By: Moses Mendoza Sprint: Windows Triage 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-6569) Improve error messaging for Windows user management
Title: Message Title Moses Mendoza created an issue Puppet / PUP-6569 Improve error messaging for Windows user management Issue Type: Task Assignee: Unassigned Created: 2016/08/01 12:44 PM Priority: Normal Reporter: Moses Mendoza While investigating PUP-6483, we found that we could be more specific with our error handling when performing some user password management tasks on Windows. Per Rob Reynolds in PUP-6483: A few error codes we could explore handling some of the errors and providing better messages around how to correct. Possibly as a separate ticket though. https://msdn.microsoft.com/en-us/library/windows/desktop/ms681385(v=vs.85).aspx * ERROR_LAST_ADMIN - 1322 (0x52A) - This operation is disallowed as it could result in an administration account being disabled, deleted or unable to log on. * ERROR_WRONG_PASSWORD - 1323 (0x52B) - Unable to update the password. The value provided as the current password is incorrect.
Jira (PUP-6483) "puppet resource user", when run in Windows creates a login attempt.
Title: Message Title Moses Mendoza commented on PUP-6483 Re: "puppet resource user", when run in Windows creates a login attempt. Rob Reynolds - agreed on improving the error handling to check for those codes and surface this info to the user. Per conversation, filed as https://tickets.puppetlabs.com/browse/PUP-6569 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-6568) launchd service provider crashes if a non-text or binary plist file in {System,}/Library/Launch{Daemons,Agents} directory exists
Title: Message Title
Clay Caviness updated an issue
Puppet / PUP-6568
launchd service provider crashes if a non-text or binary plist file in {System,}/Library/Launch{Daemons,Agents} directory exists
Change By:
Clay Caviness
If a file in the LaunchAgents or LaunchDaemons paths is encountered that's not:* a plain text file (plist or not)* a binary plist file (magic 'bplist00')then Puppet will crash with an error.To reproduce:{code}# cp /bin/ls /Library/LaunchDaemons# puppet resource serviceError: Could not run: invalid byte sequence in UTF-8{code}In [plist.rb line 34|https://github.com/puppetlabs/puppet/blob/ed209118fceb6433b51c88c10883cb7415b36adb/lib/puppet/util/plist.rb#L34] there's a check if it’s a binary plist or not.In the case of a binary blob that's on a binary plist, this will fail, and fall through to [parse_plist on line 55|https://github.com/puppetlabs/puppet/blob/ed209118fceb6433b51c88c10883cb7415b36adb/lib/puppet/util/plist.rb#L55], which tries to check the file's contents against the {{bad_xml_doctype]} regex.This fails because of the encoding.I expect the correct course of action is to handle the {{ArgumentError}} and return {{nil}}
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
Jira (PUP-6568) launchd service provider crashes if a non-text or binary plist file in {System,}/Library/Launch{Daemons,Agents} directory exists
Title: Message Title
Clay Caviness created an issue
Puppet / PUP-6568
launchd service provider crashes if a non-text or binary plist file in {System,}/Library/Launch{Daemons,Agents} directory exists
Issue Type:
Bug
Affects Versions:
PUP 4.5.2
Assignee:
Unassigned
Created:
2016/08/01 12:25 PM
Environment:
OS X 10.11.6 Puppet 4.5.2
Priority:
Normal
Reporter:
Clay Caviness
If a file in the LaunchAgents or LaunchDaemons paths is encountered that's not:
a plain text file (plist or not)
a binary plist file (magic 'bplist00')
then Puppet will crash with an error.
To reproduce:
Jira (PUP-6453) Produced capabilities are evaluated before the component
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-6453 Produced capabilities are evaluated before the component Change By: Alex Dreyer Sprint: bugs under investigation 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-6567) Test failure: /spec/unit/face/generate_spec.rb:149
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-6567 Test failure: /spec/unit/face/generate_spec.rb:149 Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-6483) "puppet resource user", when run in Windows creates a login attempt.
Title: Message Title Rob Reynolds commented on PUP-6483 Re: "puppet resource user", when run in Windows creates a login attempt. A few error codes we could explore handling some of the errors and providing better messages around how to correct. Possibly as a separate ticket though. https://msdn.microsoft.com/en-us/library/windows/desktop/ms681385(v=vs.85).aspx * ERROR_LAST_ADMIN - 1322 (0x52A) - This operation is disallowed as it could result in an administration account being disabled, deleted or unable to log on. * ERROR_WRONG_PASSWORD - 1323 (0x52B) - Unable to update the password. The value provided as the current password is incorrect. * ERROR_ILL_FORMED_PASSWORD - 1324 (0x52C) - Unable to update the password. The value provided for the new password contains values that are not allowed in passwords. * ERROR_PASSWORD_RESTRICTION - 1325 (0x52D) - Unable to update the password. The value provided for the new password does not meet the length, complexity, or history requirements of the domain. * ERROR_LOGON_FAILURE - 1326 (0x52E) - The user name or password is incorrect. * ERROR_ACCOUNT_RESTRICTION - 1327 (0x52F) - Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced. * ERROR_INVALID_LOGON_HOURS - 1328 (0x530) - Your account has time restrictions that keep you from signing in right now.
Jira (PUP-6567) Test failure: /spec/unit/face/generate_spec.rb:149
Title: Message Title Henrik Lindberg commented on PUP-6567 Re: Test failure: /spec/unit/face/generate_spec.rb:149 Problem was caused by a test that assumed that Puppet::FileSystem.children returned files in a particular order. That is not true on all platforms. The test was updated to sort the return before comparing against the expected result. Update pushed directly to master without review (adding .sort before comparing. 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-6567) Test failure: /spec/unit/face/generate_spec.rb:149
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Merged to master at: 582d87f7c17c8c87e8ded836c89b65015e4e041a Puppet / PUP-6567 Test failure: /spec/unit/face/generate_spec.rb:149 Change By: Henrik Lindberg Assignee: Henrik Lindberg Scope Change Category: Found Scope Change Reason: CI blocker Story Points: 1 Release Notes Summary: problem introduced and fixed before release Sprint: Language 2016-08-10 (3rd 1.6.0 Scrum Team: Language Release Notes: Not Needed Fix Version/s: PUP 4.6.0
Jira (PUP-6558) Regression: Puppet unable to load PE Trapperkeeper::Orchestrator type, breaking PE installation
Title: Message Title William Hopper commented on PUP-6558 Re: Regression: Puppet unable to load PE Trapperkeeper::Orchestrator type, breaking PE installation Another note: if you find yourself needing to use a different puppet-agent package for testing, you can hack it into the tarball by following the steps from this gist: https://gist.github.com/whopper/1accc14526cb767db71686bb3646ad97 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-907) cfacter doesn't implement :timeout
Title: Message Title Jorie Tappa updated an issue Facter / FACT-907 cfacter doesn't implement :timeout Change By: Jorie Tappa Labels: cfact docs_reviewed 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-6553) Environment compiler and app_management language need to support hiera lookups
Title: Message Title Ryan Coleman updated an issue Puppet / PUP-6553 Environment compiler and app_management language need to support hiera lookups Change By: Ryan Coleman Issue Type: Bug Improvement 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-1368) Windows output does not correctly print unicode snowman
Title: Message Title
Michael Smith updated an issue
Facter / FACT-1368
Windows output does not correctly print unicode snowman
Change By:
Michael Smith
In Powershell ISE (because the powershell console sucks for unicode support){code}PS C:\Users\lasth> chcp 65001Active code page: 65001PS C:\Users\lasth> $env:FACTER_snowman☃PS C:\Users\lasth> facter snowman☃{code} Note that code page 65001 is the Windows code page for UTF-8.
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-6541) Acceptance: Validate sensitive data type
Title: Message Title David Kramer updated an issue Puppet / PUP-6541 Acceptance: Validate sensitive data type Change By: David Kramer Fix Version/s: PUP 4.6.0 Fix Version/s: PUP 4.7.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-6541) Acceptance: Validate sensitive data type
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-6541 Acceptance: Validate sensitive data type Change By: John Duarte Assignee: Eric Sorenson John Duarte 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-6414) Update forgeapi.puppetlabs.com to forgeapi.puppet.com
Title: Message Title John Duarte commented on PUP-6414 Re: Update forgeapi.puppetlabs.com to forgeapi.puppet.com This is unblocked and could be pulled in after the 4.6.0 release. 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-6414) Update forgeapi.puppetlabs.com to forgeapi.puppet.com
Title: Message Title John Duarte updated an issue Puppet / PUP-6414 Update forgeapi.puppetlabs.com to forgeapi.puppet.com Change By: John Duarte Fix Version/s: PUP 4.y 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-1458) Allow setting existing facter config flags from the config file
Title: Message Title David Kramer updated an issue Facter / FACT-1458 Allow setting existing facter config flags from the config file Change By: David Kramer Fix Version/s: FACT 3.4.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 (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title David Kramer updated an issue Facter / FACT-718 Allow for disabling certain facts within Facter Change By: David Kramer Fix Version/s: FACT 3.4.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-6459) puppet resource service fails on Windows 10 Pro (x64)
Title: Message Title Ethan Brown commented on PUP-6459 Re: puppet resource service fails on Windows 10 Pro (x64) This ran through to completion in CI as part of https://jenkins.puppetlabs.com/view/puppet-agent/view/master/view/puppet/job/platform_puppet_pkg-van-promote_master/278/ 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-6545) Ruby 2.3 fails spec tests on Appveyor in Windows
Title: Message Title Ethan Brown assigned an issue to Erick Banks Puppet / PUP-6545 Ruby 2.3 fails spec tests on Appveyor in Windows Change By: Ethan Brown Assignee: qa Erick Banks 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-6545) Ruby 2.3 fails spec tests on Appveyor in Windows
Title: Message Title Ethan Brown assigned an issue to qa Puppet / PUP-6545 Ruby 2.3 fails spec tests on Appveyor in Windows Change By: Ethan Brown Status: Ready for CI Test Assignee: Ethan Brown qa 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-5501) basic_install.rb and with_version.rb module tests fail in AIX
Title: Message Title John Duarte commented on PUP-5501 Re: basic_install.rb and with_version.rb module tests fail in AIX Pending release of Beaker 2.49.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-5040) Add agent-on-master configuration to Puppet AIO CI
Title: Message Title John Duarte commented on PUP-5040 Re: Add agent-on-master configuration to Puppet AIO CI Josh Cooper, you are correct, thanks. Ruth Linehan, I will submit a PR to address this. 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 (PDB-2929) Update dujour to notify users to use 4.2.0 (PDB 4.2.0)
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2929 Update dujour to notify users to use 4.2.0 (PDB 4.2.0) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/08/01 9:39 AM Priority: Normal Reporter: Andrew Roetker (Initial planned release date: 2016-08-08) Update dujour to notify users to use 4.2.0. Dependencies: Packages pushed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-2925) Push tag (PDB 4.2.0)
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2925 Push tag (PDB 4.2.0) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/08/01 9:39 AM Priority: Normal Reporter: Andrew Roetker (Initial planned release date: 2016-08-08) The development team is responsible for updating the stable/master branches as necessary. This will be done after the version bump in version.rb. Dependencies: Go / No Go meeting (except where it's required to push the tag to build packages - MSIs) Add Comment
Jira (PDB-2928) Send out announcements (PDB 4.2.0)
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2928 Send out announcements (PDB 4.2.0) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/08/01 9:39 AM Priority: Normal Reporter: Andrew Roetker (Initial planned release date: 2016-08-08) Morgan Rhodes: update the release google spreadsheet. Update the MSI build targets in the Puppet repo in ext/build_defaults.yaml. This needs to be done for any projects that are to get into the MSI (facter and hiera as of 8/2014) Send the drafted release notes email. If final send to puppet-announce and specific distribution lists (e.g. puppet to puppet-users & puppet-dev). If this release has security implications, also send the release announcement to puppet-security-announce Make a PSA on IRC letting those kiddos know about the new release. Something along the lines of "PSA: facter 1.7.3 now available"
Jira (PDB-2922) Tag the release and create packages (PDB 4.2.0)
Title: Message Title
Andrew Roetker created an issue
PuppetDB / PDB-2922
Tag the release and create packages (PDB 4.2.0)
Issue Type:
Sub-task
Assignee:
Morgan Rhodes
Created:
2016/08/01 9:39 AM
Priority:
Normal
Reporter:
Andrew Roetker
(Initial planned release date: 2016-08-08)
Tag and create packages
Developer provides the SHA - Andrew Roetker - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb)
checkout the sha
Make sure you are about to tag the correct thing
Create the tag e.g.) git tag -s -u {GPG key}
-m "1.7.3" 1.7.3
You need to know the pass phrase for this to complete successfully. It's important that we make sure all releases are signed to verify authenticity.
DO NOT push the tag to the repo, keep it local only
`git describe` will show you the tag. Make sure you're building what you think you're building.
Jira (PDB-2927) Docs pushed (PDB 4.2.0)
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2927 Docs pushed (PDB 4.2.0) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/08/01 9:39 AM Priority: Normal Reporter: Andrew Roetker (Initial planned release date: 2016-08-08) Push the documentation updates to docs.puppetlabs.com. Dependencies: Go / No Go meeting (Status - Ship it!) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-2930) Close all resolved tickets in Jira (PDB 4.2.0)
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2930 Close all resolved tickets in Jira (PDB 4.2.0) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/08/01 9:39 AM Priority: Normal Reporter: Andrew Roetker (Initial planned release date: 2016-08-08) Close any tickets that have been resolved for the release. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PDB%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%224.2.0%22%20AND%20status%20%3D%20Resolved There is a bulk edit at the top (a gear with the word "Tools"). Should you decide to take this route: Select Bulk Change - All # issues Step 1 - choose all relevant issues (likely all of them) Step 2 - Select "Transition Issues" Step 3 - Select "Closed" Step 4 - Select "Fixed" in Change Resolution. View what is about to change and confirm it. Then commit the change. Dependencies:
Jira (PDB-2924) Go/no-go meeting (before noon PST) (PDB 4.2.0)
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2924 Go/no-go meeting (before noon PST) (PDB 4.2.0) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/08/01 9:39 AM Priority: Normal Reporter: Andrew Roetker (Initial planned release date: 2016-08-08) This should happen Monday-Thursday, before 4pm. We should not be shipping anything after 4:00 PM or on a Friday both for our users, and because shipping takes time. Get a yes/no for the release from dev, docs, product, qa, releng. This meeting is informal, over chat, and usually happens right before packages are pushed. Keep in mind we typically do not ship releases in the evening and we don't ship on Friday if the release is a final release. Dependencies: Smoke testing Participants: Andrew Roetker Andrew Roetker Andrew Roetker Andrew Roetker Morgan Rhodes
Jira (PDB-2923) Smoke test packages (PDB 4.2.0)
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2923 Smoke test packages (PDB 4.2.0) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/08/01 9:39 AM Priority: Normal Reporter: Andrew Roetker (Initial planned release date: 2016-08-08) Procedure may vary by project and point in the release cycle. Ask around. In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master. Manual smoke testing can therefore be limited to other package formats than deb and rpm. For the Puppet gem, we don't yet have automated acceptance testing, so some quick manual smoke testing should always be performed. Platform packages express their dependencies differently than gems, so it's possible to encounter a situation where the build pipeline produced packages out of sync with the gems. Lighter testing of Z releases is acceptable. Add a link to the Packages repository that you receive from the "Tag and create packages" subtask Ping folks on your team for help with different platforms. When you pick up a platform, please leave a comment below that you are testing it. When it looks good, leave another comment, preferably with a code snippet showing the commands executed and their output.
Jira (PDB-2926) Packages pushed (PDB 4.2.0)
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2926 Packages pushed (PDB 4.2.0) Issue Type: Sub-task Assignee: Morgan Rhodes Created: 2016/08/01 9:39 AM Priority: Normal Reporter: Andrew Roetker (Initial planned release date: 2016-08-08) Push packages run `rake pl:jenkins:uber_ship` You will need the keys to the castle (aka the passphrase) for this to work. Don't forget to make sure everything looks like it's in the correct folder, the pkgs dir has been cleared out, and that you are shipping for all expected platforms. Get a second set of RelEng eyes on the packages that are about to be shipped to make sure everything looks a-okay. If you're shipping a gem you need to make sure you have a rubygems account, are an owner of that project, and have a gem config file. If you're shipping puppet you need to sign the MSI file for Windows. This is a manual process and the ship task doesn't ship or build the msi so talk to Moses or Haus for more details. This file also needs to be manually signed.
Jira (PDB-2919) Merge master into stable (PDB 4.2.0)
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2919 Merge master into stable (PDB 4.2.0) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/08/01 9:38 AM Priority: Normal Reporter: Andrew Roetker (Initial planned release date: 2016-08-08) For some releases, the code base will need to be merged down to stable. NOTE: This is usually only during a x.y.0 release, but even then it may have already been done. If it doesn't apply, close this ticket. Assuming you have origin (your remote) and upstream (puppetlabs remote), the commands will look something like this: git fetch upstream git rebase upstream/master
Jira (PDB-2915) puppetdb 4.2.0 2016-08-08 Release
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2915 puppetdb 4.2.0 2016-08-08 Release Issue Type: Task Assignee: Andrew Roetker Created: 2016/08/01 9:38 AM Priority: Normal Reporter: Andrew Roetker puppetdb 4.2.0 2016-08-08 Release When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. Only when those are done should you move the "Prepare notes" and "Tag release/create packages" tasks to Ready for Engineering. Ping those assigned to move forward. When you hear back for "Tag Release/create packages", you should move "Smoke test packages" to Ready for Engineering or In Progress if you are ready.
Jira (PDB-2917) Reconcile git commits and JIRA tickets (PDB 4.2.0)
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2917 Reconcile git commits and JIRA tickets (PDB 4.2.0) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/08/01 9:38 AM Priority: Normal Reporter: Andrew Roetker (Initial planned release date: 2016-08-08) Use the ticketmatch script to ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. cd ~/work git clone https://github.com/puppetlabs/ticketmatch cd ~/work/puppet # or whatever the repo is you're releasing from ruby ../ticketmatch/ticketmatch.rb Enter Git From Rev: 4.1.0 Enter Git To Rev: |master| stable Enter JIRA project: |PUP| Enter JIRA fix version: PUP 4.2.0 The output may contain the following headers: COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF ...) Lists git commits that don't have a corresponding ticket, at least not for the specified fix version. If the commit has a ticket, but the ticket is not targeted correctly, then the ticket's fixVersion should be updated. This can frequently happen if a ticket is initially targeted for a future release (master), but is pulled
Jira (PDB-2921) Prepare long form release notes and short form release story (PDB 4.2.0)
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2921 Prepare long form release notes and short form release story (PDB 4.2.0) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/08/01 9:39 AM Priority: Normal Reporter: Andrew Roetker (Initial planned release date: 2016-08-08) Collaborating with product for release story Dependencies: Reconcile git commits and JIRA tickets Add Comment This message was sent by
Jira (PDB-2920) Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.2.0)
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2920 Is the Jira tidy-up done for this release and prepared for the next one? (PDB 4.2.0) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/08/01 9:38 AM Priority: Normal Reporter: Andrew Roetker (Initial planned release date: 2016-08-08) This happens on Jira - we need to clean up the current release and prepare for the next release. Mark the version that's going out as "Released" in the Project Admin -> Versions panel. Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future) Create a public pair of queries for inclusion in the release notes/announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes slated for the next release (Paste their URLs into the "Release story" ticket): 'project = XX AND affectedVersion = 'X.Y.Z', Save as "Introduced in X.Y.Z", click Details, add permission for Everyone 'project = XX AND
Jira (PUP-6546) Hardcode library dependency environment variables
Title: Message Title Michael Smith commented on PUP-6546 Re: Hardcode library dependency environment variables I had a theory this was due to setting RUNPATH as well as RPATH. That doesn't appear to be the case with EL7 binaries. 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 (PDB-2916) Is the code ready for release? (PDB 4.2.0)
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2916 Is the code ready for release? (PDB 4.2.0) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/08/01 9:38 AM Priority: Normal Reporter: Andrew Roetker (Initial planned release date: 2016-08-08) If there are any version dependencies expressed in the code base, make sure these are up to date. For Puppet, make sure the shas used to build the MSI are correct. For Puppet-Server, make sure all references to the puppet version are correct. All tests (spec, acceptance) should be passing on all platforms for both stable & master. If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through spec/acceptance/etc. tests Move all items that should be moved from Ready for CI to Ready for Review Have all tickets been resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PDB%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%224.2.0%22
Jira (PDB-2918) Update version number in source (PDB 4.2.0)
Title: Message Title Andrew Roetker created an issue PuppetDB / PDB-2918 Update version number in source (PDB 4.2.0) Issue Type: Sub-task Assignee: Andrew Roetker Created: 2016/08/01 9:38 AM Priority: Normal Reporter: Andrew Roetker (Initial planned release date: 2016-08-08) Bump VERSION in lib/PDB/version.rb or project.clj to correct version. Commit the updated version file. e.g) commit -m "(packaging) Update FACTERVERSION to 1.7.3". If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask). Once this is done, hand the SHA to be built to RelEng to be tagged. Dependencies: Is the code ready for release? Reconcile git commits and JIRA tickets
Jira (PUP-6546) Hardcode library dependency environment variables
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-6546 Hardcode library dependency environment variables 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-6546) Hardcode library dependency environment variables
Title: Message Title Kylo Ginsberg commented on PUP-6546 Re: Hardcode library dependency environment variables Ping Michael Stahnke, Branan Riley, Michael Smith, who were hipchatting about how to address this the other day. 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-6459) puppet resource service fails on Windows 10 Pro (x64)
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-6459 puppet resource service fails on Windows 10 Pro (x64) Change By: Rob Reynolds Assignee: Moses Mendoza Rob Reynolds 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-6567) Test failure: /spec/unit/face/generate_spec.rb:149
Title: Message Title Hailee Kenney created an issue Puppet / PUP-6567 Test failure: /spec/unit/face/generate_spec.rb:149 Issue Type: CI Blocker Assignee: Unassigned Created: 2016/08/01 8:39 AM Priority: Normal Reporter: Hailee Kenney From Jenkins: 04:26:21 Failures: 04:26:21 04:26:21 1) Puppet::Face[:generate, v0.1.0] when used from an interactive terminal in an environment with two modules containing resource types creates output with matching names for each input 04:26:21 Failure/Error: expect(children).to eql(['test1.pp', 'test2.pp'])
Jira (PUP-6546) Hardcode library dependency environment variables
Title: Message Title
Adam Bottchen updated an issue
Puppet / PUP-6546
Hardcode library dependency environment variables
Change By:
Adam Bottchen
The Puppet code will generally fail if it picks up a dynamic library outside those provided in /opt/puppetlabs/puppet/lib. Unfortunately, when systems are configured with global LD_LIBRARY_PATH or LIBPATH environment variables, it becomes possible for Puppet, pxp-agent, or any other Puppet application to pick up third party versions or of libraries such as libssl, libcrypto, or libstdc++ and fail.This leads to errors such as:{code:java}# /opt/puppetlabs/bin/puppet config set server server.puppet.com --section agent It returns with the error: libfacter was not found. Please make sure it was installed to the expected location.{code}or{code:java}$ /opt/puppetlabs/puppet/bin/pxp-agent --foregroundCould not load program /opt/puppetlabs/puppet/bin/pxp-agent: Dependent module /opt/custom/lib/libstdc++.a(libstdc++.so.6) could not be loaded. The module has an invalid magic number{code}Although it may not be standard to hardcode these paths, since Puppet will fail if it picks up third party versions of these libraries this needs to be done. Either,1. The Puppet vendored library path should be hardcoded to prepend /opt/puppetlabs/puppet/lib in all Puppet applications to ensure the correct libraries are picked up.2. Puppet applications should unset LD_LIBRARY_PATH and LIBPATH to ensure third party libraries are not picked up.3. The vendored binaries included with Puppet should be statically linked so these environment variables do not matter.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-1591) isrequired not supported for newparam, newproperty (in types).
Title: Message Title Craig Dunn commented on PUP-1591 Re: isrequired not supported for newparam, newproperty (in types). Is there a more streamlined workaround for this yet or is Ben Ford's top level validate method (from the linked ticket) still the best way to define mandatory parameters? 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-5948) write tool to transform ruby resource type to pcore resource type
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-5948 write tool to transform ruby resource type to pcore resource type Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-5948) write tool to transform ruby resource type to pcore resource type
Title: Message Title Thomas Hallgren commented on PUP-5948 Re: write tool to transform ruby resource type to pcore resource type Merged to master at 97676bd. 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-5948) write tool to transform ruby resource type to pcore resource type
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5948 write tool to transform ruby resource type to pcore resource type Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren 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-5948) write tool to transform ruby resource type to pcore resource type
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5948 write tool to transform ruby resource type to pcore resource type Change By: Henrik Lindberg Assignee: Henrik Lindberg 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 (PDB-2669) Provide Official Docker PuppetDB
Title: Message Title Gareth Rushgrove commented on PDB-2669 Re: Provide Official Docker PuppetDB We now have Docker images available on Hub for various bits of Puppet software. You can find the images, including a PuppetDB image, at: https://hub.docker.com/u/puppet/ The tools used to build, including Dockerfiles, are in: https://github.com/puppetlabs/puppet-in-docker 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.
