644611 - update screen resolution+apks on tegras 055 - 093

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P3)

Description

[Mike Taylor [:bear]]

We need Tegras 055 thru 094 to be reimaged so they will pickup the latest v1.0 sutAgentAndroid and also the Watcher apk's

Comment 1

[Zandr Milewski [:zandr]]

This is seriously labor intensive.

Is there a plan to be able to update stuff like this remotely in the future?

In the mean time, I'll pull these out of the racks in 2/IDF and hand them off to Spencer today.

Comment 2

[Mike Taylor [:bear]]

(In reply to comment #1)
> This is seriously labor intensive.
> 
> Is there a plan to be able to update stuff like this remotely in the future?
> 
> In the mean time, I'll pull these out of the racks in 2/IDF and hand them off
> to Spencer today.

sadly no - the current imaging process requires USB connectivity.

The current request is to catch the remaining tegras for the most recent bug-fix update of the testing apk's - in the future I am hoping that only small groups of tegras will need reimaging in order to "freshen" them.

Comment 3

[Bob Moss :bmoss]

While imaging the board's OS and/or initially installing the agent apk set (currently SUTAgentAndroid, Watcher, FfxCP, and FenCP) require physical usb connectivity, subsequent updating of the agent components can be done via network connection rather than physical connection.

Comment 4

[Aki Sasaki [:aki] (he/him) (UTC-7)]

Zandr:
Bob tells us we can fix the resolution + apks remotely for 55-94.
We will need imaging for some of the tegras < 55, but we'll open a new bug for that.

I'm hoping this didn't get too far.

Comment 5

[Bob Moss :bmoss]

I forgot one thing, at least on tegra-057 we will need to enable root access which necessitates physical access via usb. I'm not sure about the rest of 055-094.

Comment 6

[Aki Sasaki [:aki] (he/him) (UTC-7)]

How do we check that? su ?

Comment 7

[Zandr Milewski [:zandr]]

Aki- I had spencer reimage 55 and 56, and I'm about to sweep through 57-94 looking for issues with su.

Comment 8

[Zandr Milewski [:zandr]]

Just walked through the machines in 2/IDF, which are in fact 55 through 93 (there is no tegra-094)

Pulled 057, 058, 059, 063, and 078

These either wouldn't respond on the network at all, or couldn't su. Over to spencer to reimage those 5.

Comment 9

[Aki Sasaki [:aki] (he/him) (UTC-7)]

Once 55-90 are fixed, we can add 55-70 to foopy03, and 71-90 to foopy04, and point to test-master01.

Comment 10

[Chris Cooper [:coop] (he/him)]

Reassigning to bear based on discussions with Aki.

Comment 11

[Zandr Milewski [:zandr]]

All of these are working except for 58 and 59 which require some debugging. Should they go to Aki?

Comment 12

[Aki Sasaki [:aki] (he/him) (UTC-7)]

Sure. What does "require some debugging" mean from a symptom standpoint?

Comment 13

[Zandr Milewski [:zandr]]

Despite reimages and reboots, they do not respond to their assigned IP address. Have not connected a display yet, but the lights appear to blink correctly.

Comment 14

[Aki Sasaki [:aki] (he/him) (UTC-7)]

Ok. I'll take a look. I am going to guess there's a mac address typo in the dhcp configs, though.

Comment 15

[Mike Taylor [:bear]]

Attachment: helper tool to push apk's to tegra's

This is a first pass at a tool that will make devicemanager pushFile() and updateApp() calls for any of the tegra apk's it finds in a target directory.

Right now it's doing a lot of little hard-coded checks and compares to make life simpler.

Comment 16

[Mike Taylor [:bear]]

ran a script to update the two apks and the following tegras did not "take":

058, 059, 069, 077

Comment 17

[Zandr Milewski [:zandr]]

58 and 59 are on Aki's desk. :D

Comment 18

[Aki Sasaki [:aki] (he/him) (UTC-7)]

bug 646288 for tegra-058, tegra-059

tegra-069 and tegra-077 are pingable, but I can't telnet to port 20701.

To deal with these, we can:

a) ask IT to reboot, which may or may not fix
b) use them to test the network PDU (do we have a map of which ip/port is which tegra yet?), also may or may not fix
c) ask IT to reimage, should fix assuming dhcp mac is correct

We also need to update tegra-011 through tegra-030, and I believe we're all up to date with SUT v1.00 after that.  Since they've been in production for a while, it might be cleanest to image, but it wouldn't hurt to try the script either.

Comment 19

[Zandr Milewski [:zandr]]

(In reply to comment #18)
> bug 646288 for tegra-058, tegra-059
> 
> tegra-069 and tegra-077 are pingable, but I can't telnet to port 20701.
> 
> To deal with these, we can:
> 
> a) ask IT to reboot, which may or may not fix

Done; 77 came back, 69 still doesn't respond on 20701.

> b) use them to test the network PDU (do we have a map of which ip/port is which
> tegra yet?), also may or may not fix

http://pdu1.build.mozilla.org and http://pdu2.build.mozilla.org, the ports are labelled. hit me on irc for the login.

> c) ask IT to reimage, should fix assuming dhcp mac is correct

It is, or they wouldn't be pingable.

> We also need to update tegra-011 through tegra-030, and I believe we're all up
> to date with SUT v1.00 after that.  Since they've been in production for a
> while, it might be cleanest to image, but it wouldn't hurt to try the script
> either.

Let me know if you want to image these.

Comment 20

[Aki Sasaki [:aki] (he/him) (UTC-7)]

Bear: before we close this and create followup bugs, could you:

a) attach working scripts for review/landing
b) comment when the tegras are verified good in staging and pointed at production?

Comment 21

[Mike Taylor [:bear]]

Attachment: tool to install all apk's found in an update dir to set of tegras

right now the tool has some hardcoded checks to determine process name and some other variables but I was able to use it to update watcher and sutagent for tegras 053 - 093 successfully.

very brute force and kinda ugly, but it worked

Comment 22

[Mike Taylor [:bear]]

(In reply to comment #20)
> Bear: before we close this and create followup bugs, could you:
> 
> a) attach working scripts for review/landing

attached to this bug

> b) comment when the tegras are verified good in staging and pointed at
> production?

tracking in bug 646494

Comment 23

[Mike Taylor [:bear]]

Comment on attachment 523012 [details]
tool to install all apk's found in an update dir to set of tegras

committed changeset 1315:e8baf75d973d

Comment 24

[Mike Taylor [:bear]]

filed bug 646645 to reimage tegra 077 and bug 646651 to upgrade apks on tegra 011 - 030