Closed
Bug 1620424
Opened 6 years ago
Closed 6 years ago
MDC1 puppetmaster CA expire on 04/24/2020
Categories
(Infrastructure & Operations :: RelOps: General, task)
Infrastructure & Operations
RelOps: General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dividehex, Assigned: dividehex)
Details
Attachments
(2 files)
While working on revoking the AWS puppetmaster certificates, I noticed the MDC1 puppetmasters are set to expire fairly soon. We will need to reissue intermediate CA certs for these two before that date.
Not After : Apr 24 16:04:46 2020 GMT
Subject: CN=CA on releng-puppet1.srv.releng.mdc1.mozilla.com
Not After : Apr 24 16:01:55 2020 GMT
Subject: CN=CA on releng-puppet2.srv.releng.mdc1.mozilla.com
| Assignee | ||
Updated•6 years ago
|
Assignee: relops → jwatkins
| Assignee | ||
Comment 1•6 years ago
|
||
This PR will cause any puppet agents with certs issued from the expired hosts to redirect to the mdc2 hosts. We'll add them back after the mdc1 hosts have new CA certs issued.
| Assignee | ||
Comment 2•6 years ago
|
||
Certs have been changed out. These can be added back now.
| Assignee | ||
Comment 3•6 years ago
|
||
Certs have been renewed and installed
notAfter=Apr 23 17:27:32 2023 GMT
subject= /CN=CA on releng-puppet1.srv.releng.mdc1.mozilla.com
notAfter=Apr 23 17:40:28 2023 GMT
subject= /CN=CA on releng-puppet2.srv.releng.mdc1.mozilla.com
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•