Ownership of /etc/chef conflicts with chef-client cookbook
Nobody has claimed this yet.
- Dominant language
- Erlang
- Stars
- 303
- Forks
- 211
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
Chef Server Version
chef-server 12.19.31
Platform Details
AWS m5.xlarge running CentOS 7.6.1810
Configuration
Standalone
Scenario:
If the chef-client cookbook is being used on a Chef Infra Server, the ownership of /etc/chef flip flops anytime chef-server-ctl reconfigure is run. The root cause is this line which resolves to opscode instead of root
Steps to Reproduce:
Run chef-server-ctl reconfigure and then converge the chef-client cookbook
Expected Result:
/etc/chef ownership should be consistent when chef-client cookbook is being used
Actual Result:
/etc/chef ownership flip flops when chef-client cookbook is being used
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with omnibus/files/private-chef-cookbooks/private-chef/recipes/default.rb at line 93, then reproduce the issue with chef-server-ctl reconfigure followed by a converge of the chef-client cookbook. Done means /etc/chef ownership remains consistent across both operations.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100