talos-r3-w7-003/004/005/006/007 + talos-r3-fed64-011/014 not reachable

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
RESOLVED FIXED
9 years ago
3 years ago

People

(Reporter: alice, Assigned: phong)

Tracking

Details

(Reporter)

Description

9 years ago
Technically, 003 is reachable but the machine reached is labelled 004 - so there is some confusion here.

Can we check if these machines have correct dns entries?  Correct names?
Assignee: server-ops → phong
(Reporter)

Comment 1

9 years ago
Same issue with talos-r3-fed64-014, just can't access the box.
Summary: talos-r3-w7-003/004/005/006/007 not reachable → talos-r3-w7-003/004/005/006/007 + talos-r3-fed64-014 not reachable
while phong is offline, offsite, can "oncall" handle this today instead please?
Assignee: phong → server-ops
Severity: normal → blocker
I made a trip to the colo yesterday and got some of the pending reboots.  Is this really a blocker bug that we have to get done before next week?  We might be able to get this done on Friday (when phong returns).
Assignee: server-ops → aravind
I'm taking a look at this shortly, it appears all these hosts are located in Mountain View
The 003/004 mixup has been corrected, so 004 is now online with the expected DNS hostname.

003, 005, 006, and 007 were not in DHCP. This has been fixed. 003, 005, and 007 are now online. 006 did not come online, but I don't think I'll have enough time before my flight to troubleshoot why it won't boot.
Phong should be able to take a look at the remaining host once he gets back.
Assignee: aravind → phong
Severity: blocker → major
As it stands, talos-r3-w7-006 (in the 2nd floor server room) and talos-r3-fed64-014 (in the QA lab) will not boot and are still offline.
(Reporter)

Comment 8

9 years ago
talos-r3-fed64-011 also needs looking at.
Severity: major → normal
Summary: talos-r3-w7-003/004/005/006/007 + talos-r3-fed64-014 not reachable → talos-r3-w7-003/004/005/006/007 + talos-r3-fed64-011/014 not reachable
(Reporter)

Updated

9 years ago
Blocks: 537752
(Assignee)

Comment 9

9 years ago
talos-r3-w7-006 had the wrong mac address in DHCP.

host-5-78:~ phong$ ping talos-r3-w7-006
PING talos-r3-w7-006.mv.mozilla.com (10.250.49.43): 56 data bytes
64 bytes from 10.250.49.43: icmp_seq=0 ttl=128 time=2.336 ms
64 bytes from 10.250.49.43: icmp_seq=1 ttl=128 time=1.108 ms
(Assignee)

Comment 10

9 years ago
talos-r3-fed64-011/014 boot up fine at my desk.  I'm thinking it's a problem with not getting the correct IP.  I will have to track this down.
(Assignee)

Comment 11

9 years ago
talos-r3-fed64-011/014 should have the corrected IP now.

host-5-78:dnsconfig-offices phong$ ping talos-r3-fed64-011.build
PING talos-r3-fed64-011.build.mozilla.org (10.250.49.91): 56 data bytes
64 bytes from 10.250.49.91: icmp_seq=0 ttl=64 time=2.538 ms
64 bytes from 10.250.49.91: icmp_seq=1 ttl=64 time=3.122 ms

host-5-78:dnsconfig-offices phong$ ping talos-r3-fed64-014.build
PING talos-r3-fed64-014.build.mozilla.org (10.250.49.95): 56 data bytes
64 bytes from 10.250.49.95: icmp_seq=0 ttl=64 time=1.154 ms
64 bytes from 10.250.49.95: icmp_seq=1 ttl=64 time=1.151 ms
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
(Reporter)

Comment 12

9 years ago
Isn't talos-r3-w7-006 still outstanding?
(Reporter)

Comment 13

9 years ago
Never mind, talos-r3-w7-006 up and accessible.
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.