relocate mobile-imaging-stage1.p127.releng.scl1.mozilla.com from kvm to mobile-imaging-stage1.p127.releng.scl3.mozilla.com on vmware

RESOLVED FIXED

Status

RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: arich, Assigned: dustin)

Tracking

Details

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
This vm needs to migrate to scl3 before the final panda move train on July 14th.
Depends on: 1027865
Depends on: 1034235
This is puppetized now.  However, it can't reach the staging VIP, so I've requested a flow for that.

Once that's up, this host and the old host will both think they're admin nodes.  I'll have a patch for that in a sec.
Created attachment 8450455 [details] [diff] [review]
bug1027855.patch
Attachment #8450455 - Flags: review?(jwatkins)
Amy, will monitoring "automatically" move from the old to the new host when the move train occurs?
Flags: needinfo?(arich)
(Reporter)

Comment 4

4 years ago
No, monitoring needs to be updated manually.
Flags: needinfo?(arich)
OK, I added host monitoring for it.
Attachment #8450455 - Flags: review?(jwatkins) → review+
Comment on attachment 8450455 [details] [diff] [review]
bug1027855.patch

Of course, now that the DB access is working, this can be switched to the scl3 master.  I'll land that trivial change (s/scl1/scl3/g) now.
Attachment #8450455 - Flags: checked-in+
http://hg.mozilla.org/build/puppet/rev/e4a9c6f23760

I'll update the move checklist as well, but this is done and ready to go.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.