Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[STABILITY] Permission denied issue on builder-api-proxy directory #3521

Closed
chefsalim opened this issue Oct 5, 2017 · 4 comments · Fixed by #4193 or #4366
Closed

[STABILITY] Permission denied issue on builder-api-proxy directory #3521

chefsalim opened this issue Oct 5, 2017 · 4 comments · Fixed by #4193 or #4366
Assignees
Labels
Focus:Supervisor Related to the Habitat Supervisor (core/hab-sup) component Type: Bug Issues that describe broken functionality Type:Stability

Comments

@chefsalim
Copy link
Contributor

chefsalim commented Oct 5, 2017

We need to fix the issue where the supervisor sets the service directories to be owned by root, when they should be owned by the 'hab' user (nginx scenario).

@chefsalim chefsalim added this to the Pre-Neighborhoods milestone Oct 5, 2017
@chefsalim chefsalim self-assigned this Oct 6, 2017
@chefsalim
Copy link
Contributor Author

Re-opening as the hook fix does not seem to work.
Also we should handle the permission change for the builder api data folder.

@chefsalim
Copy link
Contributor Author

Re-opening as this is still occuring

@chefsalim chefsalim reopened this Nov 28, 2017
@chefsalim chefsalim removed this from the Pre-Neighborhoods milestone Nov 28, 2017
@chefsalim chefsalim changed the title Permission denied issue on builder-api-proxy directory [STABILITY] Permission denied issue on builder-api-proxy directory Nov 28, 2017
@christophermaier christophermaier self-assigned this Nov 30, 2017
christophermaier added a commit that referenced this issue Dec 1, 2017
NOTE: This is a temporary bandaid for the micro-outages we've been
having with the API server every time the service restarts. The real
fix lies in how the Supervisor starts services (and more specifically,
which user they are started by). Addressing that should (partially)
unlock new behaviors for the Supervisor (like the ability to more
sanely run as a non-root user).

Fixes: #3521

Signed-off-by: Christopher Maier <cmaier@chef.io>
@tashimi tashimi reopened this Dec 19, 2017
@tashimi
Copy link
Contributor

tashimi commented Dec 19, 2017

pretty sure this issue is still happening, and known to be so; Chris had to fix the permissions in acceptance in builder-api-proxy manually today

@burtlo
Copy link

burtlo commented Jan 5, 2018

Thank you very much for fixing this!

giphy-tumblr

burtlo pushed a commit to learn-chef/hab-two-tier that referenced this issue Jan 5, 2018
SEE Issue: habitat-sh/habitat#3521

Signed-off-by: Franklin Webber <franklin@chef.io>
@christophermaier christophermaier added Focus:Supervisor Related to the Habitat Supervisor (core/hab-sup) component Type: Bug Issues that describe broken functionality and removed A-supervisor labels Jul 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Focus:Supervisor Related to the Habitat Supervisor (core/hab-sup) component Type: Bug Issues that describe broken functionality Type:Stability
Projects
None yet
7 participants