On Wednesday, November 11, 2015 at 7:21:44 AM UTC-6, Arnau wrote: > > Change ::selinux to false (append selinux=0 in the kernel line) and > everything works as expected. > > > still (very) confused.... > >
It is plausible that disabling selinux on the machine would result in selinux-related classes declaring no resources, or otherwise behaving differently then when selinux is enabled. That would be a function of the classes involved, but the enablement status would be visible to them via a node fact. I'm inclined to think that the behavior change you describe arises from such a provision, but I cannot be sure without reviewing the classes involved. More generally, it would be helpful both to you and to us if you could narrow down the failure case as much as possible, and present a complete, minimal example with which we could reproduce the problem. There's far too much that we don't know about your manifest set and data; without (much) more, it's difficult for us to offer more than guesswork. John -- 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/bcfc422b-5cab-474a-96cc-4f10d46746da%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
