Closed
Bug 1124595
Opened 9 years ago
Closed 9 years ago
[Mozillians][prod] Chief permission denied error on push to production
Categories
(Infrastructure & Operations Graveyard :: WebOps: Engagement, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nemo-yiannis, Assigned: cliang)
Details
(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/326] )
In our latest push to production, chief is raising a "permission denied" error for generic7.webapp.phx1.mozilla.com node. The error is: [2015-01-22 02:22:12] [generic7.webapp.phx1.mozilla.com] failed: /data/bin/update-www.sh mozillians.org (0.127s) [generic7.webapp.phx1.mozilla.com] err: Permission denied (publickey,gssapi-keyex,gssapi-with-mic). [2015-01-22 02:22:34] [generic7.webapp.phx1.mozilla.com] failed: for i in {1..10}; do curl -so /dev/null -H 'Host: mozillians.org' -I http://localhost:80/ & sleep 1; done (0.107s) [generic7.webapp.phx1.mozilla.com] err: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
Reporter | ||
Comment 1•9 years ago
|
||
Is there any update regarding that bug?
Assignee | ||
Updated•9 years ago
|
Assignee: server-ops-webops → cliang
Assignee | ||
Comment 2•9 years ago
|
||
Can you please test to see if you are still getting a "permission denied" when using chief to do a push to production? I think I left off the configuration step that would have ensured that the automation SSH keys would stay enabled. My apologies! I've made the configuration change and pushed it out.
Reporter | ||
Comment 3•9 years ago
|
||
No worries, I will verify it in our next push.
Reporter | ||
Comment 4•9 years ago
|
||
No errors encountered in our last push. Marking this one as resolved. Thank you!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•