Closed
Bug 752531
Opened 13 years ago
Closed 13 years ago
migrate dev-stage01 to scl3
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Infrastructure & Operations Graveyard
CIDuty
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
References
Details
Attachments
(3 files)
892 bytes,
patch
|
rail
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
1.74 KB,
patch
|
rail
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
21.13 KB,
patch
|
rail
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
Needs to move before sjc1 goes away. We need to update the buildbot-configs to point at it, adjust post_upload.py on the machine after migration, update known_hosts, and possibly a couple of other things. bug 739778 can probably be used as a guide for the releng work.
Assignee | ||
Comment 1•13 years ago
|
||
Attachment #621649 -
Flags: review?(rail)
Assignee | ||
Comment 2•13 years ago
|
||
Attachment #621651 -
Flags: review?(rail)
Assignee | ||
Comment 3•13 years ago
|
||
Attachment #621654 -
Flags: review?(rail)
Updated•13 years ago
|
Attachment #621649 -
Flags: review?(rail) → review+
Comment 4•13 years ago
|
||
Comment on attachment 621651 [details] [diff] [review]
update ssh-config package
Can you also bump the version number of the packages (ssh-config{,-staging}?
Also make sure to add the entry to known_hosts files on the puppet masters under /N.
Attachment #621651 -
Flags: review?(rail) → review+
Updated•13 years ago
|
Attachment #621654 -
Flags: review?(rail) → review+
Assignee | ||
Comment 5•13 years ago
|
||
Comment on attachment 621651 [details] [diff] [review]
update ssh-config package
Landed, updated packages, and set to rollout to build machines.
Attachment #621651 -
Flags: checked-in+
Comment 6•13 years ago
|
||
Is there a reason why we're using the specific host name in scl3 in the configs vs just using the alias (dev-stage01.build.mozilla.org)?
Comment 7•13 years ago
|
||
I suspect it harkens back to the conversation we've had (at least twice since I've been here), that the bmo CNAMES are for human use only and shouldn't be in configurations or used by machines?
Comment 8•13 years ago
|
||
yes
Comment 9•13 years ago
|
||
(In reply to Amy Rich [:arich] [:arr] from comment #7)
> I suspect it harkens back to the conversation we've had (at least twice
> since I've been here), that the bmo CNAMES are for human use only and
> shouldn't be in configurations or used by machines?
I won't rathole this bug with that discussion. Someone can educate me privately about why that's preferable.
Assignee | ||
Updated•13 years ago
|
Attachment #621649 -
Flags: checked-in+
Assignee | ||
Comment 10•13 years ago
|
||
I added the new hostkey entry to all of the known_hosts files on the puppet servers (scl1, scl3, mv), too.
Assignee | ||
Comment 11•13 years ago
|
||
Left to do here: update buildbot-configs after the machine actually migrates.
Assignee | ||
Comment 12•13 years ago
|
||
Oh, also need to make sure it connects to Puppet alright after the hostname change.
Assignee | ||
Comment 13•13 years ago
|
||
Comment on attachment 621654 [details] [diff] [review]
update buildbot-configs
Landed this on default.
Attachment #621654 -
Flags: checked-in+
Comment 14•13 years ago
|
||
Your changes on default are now on the production branch and the masters have been reconfigured around 8AM PDT.
Comment 15•13 years ago
|
||
Can anyone reach this host?
Armens-MacBook-Air:~ armenzg$ ping dev-stage01.srv.releng.scl3.mozilla.com
PING dev-stage01.srv.releng.scl3.mozilla.com (10.26.48.44): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Comment 16•13 years ago
|
||
(In reply to Armen Zambrano G. [:armenzg] - Release Engineer from comment #15)
> Can anyone reach this host?
>
your trying to access it while it's down and being migrated
Assignee | ||
Comment 17•13 years ago
|
||
This is all done now.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Updated•7 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•