run_utah_phablet.py provisioning breaks because phablet-flash has changed

Bug #1245569 reported by Colin Ian King
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Phablet Tools
Fix Released
Undecided
Unassigned
phablet-tools (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I'm guessing that run_utah_phablet.py breaks because phablet-flash has changed over the past several weeks. Can this be fixed?

My script does:

#!/bin/bash
UTAH=./utah
PYTHONPATH=./$UTAH ./utah/examples/run_utah_phablet.py --ppa=ppa:utah/daily

When I run it I get:

= flashing device...
INFO:phablet-flash:Device detected as mako
INFO:phablet-flash:Download directory set to /home/king/Downloads/phablet-flash/ubuntu-touch/20131025
INFO:phablet-flash:Download directory set to /home/king/Downloads/phablet-flash/ubuntu-touch/20131025
INFO:urllib3.connectionpool:Starting new HTTP connection (1): cdimage.ubuntu.com
ERROR:phablet-flash:'saucy-preinstalled-touch-armel+mako.zip'

Related branches

Revision history for this message
Andy Doan (doanac) wrote :

We've stopped using UTAH to provision touch devices in our CI loop. However, your testing needs are a bit different. I'll take a look at getting this fixed today/tommorrow.

Changed in utah:
importance: Undecided → High
assignee: nobody → Andy Doan (doanac)
Revision history for this message
Andy Doan (doanac) wrote :

This actually seems to be a problem with phablet-tools. I can re-create easily at home:

 phablet-flash cdimage-touch -s $NEXUS7 --pending -b

Colin - That said, you might want to add "--ubuntu-bootstrap" to your run_utah_phablet.py arguments so that you test the new system-images rather than the older style cdimage-touch build.

Changed in utah:
importance: High → Undecided
affects: utah → phablet-tools
Changed in phablet-tools:
assignee: Andy Doan (doanac) → nobody
Revision history for this message
Sergio Schvezov (sergiusens) wrote :

The problem is that phablet-flash hasn't changed; s/saucy/trusty/ for old cdimage based images

Changed in phablet-tools:
status: New → Confirmed
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:phablet-tools at revision 218, scheduled for release in phablet-tools, milestone Unknown

Changed in phablet-tools:
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package phablet-tools - 1.0+14.04.20131030.2-0ubuntu1

---------------
phablet-tools (1.0+14.04.20131030.2-0ubuntu1) trusty; urgency=low

  [ Sergio Schvezov ]
  * phablet-flash: Adding a friendly error message when device detection
    fails. (LP: #1228129)
  * Using wait_for_recovery when flashig. (LP: #1215436)
  * Provide some information of revision/version and channel used when
    flashing. (LP: #1233800)
  * phablet-flash: Switching default from saucy to trusty for cdimage-
    touch. (LP: #1245569)
  * phablet-flash: not formatting data when already on a system image
    and not doing a bootstrap and removing support from cdimage ->
    upgradable image backup support. --no-backup is a deprecated option.
    (LP: #1218270)

  [ Andy Doan ]
  * get error information from phablet-config package installation Since
    adb-shell sends the actual stderr via stdout, we were hiding the key
    information to a user if a package failed to install. This prints it
    out for them.
  * remove an incorrect logging statement about rebooting the device.

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 220
 -- Ubuntu daily release <email address hidden> Wed, 30 Oct 2013 18:06:01 +0000

Changed in phablet-tools (Ubuntu):
status: New → Fix Released
Changed in phablet-tools:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.