Closed Bug 1009091 Opened 12 years ago Closed 11 years ago

graphite-phx1 and graphite-scl3 use SSL certificate for graphite.m.o

Categories

(Infrastructure & Operations :: Tools, task)

x86_64
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: willkg, Assigned: ericz)

References

Details

As far as I can tell, there are multiple graphite servers. One is at https://graphite.mozilla.org/ which doesn't have Input/SUMO stuff in it. The other I know about is at https://graphite-phx1.mozilla.org/ and does have Input/SUMO stuff in it. The one at https://graphite-phx1.mozilla.org/ has an SSL certificate with a CN of "graphite.mozilla.org" which causes SSL certificate validation issues. (Pretty sure that's the problem--I know I'm getting SSL validation issues.) Can we get this fixed?
Eric, I'll let you figure this one out.
Assignee: server-ops-webops → eziegenhorn
We had plans to bring everything under the graphite.m.o umbrella last year which didn't get done and now people are using the URL we want to repurpose which may make changing urls painful. It's on my plate to figure out how to move forward and I'll include fixing SSL certs in that plan.
Component: WebOps: IT-Managed Tools → Server Operations
Product: Infrastructure & Operations → mozilla.org
QA Contact: nmaul → shyam
Summary: graphite-phx1 has certificate for graphite.m.o → graphite-phx1 and graphite-scl3 use SSL certificate for graphite.m.o
Component: Server Operations → Tools
Product: mozilla.org → Infrastructure & Operations
Fixed the SSL certs for graphite-scl3.mozilla.org and graphite-phx1.mozilla.org. graphite.mozilla.org still points to graphite-scl3.m.o and that will be changed to a multi-site landing page in bug 1085670 -- it was never yet intended for end-user use.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.