914472 - Create and stage panda (Android 4..0.4) update of watcher/SUTAgent

Status: RESOLVED FIXED

(Infrastructure & Operations :: RelOps: General, task)

Description

[Justin Wood (:Callek)]

So we need to create a new mozpool related image for Android 4.2 to include the newer SUTAgent and newer watcher.

Once its created we need to add it to mozpool to allow us to image a set of pandas for a staging run, once those tests pass in staging and we're ready to deploy we'll need to swap the current android image (in mozpool) with the new one, leaving the old available if we need to rollback because of issues.

Jake said he can easily manage the new mozpool image, but mentioned Joel gave him the initial image.

Options:
(A) Take current Android 4.2 image, install new watcher and new SUTAgent, install current watcher.ini, repackage up for mozpool, deploy.
(B) Create new Android 4.2 image identical to current, but without ever installing watcher or SUTAgent, then install correct SUTAgent and Watcher versions, install watcher.ini, then repackage for mozpool, deploy.
(C...?) Other?

I updated it for Tegras in Bug 913304, We (Releng) hope to deploy newer watcher on Friday (Sept 13) so would be great if we can choose and perform one of these options and staging runs by then!'

Joel, Jake, can you two figure out what update option we want to do here.

Comment 1

[Joel Maher ( :jmaher ) (UTC -8)]

in the past while developing this we have taken the previous running image, manually update the sut/watcher, then recreated the bits.  I would just load this locally, update software, and crate a zip file of the os and hand it off to Jake.

Comment 2

[Jake Watkins [:dividehex]]

(In reply to Justin Wood (:Callek) from comment #0)
> So we need to create a new mozpool related image for Android 4.2 to include
> the newer SUTAgent and newer watcher.

I'm ok with either way but I do think updating the current image would be easier and less likely to introduce differences between in the OS that could impact tests.  Some on just needs to get me the DD image of the sdcard taken in 512b chucks.  eg dd if=/dev/mmcblk0 of=./new_androi_image.img bs=512
(The bs=512 is important).  I'll convert that image into mozpool.

Also, just so we are all clear, the version of Android we have been using all this time is android-4.0.4_r1.2 ICS (Ice Cream Sandwich).  The upstream tag can be found with the build we are using from Linaro.  http://releases.linaro.org/12.05/android/leb-panda/source-manifest.xml

I feel like there has been some confusion about that by more than a few people.  So I just want to clear that up.

Comment 3

[Joel Maher ( :jmaher ) (UTC -8)]

http://people.mozilla.org/~jmaher/panda/panda_16gb_v3.1.img.bz2

shasum panda_16gb_v3.1.img.bz2 
e4256a4eb62d640ecf36a2e9e6ff2aaa58ca7b26  panda_16gb_v3.1.img.bz2

This includes the latest sutagent (1.19) and watcher (1.16)

Comment 4

[Pete Moore [:pmoore][:pete]]

Thanks Joel. Will you also be rolling it out to staging pandas, or should we (RelEng) do that?

Thanks,
Pete

Comment 5

[Joel Maher ( :jmaher ) (UTC -8)]

Pete, dividehex might be doing that, I believe he is making this available to the pandas via mozpool, then somebody would need to specify which OS version to install via mozpool during checkout.

Comment 6

[Jake Watkins [:dividehex]]

The new android image is available in mozpool as image name 'panda-android-4.0.4_v3.1'
I've tested this on a couple unused pandas with lifeguard; It deploys fine and verifies with a sut connection.

Releng will need to update mozpool requests with the new image name for the pandas managed by mozpool.
For the ones that are locked out, they will need to be manually updated with lifeguard and then re-locked_out