Ok, well, it was on one test computer. On others it's giving the same
error, but I think the parameter issue is actually specific to the existing
file / permissions. I moved the file and re-ran puppet, which as part of
the manifest re-created the file and could set permissions fine. It seems
like there is some issue with a certain permissions set that causes me
issues with ACL module. Specifically, the original file doesn't have any
user permissions set. I'm wondering if that is the issue?
On Monday, November 9, 2015 at 3:22:11 PM UTC-5, jmp242 wrote:
>
> Ok, sorry everyone for a false alarm. I finally figured this out -
> something I thought wouldn't be relevant at all, hence my failure to
> mention, but what happened is this. I have a module that is applied via the
> Forman ENC. It uses the acl module as a "puppet feature extension" (I don't
> know the official term for these sorts of forge modules). The ACL module is
> never applied to a host group or host via the Foreman "puppet classes". So
> I hadn't imported it into Foreman. This apparently is a problem. I was
> building a new module today, and happened to say "why not import the acl
> module while I'm here?" and did. Bam, ACL module now works.
>
> I apparently still don't totally understand how the ENC -> Puppet works
> wrt modules that aren't directly applied. Now in my notes for the future!
>
> On Wednesday, November 4, 2015 at 1:32:07 PM UTC-5, Rob Reynolds wrote:
>
>
>
> On Mon, Oct 19, 2015 at 10:10 AM, jmp242 <jp1...@gmail.com> wrote:
>
> Hmm, so on one test computer, the upgrade to puppet 3.8.3 fixed the issue.
> On the second test computer, it didn't - everything remains the same, but
> getting the same repeated ACE...
>
>
> What does 'cacls *folderlocation*' return?
>
>
>
>
> On Thursday, October 15, 2015 at 12:27:34 AM UTC-4, Rob Reynolds wrote:
>
>
>
> On Thu, Oct 1, 2015 at 8:09 AM, jmp242 <jp1...@gmail.com> wrote:
>
> Puppet 3.8.1 on Windows currently. puppet module list doesn't return
> anything for me. I'm downloading the zip file and unzipping the module into
> a folder. I then copy the folder into my local dev modules directory using
> Geppeto, and doing the same for any dependencies. I then check into our SVN
> the modules, and tag them with the version they are from forge if public,
> or an internal version for our custom modules. I then check out the tag or
> svn switch to the latest tag on the puppet server dev module directory.
>
>
> Ah okay. I'm wondering what might cause issues surrounding 3.8.1 and ACL
> provider. An ACE with the same structure 142 times though, I'm wondering if
> there is a memory issue there.
>
>
>
> On Wednesday, September 30, 2015 at 3:38:49 PM UTC-4, Rob Reynolds wrote:
>
> Thanks. I'm surprised that a 'puppet agent --trace --debug --verbose'
> didn't turn up any more information about the error.
>
> Can you remind me again what version of Puppet you have installed?
>
> And the modules, `puppet module list`. How are you installing these
> modules by the way?
>
> On Tue, Sep 29, 2015 at 2:43 PM, jmp242 <jp1...@gmail.com> wrote:
>
> Sure, that's perhaps misleading a little - our internal custom puppet
> module is called yum as it was created for EL6 first. When we got a package
> manager on Windows, i.e. chocolatey, it seemed to make sense to put it in
> the Windows section of the yum module. By that I mean we have a switch on
> kernel in our modules. Here's the complete module:
> class yum ($choco_repo_url, $choco_repo_name) {
> schedule { 'monday_updates':
> range => '22:00 - 12:00',
> weekday => 'Monday',
> }
>
> schedule { 'tuesday_updates':
> range => '10:00 - 12:00',
> weekday => 'Tuesday',
> }
>
> schedule { 'daily_updates':
> period => daily,
> range => '22:00-3:00',
> }
>
> define repo {
> file { "${title}":
> path => "/etc/yum.repos.d/${title}",
> source => "puppet:///modules/${caller_module_name}/${title}",
> ensure => 'present',
> owner => root,
> group => root,
> mode => "644",
> notify => Exec["yum-clean-all"],
> }
>
> }
>
> case $kernel {
> 'linux' : {
> package { 'yum': ensure => present, }
>
> package { 'yum-autoupdate': ensure => present, }
>
> repo { "sl-classe.repo": }
>
> file { "sl-classe-testing":
> content => template('yum/sl-classe-testing.repo.erb'),
> path => "/etc/yum.repos.d/sl-classe-testing.repo",
> owner => root,
> group => root,
> mode => 644,
> ensure => present,
> notify => Exec["yum-clean-all"],
> }
>
> file { "yum.conf":
> source => "puppet:///modules/yum/yum.conf",
> path => "/etc/yum.conf",
> owner => root,
> group => root,
> mode => 644,
> ensure => present,
> }
>
> file { "sl-lepp":
> path => "/etc/yum.repos.d/sl-lepp.repo",
> ensure => absent,
> }
>
> file { "sl-lepp-testing":
> path => "/etc/yum.repos.d/sl-lepp-testing.repo",
> ensure => absent,
> }
>
> exec { "yum-clean-all":
> command => "yum clean all",
> refreshonly => true,
> }
>
> case $operatingsystemmajrelease {
> '6' : {
> $sl6repos = ["devtoolset.repo", "sl-other.repo", "sl.repo"]
>
> repo { $sl6repos: }
>
> file { "softwarecollections":
> source => "puppet:///modules/yum/sl6-softwarecollections.repo"
> ,
> path => "/etc/yum.repos.d/softwarecollections.repo",
> owner => root,
> group => root,
> mode => 644,
> ensure => present,
> notify => Exec["yum-clean-all"],
> }
>
> exec { "yum-autoupdate":
> command => "mv /etc/cron.daily/yum-autoupdate
> /etc/cron.weekly/yum-autoupdate",
> onlyif => "[ -f /etc/cron.daily/yum-autoupdate ]",
> }
>
> file { "/etc/cron.daily/yum-autoupdate": ensure => absent, }
>
> file { "/etc/cron.weekly/yum-autoupdate": ensure => present, }
> Exec['yum-autoupdate'] -> File['/etc/cron.daily/yum-autoupdate']
> -> File['/etc/cron.weekly/yum-autoupdate']
>
> }
> '7' : {
> packages::removepackage { "yum-conf-sl7x": }
>
> $sl7repos = [
> "sl7-other.repo",
> "sl7.repo",
> "sl-extras.repo",
> "sl7-security.repo",
> "sl7-fastbugs.repo",
> "sl7-rolling.repo",
> "sl7-testing.repo"]
>
> repo { $sl7repos: }
>
> file { "softwarecollections":
> source => "puppet:///modules/yum/sl7-softwarecollections.repo"
> ,
> path => "/etc/yum.repos.d/sl-softwarecollections.repo",
> owner => root,
> group => root,
> mode => 644,
> ensure => present,
> notify => Exec["yum-clean-all"],
> }
>
> exec { "yum-autoupdate":
> command => "mv /etc/cron.daily/0yum-daily.cron
> /etc/cron.weekly/0yum-daily.cron",
> onlyif => "[ -f /etc/cron.daily/0yum-daily.cron ]",
> }
>
> file { "/etc/cron.daily/0yum-daily.cron": ensure => absent, }
>
> file { "/etc/cron.weekly/0yum-daily.cron": ensure => present, }
> Exec['yum-autoupdate'] -> File['/etc/cron.daily/0yum-daily.cron'
> ] -> File['/etc/cron.weekly/0yum-daily.cron']
>
> }
> }
> }
> 'windows' : {
> exec { 'chocolatelyinstall':
> command => '$((iex ((new-object net.webclient).DownloadString("
> https://chocolatey.org/install.ps1";)))>$null 2>&1)',
> unless => 'if (Test-Path C:\ProgramData\chocolatey){ exit 0 }
> else { exit 1}',
> provider => powershell,
> }
>
> file { 'chocolatey.config':
> path => "C:/ProgramData/chocolatey/config/chocolatey.config",
> content => template('yum/chocolatey.config.erb'),
> ensure => present,
> }
>
> acl { 'C:/ProgramData/chocolatey/config/chocolatey.config':
> permissions => [
> {
> identity => 'SYSTEM',
> rights => [
> 'full']
> }
> ,
> {
> identity => 'Administrators',
> rights => [
> 'full']
> }
> ,
> {
> identity => 'Users',
> rights => [
> 'read',
> 'execute']
> }
> ],
> require => File['chocolatey.config'],
> }
>
> }
> }
> }
>
>
>
>
> On Monday, September 28, 2015 at 3:19:50 PM UTC-4, Rob Reynolds wrote:
>
> Can you address the yum bit?
>
> On Mon, Sep 28, 2015 at 12:34 PM, jmp242 <jp1...@gmail.com> wrote:
>
> And I removed the "target" and put it in the ACL name as you showed, and
> get the same error.
>
>
> On Friday, September 25, 2015 at 2:31:43 PM UTC-4, jmp242 wrote:
>
> I tried with the simplified version:
> Enter code here... acl { 'chocolatey.config':
> target =>
> 'C:/ProgramData/chocolatey/config/chocolatey.config',
> permissions => [
> {
> identity => 'SYSTEM',
> rights => [
> 'full']
> }
> ,
> {
> identity => 'Administrators',
> rights => [
> 'full']
> }
> ,
> {
> identity => 'Users',
> rights => [
> 'read',
> 'execute']
> }
> ],
> require => File['chocolatey.config'],
> }
>
> I got the same error. Unless the problem is using
> target=>
>
> I'm at a loss...
>
> ...
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/c22bcfb6-b70e-48fd-8b83-4b07fccd3db9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
