Closed Bug 1449230 Opened 2 years ago Closed 2 years ago

update bugzilla-dev.allizom.org to point to bugzilla.devsvcdev.mozaws.net

Categories

(bugzilla.mozilla.org :: Infrastructure, enhancement)

Production
enhancement
Not set

Tracking

()

RESOLVED FIXED

People

(Reporter: glob, Assigned: ckolos)

References

Details

bugzilla-dev.allizom.org is the long established site for testing/playing with bmo, currently running in scl3.

bugzilla.devsvcdev.mozaws.net is the new aws-hosted site that replaces it.



bugzilla-dev.allizom.org should either redirect to bugzilla.devsvcdev.mozaws.net, or become the new canonical hostname for that service.
12:10 AM <@dylan|pto-ish> glob: in that bug you probably should be explicit that the data/params from scl3 bugzilla dev should be copied
12:11 AM <@dylan|pto-ish> so as to not break integration with mozphab
note that I think bugzilla-dev.allizom.org should " become the new canonical hostname for that service."
We can't create canonical records in non-r53 zones that we don't control via our provisioning and allizom.org is not in r53 under cloudops control. 

I can CNAME this from allizom.org to devsvcdev.mozaws.net Aside from requiring a new cert on the AWS side, this should work fine
Assignee: nobody → ckolos
Depends on: 1451339
This has been done.

dig @8.8.8.8 bugzilla-dev.allizom.org

; <<>> DiG 9.12.1 <<>> @8.8.8.8 bugzilla-dev.allizom.org
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54231
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;bugzilla-dev.allizom.org.	IN	A

;; ANSWER SECTION:
bugzilla-dev.allizom.org. 3291	IN	CNAME	bugzilla.devsvcdev.mozaws.net.
bugzilla.devsvcdev.mozaws.net. 59 IN	A	52.88.74.55
bugzilla.devsvcdev.mozaws.net. 59 IN	A	54.148.247.121

;; Query time: 61 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Apr 04 10:08:22 CDT 2018
;; MSG SIZE  rcvd: 128
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Looks like the urlbase wasn't updated yet.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Fixed in dev.
Status: REOPENED → RESOLVED
Closed: 2 years ago2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.