Closed Bug 893277 Opened 11 years ago Closed 11 years ago

tegra-recovery

Categories

(Infrastructure & Operations :: DCOps, task)

ARM
Android
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Callek, Unassigned)

References

Details

(Whiteboard: [Recovering])

+++ This bug was initially created as a clone of Bug #892096 +++ +++ This bug was initially created as a clone of Bug #889567 +++
colo-trip: --- → mtv1
Tegra-051 has been reimaged and is back online. PING tegra-051.build.mtv1.mozilla.com (10.250.49.38): 56 data bytes 64 bytes from 10.250.49.38: icmp_seq=0 ttl=63 time=62.884 ms 64 bytes from 10.250.49.38: icmp_seq=1 ttl=63 time=2.591 ms Trying 10.250.49.38... Connected to tegra-051.build.mtv1.mozilla.com. There seems to be an issue with tegra-261. I am able to ping it but I cant not connect it with telnet. I reimaged it 3 times and even swapped out the SD card, but I was still unable to connect with telnet.
Blocks: tegra-195
Blocks: tegra-227
Blocks: tegra-315
Blocks: tegra-364
Blocks: tegra-090
Blocks: tegra-134
Depends on: tegra-246
Whiteboard: [Recovering]
All systems below have been re-imaged and are back online PING tegra-134.build.mtv1.mozilla.com (10.250.50.44): 56 data bytes 64 bytes from 10.250.50.44: icmp_seq=0 ttl=63 time=5.016 ms 64 bytes from 10.250.50.44: icmp_seq=1 ttl=63 time=7.021 ms 64 bytes from 10.250.50.44: icmp_seq=2 ttl=63 time=5.025 ms mozilla$ telnet tegra-134.build.mtv1.mozilla.com. 20701 Trying 10.250.50.44... Connected to tegra-134.build.mtv1.mozilla.com. PING tegra-227.build.mtv1.mozilla.com (10.250.51.67): 56 data bytes 64 bytes from 10.250.51.67: icmp_seq=0 ttl=63 time=5.174 ms 64 bytes from 10.250.51.67: icmp_seq=1 ttl=63 time=2.657 ms 64 bytes from 10.250.51.67: icmp_seq=2 ttl=63 time=4.898 ms mozilla$ telnet tegra-227.build.mtv1.mozilla.com. 20701 Trying 10.250.51.67... Connected to tegra-227.build.mtv1.mozilla.com. PING tegra-195.build.mtv1.mozilla.com (10.250.50.105): 56 data bytes 64 bytes from 10.250.50.105: icmp_seq=0 ttl=63 time=5.263 ms 64 bytes from 10.250.50.105: icmp_seq=1 ttl=63 time=5.281 ms 64 bytes from 10.250.50.105: icmp_seq=2 ttl=63 time=5.703 ms mozilla$ telnet tegra-195.build.mtv1.mozilla.com. 20701 Trying 10.250.50.105... Connected to tegra-195.build.mtv1.mozilla.com. PING tegra-090.build.mtv1.mozilla.com (10.250.49.78): 56 data bytes 64 bytes from 10.250.49.78: icmp_seq=0 ttl=63 time=4.952 ms 64 bytes from 10.250.49.78: icmp_seq=1 ttl=63 time=5.045 ms 64 bytes from 10.250.49.78: icmp_seq=2 ttl=63 time=3.338 ms mozilla$ telnet tegra-090.build.mtv1.mozilla.com. 20701 Trying 10.250.49.78... Connected to tegra-090.build.mtv1.mozilla.com. PING tegra-051.build.mtv1.mozilla.com (10.250.49.38): 56 data bytes 64 bytes from 10.250.49.38: icmp_seq=0 ttl=63 time=2.345 ms 64 bytes from 10.250.49.38: icmp_seq=1 ttl=63 time=3.150 ms 64 bytes from 10.250.49.38: icmp_seq=2 ttl=63 time=2.700 ms mozilla$ telnet tegra-051.build.mtv1.mozilla.com. 20701 Trying 10.250.49.38... Connected to tegra-051.build.mtv1.mozilla.com.
PING tegra-051.build.mtv1.mozilla.com (10.250.49.38): 56 data bytes 64 bytes from 10.250.49.38: icmp_seq=0 ttl=63 time=62.884 ms 64 bytes from 10.250.49.38: icmp_seq=1 ttl=63 time=2.591 ms Trying 10.250.51.155... Connected to tegra-315.build.mtv1.mozilla.com. PING tegra-364.build.mtv1.mozilla.com (10.250.51.204): 56 data bytes 64 bytes from 10.250.51.204: icmp_seq=0 ttl=63 time=19.300 ms 64 bytes from 10.250.51.204: icmp_seq=1 ttl=63 time=2.516 ms Trying 10.250.51.204... Connected to tegra-364.build.mtv1.mozilla.com.
PING tegra-315.build.mtv1.mozilla.com (10.250.51.155): 56 data bytes 64 bytes from 10.250.51.155: icmp_seq=0 ttl=62 time=6.159 ms 64 bytes from 10.250.51.155: icmp_seq=1 ttl=62 time=6.289 ms Trying 10.250.51.155... Connected to tegra-315.build.mtv1.mozilla.com.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Alias: tegra-recovery
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.