Jira (PUP-6586) User resource always reports password changed when account disabled
Title: Message Title Glenn Sarti commented on PUP-6586 Re: User resource always reports password changed when account disabled Merged to master at; https://github.com/puppetlabs/puppet/commit/a0516659fc55a614984ed74cf68857aee9497d78 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-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title Glenn Sarti commented on PUP-6629 Re: Corrective Change YAML file causes errors when type parameter is a complex type Merged into master at; https://github.com/puppetlabs/puppet/commit/a0516659fc55a614984ed74cf68857aee9497d78 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-6623) Add function for unwrapping sensitive data
Title: Message Title Glenn Sarti commented on PUP-6623 Re: Add function for unwrapping sensitive data Merged to master at: https://github.com/puppetlabs/puppet/commit/a0516659fc55a614984ed74cf68857aee9497d78 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-6557) Dir.glob in Ruby 2.3 has changed behavior on Windows, can break code loading
Title: Message Title Glenn Sarti commented on PUP-6557 Re: Dir.glob in Ruby 2.3 has changed behavior on Windows, can break code loading Merged into stable at; https://github.com/puppetlabs/puppet/commit/1cf1ef7d032b44306578e114b8611bebad65663b Merged into master at; https://github.com/puppetlabs/puppet/commit/a0516659fc55a614984ed74cf68857aee9497d78 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-6586) User resource always reports password changed when account disabled
Title: Message Title Ethan Brown commented on PUP-6586 Re: User resource always reports password changed when account disabled Merged to stable in https://github.com/puppetlabs/puppet/commit/352dde3557a8ca1854f411501fefda7c3ffcd40e 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-6557) Dir.glob in Ruby 2.3 has changed behavior on Windows, can break code loading
Title: Message Title Glenn Sarti assigned an issue to Glenn Sarti Puppet / PUP-6557 Dir.glob in Ruby 2.3 has changed behavior on Windows, can break code loading Change By: Glenn Sarti Assignee: Glenn Sarti 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-6557) Dir.glob in Ruby 2.3 has changed behavior on Windows, can break code loading
Title: Message Title
Glenn Sarti commented on PUP-6557
Re: Dir.glob in Ruby 2.3 has changed behavior on Windows, can break code loading
Repro case:
Install Puppet Agent (This will setup the required directories etc.) Git clone puppet (Bundle install etc.) with Ruby 2.3.1
Install test fixture Copy "spec\fixtures\unit\functions\lookup\environments\production\modules\abc" to "C:\ProgramData\PuppetLabs\code\environments\production\modules\abc"
Modify Puppet Config (Use shortnames with two tildes) bundle exec puppet config set environmentpath C:/progra~3/puppet~1/code/environments
Create test manifest:
$test = abc::data()
notify{"#{$test}":}
Running without changes from https://github.com/puppetlabs/puppet/pull/5156
Expected result is Error in puppet run
Error: Evaluation Error: Unknown function: 'abc::data'. at C:/Source/. on node ...
Jira (PUP-6627) Puppet file `show_diff` setting leaks information
Title: Message Title Adrien Thebo updated an issue Puppet / PUP-6627 Puppet file `show_diff` setting leaks information Change By: Adrien Thebo Fix Version/s: PUP 4.6.1 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-2018) `puppet certificate generate` Generates Two CSRs in One Run
Title: Message Title Branan Riley updated an issue Puppet / PUP-2018 `puppet certificate generate` Generates Two CSRs in One Run Change By: Branan Riley Fix Version/s: PUP 4.y Fix Version/s: PUP 4.6.1 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
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] in PUP-6483:{quote}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{code}* 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.* ERROR_INVALID_WORKSTATION - 1329 (0x531) - This user isn't allowed to sign in to this computer.* ERROR_PASSWORD_EXPIRED - 1330 (0x532) - The password for this account has expired.* ERROR_ACCOUNT_DISABLED - 1331 (0x533) - This user can't sign in because this account is currently disabled.{code}{quote}*In Scope** Modify the Puppet Windows user provider or backing libs in puppet/util/windows to detect and surface some or all of the preceding errors to the user when applicable *Notes*From - https://github.com/puppetlabs/puppet/pull/5201#discussion_r75033133{{ERROR_ACCOUNT_LOCKED_OUT = 1909}} - is raised if account is locked out even when supplied login credentials are validWith both {{ERROR_ACCOUNT_LOCKED_OUT = 1909}} and {{ERROR_ACCOUNT_EXPIRED = 1793}}, puppet will proceed to set the password anyway after failed logon.Both of these (and probably others) are cases we could improve on... for example, puppet should not try to set passwords for expired or locked out accounts, and possibly should log a debug message that this was encountered?
Add Comment
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 Sprint: Client 2016-08-24 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 The certificate issue on the test forge has been corrected. I have submitted PR 5223 to revert the revert of this change in order to reinstate the improvement. This change has be smoke tested against the test forge on RHEL-7 and OSX-1011 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-6608) variable scoping change in Puppet 4.6.0
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6608 variable scoping change in Puppet 4.6.0 Change By: Henrik Lindberg Release Notes Summary: A regression in evaluation of resource like class inclusion caused evaluation of the class to be lazy as opposed to the correct immediate evaluation. This in turn led to problems with missing variables which in turn could lead to other problems. The order of evaluation is now restored. Release Notes: Bug Fix 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-6582) The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart"
Title: Message Title Peter Huene assigned an issue to Unassigned Puppet / PUP-6582 The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart" Change By: Peter Huene Assignee: Peter Huene 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-2993) Convert command :attempts from strings to a list of exceptions
Title: Message Title Rob Browning created an issue PuppetDB / PDB-2993 Convert command :attempts from strings to a list of exceptions Issue Type: Improvement Assignee: Unassigned Created: 2016/08/19 2:35 PM Priority: Normal Reporter: Rob Browning 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
Jira (PUP-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title Rob Reynolds commented on PUP-6629 Re: Corrective Change YAML file causes errors when type parameter is a complex type Merged into stable at https://github.com/puppetlabs/puppet/commit/9f1eb723bf64603dacc70c993a3fbb8905fb51b7 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-6638) create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x
Title: Message Title Michael Smith commented on PUP-6638 Re: create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x I don't believe so, we only test upgrades from our own yum/apt repos. 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-6638) create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x
Title: Message Title Brandon High commented on PUP-6638 Re: create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x Kylo Ginsberg Upgrades from distro packages are not tested by PE (as https://tickets.puppetlabs.com/browse/PE-15373 demonstrates) but I'm pretty sure upgrades from distro packages to PC1 packages are supported/tested? Michael Smith is that accurate? 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-6641) Integration test for Windows service fails on Windows 10
Title: Message Title Glenn Sarti created an issue Puppet / PUP-6641 Integration test for Windows service fails on Windows 10 Issue Type: Bug Assignee: Unassigned Created: 2016/08/19 2:06 PM Priority: Normal Reporter: Glenn Sarti ./spec/integration/provider/service/windows_spec.rb:33 uses the lmhosts service to test whether the service is enabled. However in Windows 10 the service startup type of lmhosts has changed to Manual (Trigger Start). This means the test will fail because it expects the service to be of type Automatic. This changed from Windows 8 to Windows 10. Unsure on the status for Windows Server. I also believe that lmhosts will not be available on Nano Server (Could be wrong on that). This test should be changed to not depend on the lmhosts having a startup type of Automatic. Add Comment
Jira (PUP-6628) Corrective change should use property values directly, bypassing any munging
Title: Message Title John Duarte updated an issue Puppet / PUP-6628 Corrective change should use property values directly, bypassing any munging Change By: John Duarte QA Risk Assessment: Medium 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-6628) Corrective change should use property values directly, bypassing any munging
Title: Message Title John Duarte updated an issue Puppet / PUP-6628 Corrective change should use property values directly, bypassing any munging Change By: John Duarte QA Status: 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-6628) Corrective change should use property values directly, bypassing any munging
Title: Message Title John Duarte commented on PUP-6628 Re: Corrective change should use property values directly, bypassing any munging Validated using pre-release version of puppet-agent at SHA cd3af7c containing puppet at SHA 738a8d7 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-6628) Corrective change should use property values directly, bypassing any munging
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-6628 Corrective change should use property values directly, bypassing any munging Change By: John Duarte Assignee: qa 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-6586) User resource always reports password changed when account disabled
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6586 User resource always reports password changed when account disabled Change By: Kenn Hussey Flagged: Impediment 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-6557) Dir.glob in Ruby 2.3 has changed behavior on Windows, can break code loading
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6557 Dir.glob in Ruby 2.3 has changed behavior on Windows, can break code loading Change By: Kenn Hussey Flagged: Impediment 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-6628) Corrective change should use property values directly, bypassing any munging
Title: Message Title
Branan Riley updated an issue
Puppet / PUP-6628
Corrective change should use property values directly, bypassing any munging
Change By:
Branan Riley
Acceptance Criteria:
It should be possible to apply the two following manifests in sequence without Puppet apply failing with an error , and the report should indicate that it was NOT a corrective change, since the manifest has changed : {noformat}group { 'bar': ensure => present}user { 'foo': ensure => present, membership => inclusive, groups => ['bar']}{noformat}{noformat}group { 'bar': ensure => present}group { 'baz': ensure => present}user { 'foo': ensure => present, membership => inclusive, groups => ['bar', 'baz']}{noformat} {noformat} User[foo]: !ruby/object:Puppet::Resource::Statustitle: foofile: "/home/branan/proj/pl/puppet/test.pp"line: 9resource: User[foo]resource_type: Usercontainment_path:- Stage[main]- Main- User[foo]evaluation_time: 0.033121403tags:- user- foo- classtime: '2016-08-19T12:41:22.752345544-07:00'failed: falsechanged: trueout_of_sync: trueskipped: falsechange_count: 1out_of_sync_count: 1events:- !ruby/object:Puppet::Transaction::Event audited: false property: groups previous_value: - baz desired_value: bar,baz historical_value: message: groups changed 'baz' to ['bar', 'baz'] name: :groups_changed status: success time: 2016-08-19 12:41:22.752746299 -07:00 redacted: corrective_change: falsecorrective_change: false{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6628) Corrective change should use property values directly, bypassing any munging
Title: Message Title Branan Riley commented on PUP-6628 Re: Corrective change should use property values directly, bypassing any munging John Duarte Acceptance criteria added. It is essentially borrowed from the user report in PUP-6632 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-6628) Corrective change should use property values directly, bypassing any munging
Title: Message Title
Branan Riley updated an issue
Puppet / PUP-6628
Corrective change should use property values directly, bypassing any munging
Change By:
Branan Riley
Acceptance Criteria:
It should be possible to apply the two following manifests in sequence without Puppet apply failing with an error:{noformat}group { 'bar': ensure => present}user { 'foo': ensure => present, membership => inclusive, groups => ['bar']}{noformat}{noformat}group { 'bar': ensure => present}group { 'baz': ensure => present}user { 'foo': ensure => present, membership => inclusive, groups => ['bar', 'baz']}{noformat}
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-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title Ken Barber commented on PUP-6629 Re: Corrective Change YAML file causes errors when type parameter is a complex type We have a patch up here: https://github.com/puppetlabs/puppet/pull/5220 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-6621) Corrective Change in Puppet 4.6.0 incorrectly errors when custom types are incompatible with it
Title: Message Title John Duarte updated an issue Puppet / PUP-6621 Corrective Change in Puppet 4.6.0 incorrectly errors when custom types are incompatible with it Change By: John Duarte QA Risk Assessment Reason: Covered by existing acceptance tests in CI 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-6621) Corrective Change in Puppet 4.6.0 incorrectly errors when custom types are incompatible with it
Title: Message Title John Duarte updated an issue Puppet / PUP-6621 Corrective Change in Puppet 4.6.0 incorrectly errors when custom types are incompatible with it Change By: John Duarte QA Status: 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-6621) Corrective Change in Puppet 4.6.0 incorrectly errors when custom types are incompatible with it
Title: Message Title John Duarte updated an issue Puppet / PUP-6621 Corrective Change in Puppet 4.6.0 incorrectly errors when custom types are incompatible with it Change By: John Duarte QA Risk Assessment: Low 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-6628) Corrective change should use property values directly, bypassing any munging
Title: Message Title John Duarte commented on PUP-6628 Re: Corrective change should use property values directly, bypassing any munging Branan Riley, can you provide an acceptance criteria example for 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 (PUP-6557) Dir.glob in Ruby 2.3 has changed behavior on Windows, can break code loading
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6557 Dir.glob in Ruby 2.3 has changed behavior on Windows, can break code loading Change By: Kenn Hussey Fix Version/s: PUP 4.6.2 Fix Version/s: PUP 4.6.1 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-6586) User resource always reports password changed when account disabled
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6586 User resource always reports password changed when account disabled Change By: Ethan Brown Fix Version/s: PUP 4.6.1 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-6586) User resource always reports password changed when account disabled
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-6586 User resource always reports password changed when account disabled Change By: Ethan Brown 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-6557) Dir.glob in Ruby 2.3 has changed behavior on Windows, can break code loading
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6557 Dir.glob in Ruby 2.3 has changed behavior on Windows, can break code loading Change By: Kenn Hussey Fix Version/s: PUP 4.6.z Fix Version/s: PUP 4.6.2 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6619) PUP ticket for adding tests for PA-466 ([regression] aio_agent_build, env_windows_installdir facts broken on Windows)
Title: Message Title
Ethan Brown commented on PUP-6619
Re: PUP ticket for adding tests for PA-466 ([regression] aio_agent_build, env_windows_installdir facts broken on Windows)
Puppet acceptance tests ran successfully at https://jenkins.puppetlabs.com/view/puppet-agent/view/stable/view/puppet/job/platform_puppet_intn-van-sys_stable/SLAVE_LABEL=beaker,TEST_TARGET=windows2012r2-64a/199/consoleFull
tests/windows/env_windows_installdir_fact.rb passed
The value retrieved for the fact env_windows_installdir is the desired value C:\Program Files\Puppet Labs\Puppet on a 64-bit OS with 64-bit agent.
07:30:27 Begin tests/windows/env_windows_installdir_fact.rb
07:30:27
07:30:27 PA-466: Ensure env_windows_installdir fact is present and correct
07:30:27
07:30:27 * test for presence/accuracy of fact on atkmhzhs92fa6w6.delivery.puppetlabs.net
07:30:27
07:30:27 atkmhzhs92fa6w6.delivery.puppetlabs.net (windows2012r2-64-1) 07:30:27$ cmd.exe /c puppet facts --render-as json
07:30:28 {"name":"atkmhzhs92fa6w6.delivery.puppetlabs.net","values":{"agent_specified_environment":"production","aio_agent_version":"1.6.0.34","architecture":"x64","dhcp_servers":{"Ethernet":"10.32.22.10","system":"10.32.22.10"},"dmi":{"manufacturer":"Phoenix Technologies
Jira (PUP-6619) PUP ticket for adding tests for PA-466 ([regression] aio_agent_build, env_windows_installdir facts broken on Windows)
Title: Message Title Ethan Brown assigned an issue to Erick Banks Puppet / PUP-6619 PUP ticket for adding tests for PA-466 ([regression] aio_agent_build, env_windows_installdir facts broken on 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-6620) Ensure test setup doesn't mask test failure of PMT to connect to Forge
Title: Message Title Ethan Brown commented on PUP-6620 Re: Ensure test setup doesn't mask test failure of PMT to connect to Forge Manual validation has shown that this removal of the pre-suite step to install certs on Windows will successfully demonstrate test failures related to connecting to the forge over HTTPS, when the cert bundle from the puppet-agent / Vanagon builds is not included or configured properly. I have additionally validated that in the last passing test run over packages at https://jenkins.puppetlabs.com/view/puppet-agent/view/stable/view/puppet/job/platform_puppet_intn-van-sys_stable/SLAVE_LABEL=beaker,TEST_TARGET=windows2012r2-64a/199/consoleFull that the 070_InstallCACerts.rb pre-suite step is no longer run: 07:17:50 "pre_suite": [ 07:17:50 "setup/common/pre-suite/000-delete-puppet-when-none.rb", 07:17:50 "setup/aio/pre-suite/010_Install.rb", 07:17:50 "setup/aio/pre-suite/015_PackageHostsPresets.rb", 07:17:50 "setup/aio/pre-suite/020_InstallCumulusModules.rb", 07:17:50 "setup/aio/pre-suite/021_InstallAristaModule.rb", 07:17:50 "setup/common/pre-suite/025_StopFirewall.rb", 07:17:50 "setup/common/pre-suite/040_ValidateSignCert.rb",
Jira (PUP-6619) PUP ticket for adding tests for PA-466 ([regression] aio_agent_build, env_windows_installdir facts broken on Windows)
Title: Message Title Ethan Brown assigned an issue to qa Puppet / PUP-6619 PUP ticket for adding tests for PA-466 ([regression] aio_agent_build, env_windows_installdir facts broken on 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-6620) Ensure test setup doesn't mask test failure of PMT to connect to Forge
Title: Message Title Ethan Brown assigned an issue to Erick Banks Puppet / PUP-6620 Ensure test setup doesn't mask test failure of PMT to connect to Forge 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-6620) Ensure test setup doesn't mask test failure of PMT to connect to Forge
Title: Message Title Ethan Brown assigned an issue to qa Puppet / PUP-6620 Ensure test setup doesn't mask test failure of PMT to connect to Forge 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 (FACT-1490) Allow blocking collection of the facts associated with filesystem_resolver
Title: Message Title Maggie Dreyer created an issue Facter / FACT-1490 Allow blocking collection of the facts associated with filesystem_resolver Issue Type: Task Assignee: Maggie Dreyer Created: 2016/08/19 10:40 AM Fix Versions: FACT 3.5.0 Priority: Normal Reporter: Maggie Dreyer As a proof of concept for blocking facts by passing the blocklist into the resolver, allow blocking each of the various facts handled by the filesystem_resolver. Because this resolver maps to more than one top-level fact, it represents a more complicated case. In addition, blocking this resolver's facts (esp. mountpoints) has been specifically requested by customers. Add Comment
Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title Maggie Dreyer updated an issue Facter / FACT-718 Allow for disabling certain facts within Facter Change By: Maggie Dreyer Sprint: Client 2016-09-07 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 Maggie Dreyer updated an issue Facter / FACT-718 Allow for disabling certain facts within Facter Change By: Maggie Dreyer Sprint: Client 2016-08-24 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-6640) The function generate() should merge stdout and stdin
Title: Message Title Chris Price commented on PUP-6640 Re: The function generate() should merge stdout and stdin Fabien Wernli great, thanks for filing 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 (PUP-6582) The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart"
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6582 The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart" Change By: Kenn Hussey Flagged: Impediment 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
John Duarte commented on PUP-6397
Re: File autorequire in Mount causes dependency loops
Validated using pre-release version of puppet-agent at SHA cd3af7c containing puppet at SHA 738a8d7.
Using the manifest from the acceptance criteria of this ticket, the catalog no longer results in a cyclic dependency.
root@tfoxaebkvjclhab:~# cat pup6397.pp
$_instance_path = '/opt/tomcat_myinstance'
mount { $_instance_path:
ensure => 'mounted',
device => '/dev/foo',
fstype => 'test',
}
tomcat::instance { 'myinstance':
Jira (PUP-6397) File autorequire in Mount causes dependency loops
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-6397 File autorequire in Mount causes dependency loops Change By: John Duarte Assignee: qa 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-6621) Corrective Change in Puppet 4.6.0 incorrectly errors when custom types are incompatible with it
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-6621 Corrective Change in Puppet 4.6.0 incorrectly errors when custom types are incompatible with it Change By: John Duarte Assignee: 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-6608) variable scoping change in Puppet 4.6.0
Title: Message Title John Duarte commented on PUP-6608 Re: variable scoping change in Puppet 4.6.0 Henrik Lindberg can we get a release note on this one? Thanks. 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-6622) Puppet function_loading benchmark performance degredation
Title: Message Title John Duarte assigned an issue to Unassigned Puppet / PUP-6622 Puppet function_loading benchmark performance degredation Change By: John Duarte 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-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title Ken Barber commented on PUP-6629 Re: Corrective Change YAML file causes errors when type parameter is a complex type Kenn Hussey understood, we have some partial fixes in already, there is a final patch/approach we are debating still that might not make it, we're just not sure if its a good idea to rush it yet. 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-6623) Add function for unwrapping sensitive data
Title: Message Title Henrik Lindberg commented on PUP-6623 Re: Add function for unwrapping sensitive data Merged to stable at: 2eabe4f 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-6640) The function generate() should merge stdout and stdin
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6640 The function generate() should merge stdout and stdin Change By: Henrik Lindberg Scrum Team: Puppet Server 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-2940) puppet query does not render UTF-8 characters correctly
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-2940 puppet query does not render UTF-8 characters correctly Change By: Wyatt Alt Assignee: Wyatt Alt 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-6617) puppet4 function generate() should throw exception when command fails
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6617 puppet4 function generate() should throw exception when command fails Change By: Henrik Lindberg Scrum Team: Puppet Server 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-6622) Puppet function_loading benchmark performance degredation
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6622 Puppet function_loading benchmark performance degredation Change By: Henrik Lindberg Release Notes Summary: Function loading and calling was hit by a performance regression that caused a 300% degradation in performance as observed by benchmarks. This is now fixed. Release Notes: Bug Fix 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-6574) Function call fails when using camel case for class names. It should be handled by puppet parser syntax validator
Title: Message Title John Duarte commented on PUP-6574 Re: Function call fails when using camel case for class names. It should be handled by puppet parser syntax validator Validated using pre-release version of puppet-agent at SHA cd3af7c containing puppet at SHA 738a8d7 Reproduction steps Create module Create module with sample code provided in the initial report. The module is named mytest in lowercase as per module documentation. Note: If the module name is in camel case, then the module itself will not be available for loading. Module layout # tree -a /etc/puppetlabs/code/environments/production/modules /etc/puppetlabs/code/environments/production/modules └── mytest ├── files │ ├── .zshrc │ └── .zshrc.dev ├── manifests │ ├── developer.pp │ └── init.pp
Jira (PUP-6582) The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart"
Title: Message Title Henrik Lindberg assigned an issue to Peter Huene Puppet / PUP-6582 The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart" Change By: Henrik Lindberg Assignee: Peter Huene 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-6613) regression: explicit undef cannot be used in create_resources
Title: Message Title Phong Ly assigned an issue to Phong Ly Puppet / PUP-6613 regression: explicit undef cannot be used in create_resources Change By: Phong Ly Assignee: qa Phong Ly 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-6622) Puppet function_loading benchmark performance degredation
Title: Message Title John Duarte assigned an issue to Ethan Brown Puppet / PUP-6622 Puppet function_loading benchmark performance degredation Change By: John Duarte 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-6574) Function call fails when using camel case for class names. It should be handled by puppet parser syntax validator
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-6574 Function call fails when using camel case for class names. It should be handled by puppet parser syntax validator Change By: John Duarte Assignee: qa 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-6640) The function generate() should merge stdout and stdin
Title: Message Title Fabien Wernli commented on PUP-6640 Re: The function generate() should merge stdout and stdin See https://tickets.puppetlabs.com/browse/PUP-6617 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-6622) Puppet function_loading benchmark performance degredation
Title: Message Title John Duarte commented on PUP-6622 Re: Puppet function_loading benchmark performance degredation Ethan Brown or Henrik Lindberg do we want a release note for this fix? 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-6622) Puppet function_loading benchmark performance degredation
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-6622 Puppet function_loading benchmark performance degredation Change By: John Duarte Status: Ready for CI Test Assignee: Henrik Lindberg 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-6613) regression: explicit undef cannot be used in create_resources
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-6613 regression: explicit undef cannot be used in create_resources Change By: John Duarte Status: Ready for CI Test Assignee: 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-6574) Function call fails when using camel case for class names. It should be handled by puppet parser syntax validator
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-6574 Function call fails when using camel case for class names. It should be handled by puppet parser syntax validator Change By: John Duarte Status: Ready for CI Test Assignee: 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-6638) create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x
Title: Message Title Kylo Ginsberg commented on PUP-6638 Re: create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x Nikolai R Kristiansen yes, since this is in the course of provisioning new machines, offhand I'd recommend simply starting those new machines out with a puppet-agent package. From that point on, you could do future upgrades via the puppetlabs-puppet_agent module and you'd be on a well-trodden path. Btw, this conversation is getting a bit OT for this ticket per se. Just as a heads up, you may get more interactive brainstorming from slack (signup at slack.puppet.com) or IRC (details at https://puppet.com/community). 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-1460) Load facter.conf when facter. is used as a library
Title: Message Title John Duarte assigned an issue to qa Facter / FACT-1460 Load facter.conf when facter. is used as a library Change By: John Duarte Status: Ready for CI Test Assignee: 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-6617) puppet4 function generate() should throw exception when command fails
Title: Message Title Fabien Wernli commented on PUP-6617 Re: puppet4 function generate() should throw exception when command fails https://tickets.puppetlabs.com/browse/PUP-6640 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-6629) Corrective Change YAML file causes errors when type parameter is a complex type
Title: Message Title Kenn Hussey commented on PUP-6629 Re: Corrective Change YAML file causes errors when type parameter is a complex type Ken Barber these changes need to get into a build by end of day today in order to make the cut for puppet-agent 1.6.1. 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-6640) The function generate() should merge stdout and stdin
Title: Message Title Fabien Wernli created an issue Puppet / PUP-6640 The function generate() should merge stdout and stdin Issue Type: Bug Affects Versions: PUP 4.5.3 Assignee: Unassigned Created: 2016/08/19 7:25 AM Environment: master Platform: CentOS 7.2.1511 Architecture: x86_64 Linux ccsvli80 3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux puppetserver --version puppetserver version: 2.4.0 puppetserver gem list Warning: The following options to parse-opts are unrecognized: :flag LOCAL GEMS *** collectd-dsl (0.3.6cc, 0.3.5) hiera-eyaml (2.1.0) hiera-eyaml-gpg (0.6) highline (1.6.21) jar-dependencies (0.1.13) jruby-openssl (0.9.7 java) json (1.8.0 java) mini_portile2 (2.1.0) rake (10.1.0) rdoc (4.1.2) ruby_gpg (0.3.2) trollop (2.1.2) uuidtools (2.1.5) agent Platform: CentOS 7.2.1511 Architecture: x86_64 Linux ccosvms0033 3.10.0-327.22.2.el7.x86_64 #1 SMP Thu Jun 23 17:05:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux rpm -q puppet puppet-3.7.2-1.el7.noarch Priority: Normal Reporter: Fabien Wernli description The function generate() does not merge stdout and stderr using a puppet4 master. It works as expected on a v3
Jira (PUP-6623) Add function for unwrapping sensitive data
Title: Message Title Kenn Hussey commented on PUP-6623 Re: Add function for unwrapping sensitive data Adrien Thebo these changes need to get into a build by end of day today in order to make the cut for puppet-agent 1.6.1. 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 Kenn Hussey updated an issue Puppet / PUP-6397 File autorequire in Mount causes dependency loops Change By: Kenn Hussey Flagged: Impediment 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-6628) Corrective change should use property values directly, bypassing any munging
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-6628 Corrective change should use property values directly, bypassing any munging Change By: John Duarte Status: Ready for CI Test Assignee: 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-6623) Add function for unwrapping sensitive data
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6623 Add function for unwrapping sensitive data Change By: Kenn Hussey Flagged: Impediment 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 John Duarte assigned an issue to qa Puppet / PUP-6397 File autorequire in Mount causes dependency loops Change By: John Duarte Status: Ready for CI Test Assignee: Branan Riley 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-6638) create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x
Title: Message Title Nikolai R Kristiansen commented on PUP-6638 Re: create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x Just a note on the upgrade path. We use pxe with preseed to install ubuntu on new desktops. The last step of the pxe-install is to install the distro version of puppet, and after the new node being autosigned, it should upgrade itself. Do you suggest installing the 4.x puppet-agent from puppetlabs directly instead? 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-6638) create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x
Title: Message Title Kylo Ginsberg commented on PUP-6638 Re: create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x Ping Brandon High or Michael Smith to see if anything comes to mind. One thought: this was using the puppetlabs-puppet_agent module to upgrade from a distro package of puppet 3.8 to latest puppet-agent 1.6 packages. I'm pretty sure that upgrades from distro packages are not an upgrade path that has been tested or is currently intended to work, so there might be gotchas there. 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-6582) The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart"
Title: Message Title Thomas Hallgren commented on PUP-6582 Re: The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart" And onward to master at 07ac2e9 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-6582) The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart"
Title: Message Title Thomas Hallgren commented on PUP-6582 Re: The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart" PR-5215 merged to stable at 368b65e 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-6639) Yumrepo can't work with files using spaces in their INI format
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6639 Yumrepo can't work with files using spaces in their INI format Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6582) The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart"
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-6582 The environment cache erroneously binds topscope and compilation gets values from "first compilation after restart" 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-6638) create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x
Title: Message Title Henrik Lindberg commented on PUP-6638 Re: create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x To me it sounds like you managed to get a mix of two versions and they clashed - a 3.x runtime started running 4.x code. 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-6638) create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x
Title: Message Title Nikolai R Kristiansen commented on PUP-6638 Re: create_resource in v4.6.0 makes puppet 3.x agents fail upgrade to 4.x Henrik Lindberg I see my understanding is lacking, of course it only runs master side. I can't test it right away, but this is probably happening because puppetserver was not upgraded to the latest version as the puppet-agent was. I'll post back. 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-6631) Apt package provider does not mark managed packages as manual
Title: Message Title Peter Kroon commented on PUP-6631 Re: Apt package provider does not mark managed packages as manual Ben Ford Thanks, but I already found that (man apt-mark), and fixed it for my specific situation. However, I think that's completely besides the point here: any package that should be installed (or latest) according to puppet should be marked as manual by puppet. Even if it's already installed automatically to satisfy dependencies. 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-6609) After a Debian puppet package upgrade, parameter error persists on dashboard
Title: Message Title Karoly Czovek commented on PUP-6609 Re: After a Debian puppet package upgrade, parameter error persists on dashboard Henrik Lindberg this is seems to a jessie/systemd incompatibility, once i killed all the old puppet agents, and restarted them on some test servers - and I could not reproduce the issue. Might be the package was failed to restart the running daemon but the underlaying files were changed. (we updated from 4.5 -> 4.6, but i guess at 4.6 the legacy sysV init scripts were translated to systemd config file in this release) The daemon now is running fine with --trace --verbose without errors on the selected test servers 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-6639) Yumrepo can't work with files using spaces in their INI format
Title: Message Title Benjamin Merot created an issue Puppet / PUP-6639 Yumrepo can't work with files using spaces in their INI format Issue Type: Bug Affects Versions: PUP 4.4.0 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2016/08/19 12:13 AM Environment: RHEL/CentOS/Fedora Priority: Normal Reporter: Benjamin Merot Yumrepo seems to work fine with YUM repository defined in '.repo' files as long as the INI styled file doesn't use spaces around equal signs. But if spaces around equal signs are used (and the 'redhat.repo' on RHEL does that), then the Yumrepo resource cannot manage settings for a repository. How it fails to do so seems to have changed since PUP-5682 , before 4.4.0 such repos were ignored, now Puppet tries to modify the value on every run like so:
