Don't set owner, group, mode unless unpacking the archive#30
Don't set owner, group, mode unless unpacking the archive#30jdutton wants to merge 1 commit intobryanwb:masterfrom
Conversation
|
Hey @jdutton tks for the patch! i worry that since these actions are run as root that the permissions will never be set properly for the :put and :install actions. I think a better place to put the https://github.com/bryanwb/chef-ark/blob/master/libraries/provider_ark.rb#L179 What do you think? |
|
@jdutton btw, I could really use some help w/ the tomcat cookbook :) . Got a public repo? |
|
Yes, maybe also on https://github.com/bryanwb/chef-ark/blob/master/libraries/provider_ark.rb#L169. As for tomcat cookbook help, I'm in! That was the first cookbook I worked on, so I didn't fork the repo, I downloaded it into my chef repo's cookbooks directory. Also, it's based on your older bryanwb/tomcat repo, not the bryanwb/chef-tomcat repo that you are actively developing on. Are you looking to push your new tomcat cookbook upstream eventually? |
|
I see you're all over CentOS. I'm using Ubuntu - is that still helpful to you? Also, I have a 1 character Ubuntu-specific pull request outstanding to you - bryanwb/chef-collectd#1. I've found your interests very similar to my interests. I guess I'll be deploying logstash next ;-) |
|
@jdutton it is very important to me that my cookbooks all work on ubuntu. not enough time to respond to all your q's right now you should check out my chef-logstash cookbook. I has a super useful also, check out http://foodfightshow.org my chef podcast if you haven't yet On Tue, Oct 30, 2012 at 2:49 AM, Jeff Dutton notifications@github.comwrote:
|
I am using ark to install Tomcat (also derived from a @bryanwb cookbook), and I noticed that Tomcat was restarting every time I did a chef run. The root cause was because of the recursive FileUtils.chown_R and FileUtils.chmod_R called unconditionally from action_set_owner(), which is called from action_install() and action_put().
Inside my exploded Tomcat, I have some config XML files and WAR files that do not have 755 permissions (which is what ark is recursively setting). When chef runs, the ark recipe changes my war and config files to 755 and then when my template and remote_file resources run to set up XML and WAR files they change the permissions back. This falsely triggers service tomcat to restart every chef run.
The way ark is now, the only permissions that will avoid this behavior is if every file under the exploded archive has user and group match the ark archive and has a 755 permission level.
I think a reasonable fix is to only change the permissions when unpacking.