[chef] RE: Re: Recent change to template resource behavior?


Chronological Thread 
  • From: Kevin Keane (subscriptions) < >
  • To: < >
  • Subject: [chef] RE: Re: Recent change to template resource behavior?
  • Date: Fri, 11 Jan 2013 18:26:26 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=sendgrid.info; h=subject :from:to:mime-version:content-type:in-reply-to:references :sender; q=dns; s=smtpapi; b=Ahx2RTjAclrieYrbUK0Jov40OKyPTIeD8O/ Pp0FhaDJAtqKjZVAjpxbnaH/v50H5zm53YmPb2cV9cRJKRHZu0Sr9AgTI21+TIp3 ieQ6u9kH+UXEyXZ9T9FxBmCEtxvr9Xkql4bW8uxwUbCXAqkJ+XsudXFWsHmfhk0y L5r6d5cA=

Title: RE: [chef] Re: Recent change to template resource behavior?

I agree, that change was probably it.

 

Would it make sense to change CHEF-1856 from "wontfix" to "fixed" to prevent a regression in the future?
 

-----Original message-----
From: Matthew Moretti < >
Sent: Fri 01-11-2013 05:55 pm
Subject: [chef] Re: Recent change to template resource behavior?
To: ;
I found this in the differences between those two versions.  Could that be what fixed it?  I know hardly anything about SELinux, but I thought someone on the list had said something about the context being clobbered because the file was created in a temporary directory and then moved into place.  Is the behavior different if you copy the file there instead?
 
If this was what caused the fix, then I would say that it wasn't a deliberate attempt to fix an SELinux problem, judging by the commit message.
 
-Matt Moretti


On Fri, Jan 11, 2013 at 8:04 PM, Kevin Keane (subscriptions) < "> > wrote:

I am trying to work on the selinux cookbook for various things. One of the main issues I wanted to address is described in CHEF-1856; the same problem has been driving me crazy for quite a while.

 

Basically, Chef will clobber the SELinux context of files generated from a template. This is still happening in 10.16.0.

 

Much to my surprise, the problem no longer seems to exist in 10.16.6. I didn't see anything in the release notes about this issue being addressed.

 

Can anybody confirm that this has been fixed? And if so, was it fixed as a side effect of something else (and thus could regress easily), or has it been specifically addressed?

 

Thanks!

 




Archive powered by MHonArc 2.6.16.

§