Issue #3999 has been updated by Todd Zullinger.

Sean Millichamp wrote:
> I think I understand the problem.  However, I am almost 2 years rusty on my 
> Ruby and Puppet internals at this point and don't have a ton of time.
> 
> I am happy to look at it, but I can't promise an ETA.

What?  We need guarantees.  This isn't volunteer work... Oh wait, it is.  ;)

Thanks for taking a look Sean, whenever you get some time for it.

> One a first pass, it sounds like one (or both) of the following are correct 
> approaches:
> 
> 1) Test if a path is a mountpoint, if so, skip checking/applying SELinux 
> permissions
> 2) Honor "undef" for the permissions, which should cause SELinux to the label 
> on the filesystem and leave it as it is.

I think 2 makes sense.

I'm not so sure that special casing mount points does.  Or at least, not 
skipping them unconditionally.  Some folks may want to label a mount point.  
Perhaps defaulting to undef for mount points makes sense?  I'm not at all sure 
of that though, just tossing it out for discussion.
----------------------------------------
Bug #3999: undef values for the SELinux attributes of the file resource type 
don't work
http://projects.puppetlabs.com/issues/3999

Author: Cristian Ciupitu
Status: Investigating
Priority: Normal
Assigned to: Sean Millichamp
Category: SELinux
Target version: 
Affected version: 0.25.5
Keywords: SELinux, undef
Branch: 


I've reported first this bug on Fedora's bug tracker - 
https://bugzilla.redhat.com/show_bug.cgi?id=597285.



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to