Bug 728257 (tegra-268)

tegra-268 problem tracking

RESOLVED FIXED

Status

Release Engineering
Buildduty
P3
normal
RESOLVED FIXED
6 years ago
4 years ago

People

(Reporter: armenzg, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [buildduty][buildslave][capacity], URL)

(Reporter)

Description

6 years ago
I couldn't manage to recover tegra-268.

Could you please recover it when you can get to it?
Thanks!

foopy23:~ cltbld$ /builds/check.sh -t tegra-268 -c
2012-02-17 08:33:17,989  Tegra ID M    Tegra       CP    Slave :: Msg
2012-02-17 08:33:33,368 tegra-268 p   OFFLINE   active  OFFLINE :: PING tegra-268.build.mtv1.mozilla.com (10.250.51.108): 56 data bytes Request timeout for icmp_seq 0;
2012-02-17 08:33:33,369 power cycling tegra
SNMPv2-SMI::enterprises.1718.3.2.3.1.11.1.1.10 = INTEGER: 

foopy23:~ cltbld$ /builds/check.sh -t tegra-268 
2012-02-17 08:48:21,806  Tegra ID M    Tegra       CP    Slave :: Msg
2012-02-17 08:48:36,837 tegra-268 p   OFFLINE   active  OFFLINE :: PING tegra-268.build.mtv1.mozilla.com (10.250.51.108): 56 data bytes Request timeout for icmp_seq 0;
Assignee: server-ops-releng → mlarrain
colo-trip: --- → mtv1
(Reporter)

Comment 1

6 years ago
bear, here is a paste of what was the last step it ever run in case we need to file a bug to find out if there is something we can do:

python /builds/sut_tools/cleanup.py 10.250.51.108
 in dir /builds/tegra-268/test/. (timeout 1200 secs)
 watching logfiles {}
 argv: ['python', '/builds/sut_tools/cleanup.py', '10.250.51.108']
 environment:
  PATH=/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
  PWD=/builds/tegra-268/test
  SUT_IP=10.250.51.108
  SUT_NAME=tegra-268
  __CF_USER_TEXT_ENCODING=0x1F5:0:0
 closing stdin
 using PTY: False
Warning proxy.flg found during cleanup
Connecting to: 10.250.51.108
reconnecting socket
unable to connect socket
reconnecting socket
unable to connect socket
reconnecting socket
unable to connect socket
reconnecting socket
unable to connect socket
reconnecting socket
unable to connect socket
reconnecting socket
unable to connect socket
devroot None
/builds/tegra-268/test/../error.flg
Remote Device Error: devRoot from devicemanager [None] is not correct

Updated

6 years ago
Status: NEW → ASSIGNED
The sdcard might be dead trying a second reimage
imaged and put back into the rack
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Reporter)

Comment 4

6 years ago
This seems to have gone down again.

03-02-2012 13:37:01 PING down since then.

What should we do?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
ping?
I will try a new SD card on it
new SD card imaged and plugged back in. Please test again. I will copy and zip the contents of the possible bad SD card. Who would like it for review?

Updated

6 years ago
Assignee: mlarrain → nobody
Component: Server Operations: RelEng → Release Engineering
QA Contact: zandr → release

Updated

6 years ago
Component: Release Engineering → Release Engineering: Machine Management
Priority: -- → P3
Whiteboard: [buildduty][buildslave][capacity]
I'm still having trouble getting this Tegra up. Our scripts are saying:
2012-03-08 12:31:13,032 tegra-268 p   OFFLINE   active  OFFLINE :: ping: sendto: No route to host PING tegra-268.build.mtv1.mozilla.com (10.250.51.108): 56 data bytes;


And I've already tried rebooting it via the PDU.
Assignee: nobody → server-ops-releng
Component: Release Engineering: Machine Management → Server Operations: RelEng
QA Contact: release → arich
17:03 < bear-afk> bhearsum - tegra-268 should be put back for some lovin'  - most likely the power switch is 
                  wrong or something simple - that keeps it from starting the OS 
17:03 < bhearsum|buildduty> alrighty
17:03 < bhearsum|buildduty> thanks bear
17:03 < bear-afk> the power switch has 3 positions, two of them prevent it from working :)
17:03 < bhearsum|buildduty> of course!
17:03 < bear-afk> one is for "simulate battery" or some such
Assignee: server-ops-releng → mlarrain
it only has two modes battery mode and power supply I always make sure it is on power supply mode which it should be. I think i used the wrong SD card (grabbed one of the ones for panda boards) when I replaced it using a new one meant for tegras.

Comment 11

6 years ago
moved over to staging by manually editing the tac file - clientproxy restarted

Updated

6 years ago
Assignee: mlarrain → nobody
Component: Server Operations: RelEng → Release Engineering
QA Contact: arich → release

Updated

6 years ago
Alias: tegra-268
Summary: recover tegra-268 → tegra-268 problem tracking
Is this tegra ready for production again?
Looks like it hasn't done any jobs in staging yet.

Comment 14

6 years ago
It appears to be hard offline, i've given the PDU a kick and will check on it in an hour

Updated

6 years ago
Depends on: 738422

Updated

6 years ago
Assignee: nobody → coop
Status: REOPENED → ASSIGNED
OS: Mac OS X → Android
Priority: P3 → P2
Hardware: x86 → ARM

Updated

6 years ago
Assignee: coop → nobody
Status: ASSIGNED → NEW
Priority: P2 → P3

Updated

6 years ago
Assignee: nobody → bear

Updated

6 years ago
Blocks: 746661

Comment 15

6 years ago
268 is now offline for use in rackmount enclosure testing - closing bug
Status: NEW → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
Assignee: bear → nobody
Component: Release Engineering → Release Engineering: Machine Management
QA Contact: armenzg

Updated

4 years ago
(Assignee)

Updated

4 years ago
Product: mozilla.org → Release Engineering
Blocks: 959225
You need to log in before you can comment on or make changes to this bug.