Hi,
I just saw there is an update to 2.7.x IN SLES 11 SP3 now - there it is
fixed.
Regards
Torsten
--
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
Hi,
it's easy to reproduce.
On Puppet-Master i have a module called test_bug with this manifest:
test_bug/manifests/init.pp
class test_bug {
file{/tmp/test_bug.sh:
ensure = present,
source = puppet:///modules/test_bug/test_bug.sh,
}
}
And one file:
On Monday, October 13, 2014 3:54:17 AM UTC-5, Torsten Amshove wrote:
Hi,
it's easy to reproduce.
On Puppet-Master i have a module called test_bug with this manifest:
test_bug/manifests/init.pp
class test_bug {
file{/tmp/test_bug.sh:
ensure = present,
source =
On Wednesday, October 8, 2014 7:33:32 AM UTC-5, Torsten Amshove wrote:
Ok, the other modules works because they don't create a new file.
If the file on the puppet client exists, (even an empty one) everything
works fine - if you delete it, this error occures.
ensure = present,
and
Any solution here?
I stuck at the same problem. puppet 2.6.18 on SLES 11
even if I remove the mode line it gets the same error with 644 instead of
700
I think the message is more about the strange whereever this came from.
Another strange thing: This only happens in one puppet module - the
Ok, the other modules works because they don't create a new file.
If the file on the puppet client exists, (even an empty one) everything
works fine - if you delete it, this error occures.
ensure = present,
and
ensure = file,
makes no difference
--
You received this message because
Hello,
i could narrow this down a little bit
`' for 760:String
stands for the file permissions declared as
mode = '0760',
so there must be a problem when setting file permissions.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To
