Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
PUP 4.6.0
-
None
-
2
-
Client 2016-08-24, Client 2016-09-07
-
Bug Fix
-
Description
|
file { 'c:/tmp':
|
ensure => directory,
|
}
|
|
user { 'bob':
|
ensure => present,
|
groups => 'Users',
|
managehome => true,
|
password => "L0v3Pupp3t!"
|
}
|
|
acl { 'c:/tmp':
|
permissions => [
|
{ identity => 'bob', perm_type => 'allow', rights => ['modify'] },
|
],
|
}
|
The permissions property of acl is a hash type. This looks to be killing runs for anyone using acl or another type that has a parameter/property that is a hash type.
The contents of the transactionstore.yaml are as so:
---
|
resources:
|
File[c:/temp]:
|
parameters:
|
ensure:
|
system_value: :directory
|
File[c:/temp/deny_full_rights_dir]:
|
parameters:
|
ensure:
|
system_value: :directory
|
User[bob]:
|
parameters:
|
ensure:
|
system_value: :present
|
password:
|
system_value: L0v3Pupp3t!
|
groups:
|
system_value: BUILTIN\Users,Users
|
Acl[c:/temp/deny_full_rights_dir]:
|
parameters:
|
permissions:
|
system_value:
|
- !ruby/hash:Puppet::Type::Acl::Ace {}
|
inherit_parent_permissions:
|
system_value: :true
|
Attachments
Issue Links
- is cloned by
-
MODULES-11312 Corrective Change YAML file causes errors when type parameter is a complex type
-
- Closed
-
- is duplicated by
-
PUP-6630 Puppet-agent 4.6.0 throws transactionstore.yaml is corrupt with puppetlabs-acl module on Windows
-
- Closed
-
- relates to
-
MODULES-5051 ACL 2.0 doesn't work with corrective change
-
- Ready for Engineering
-
-
PCP-542 Console displays error about last_run_report.yaml could not be loaded with undefined class/module, after successfully applying a Puppet manifest
-
- Closed
-
-
MODULES-3766 ACL - ace should appear as a hash so it gets serialized/deserialized properly
-
- Ready for Engineering
-
-
PUP-6295 Include corrective_change field in reports
-
- Closed
-