Closed Bug 991093 Opened 11 years ago Closed 10 years ago

spot instances trying to use revoked puppet certs

Categories

(Release Engineering :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: catlee, Unassigned)

Details

(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2410] )

Attachments

(1 file)

At least the following machines are failing to come up because of certificate revocation: try-linux64-spot-137.try.releng.use1.mozilla.com try-linux64-spot-036.try.releng.use1.mozilla.com try-linux64-spot-183.try.releng.use1.mozilla.com
Attached file list of revoked certs
There are 300 revoked certs. I've moved them out of the way into ~/revoked on aws-manager.
I found revoked certs with this command (in /builds/aws_manager/secrets/cached_certs) for f in *; do if ( ! echo "" | openssl s_client -host releng-puppet2.srv.releng.scl3.mozilla.com -port 8140 -quiet -no_ign_eof -cert $f > ~/$f.log 2>&1 ); then echo $f bad; else rm ~/$f.log; fi; done then I double checked that the log files indicated the revocation as opposed to some other error
Boo, bug 986477 will help here a lot.
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2404]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2404] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2410]
No more puppet on spot instances
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: