1643119 - do something with docs.mozilla-releng.net

Status: RESOLVED FIXED

(Release Engineering :: General, enhancement)

Description

[[e-mail] (:bhearsum)]

These have been replaced by https://moz-releng-docs.readthedocs.io/en/latest/index.html. We should 302 or CNAME if possible. Or add a page with a redirect at the very least.

Comment 1

[Simon Fraser [:sfraser] ⌚️GMT]

We'll need to un-archive https://github.com/mozilla/release-services briefly to update the docs there with a link.

Who controls mozilla-releng.net? It has AWS nameservers.

Comment 2

[Tom Prince [:tomprince]]

According to Bug 1558787, it looks like it is managed be cloudops. It appears to be tracked configured here.

Comment 3

[[e-mail] (:bhearsum)]

Jeremy, is it possible to CNAME docs.mozilla-releng.net to moz-releng-docs.readthedocs.io?

Comment 4

[Tom Prince [:tomprince]]

We should also ensure that any cloudfront distribution and s3 bucket are cleaned up, from the old name are cleaned up as well.

Comment 5

[Jeremy Orem [:oremj]]

It looks like if I add that CNAME, it will 403:

curl -H 'Host: docs.mozilla-releng.net' -v https://moz-releng-docs.readthedocs.io/

< HTTP/2 403
< server: cloudflare
< date: Tue, 09 Jun 2020 20:58:06 GMT
< content-type: text/html
< content-length: 151
< cf-ray: 5a0dc4cbdc4ffda9-PDX
< cf-request-id: 033c7953690000fda9fd18b200000001

Whoever manages the domain on RTD will need to add the custom domain: https://docs.readthedocs.io/en/stable/custom_domains.html#custom-domain-support and then I can CNAME it over.

Comment 6

[[e-mail] (:bhearsum)]

(In reply to Jeremy Orem [:oremj] from comment #5)

It looks like if I add that CNAME, it will 403:

curl -H 'Host: docs.mozilla-releng.net' -v https://moz-releng-docs.readthedocs.io/

< HTTP/2 403
< server: cloudflare
< date: Tue, 09 Jun 2020 20:58:06 GMT
< content-type: text/html
< content-length: 151
< cf-ray: 5a0dc4cbdc4ffda9-PDX
< cf-request-id: 033c7953690000fda9fd18b200000001

Whoever manages the domain on RTD will need to add the custom domain: https://docs.readthedocs.io/en/stable/custom_domains.html#custom-domain-support and then I can CNAME it over.

I just did this.

Comment 7

[Jeremy Orem [:oremj]]

Hmm, I'm still seeing the 403. I wonder what might be up? You should be able to test whether or not it is working with the command in the previous comment.

Comment 8

[[e-mail] (:bhearsum)]

(In reply to Jeremy Orem [:oremj] from comment #7)

Hmm, I'm still seeing the 403. I wonder what might be up? You should be able to test whether or not it is working with the command in the previous comment.

I'm not exactly sure, but I think RTD may require the CNAME to exist for this to work? In the UI I currently see:

SSL certificate status: pending_validation
Did you setup a CNAME record in DNS pointing at "readthedocs.io"?

The docs also say that we should be CNAMEing to plain readthedocs.io, which may be a factor here? Although curl -H 'Host: docs.mozilla-releng.net' -v https://readthedocs.io/ also doesn't work.

Comment 9

[Jeremy Orem [:oremj]]

I just updated the record to point to readthedocs.io:

dig docs.mozilla-releng.net

; <<>> DiG 9.10.6 <<>> docs.mozilla-releng.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25571
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;docs.mozilla-releng.net.	IN	A

;; ANSWER SECTION:
docs.mozilla-releng.net. 299	IN	CNAME	readthedocs.io.
readthedocs.io.		299	IN	A	104.17.32.82
readthedocs.io.		299	IN	A	104.17.33.82

;; Query time: 70 msec
;; SERVER: 192.168.86.1#53(192.168.86.1)
;; WHEN: Mon Jun 29 10:16:21 PDT 2020
;; MSG SIZE  rcvd: 112

Comment 10

[Jeremy Orem [:oremj]]

It looks like this did work.

Comment 11

[[e-mail] (:bhearsum)]

(In reply to Jeremy Orem [:oremj] from comment #10)

It looks like this did work.

Yep! I had to remove and re-add the domain on RTD to force it to redo its SSL verification, I think. But http://docs.mozilla-releng.net/en/latest/ is working for me now too.

Thanks!