'UTAHProvisioningException: Failed to install client' on raring server provisioning after update to utah-client_0.5ubuntu15-r769~precise1_all.deb

Bug #1087288 reported by Para Siva
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
UTAH
Fix Released
Critical
Max Brustkern

Bug Description

The raring server tests are failing to installl utah client after provisioning with the following error. This seems to happen only after the upgrade from utah-client_0.5ubuntu14-r759~precise1_all.deb to utah-client_0.5ubuntu15-r769~precise1_all.deb

2012-12-06 14:42:08,809 utah-1644-raring-server-amd64 INFO: Running command through SSH: DEBIAN_FRONTEND=noninteractive; while (fuser /var/lib/dpkg/lock >/dev/null 2>&1); do echo "Waiting for dpkg lock to become available"; sleep 10; done ; gdebi -n -q /tmp/utah-client_0.5ubuntu15-r769~precise1_all.deb
2012-12-06 14:42:10,471 utah-1644-raring-server-amd64 WARNING: Return code: 1
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/utah/run.py", line 113, in run_tests
    machine.installclient()
  File "/usr/lib/python2.7/dist-packages/utah/provisioning/provisioning.py", line 400, in installclient
    raise UTAHProvisioningException('Failed to install client\n')
UTAHProvisioningException: Failed to install client

This will impact all the server tests and the failure is going to be quite high in number.

https://jenkins.qa.ubuntu.com/view/Raring/view/Smoke%20Testing/job/raring-server-amd64-smoke-lamp/19/console
https://jenkins.qa.ubuntu.com/view/Raring/view/Smoke%20Testing/job/raring-server-amd64-smoke-floodlight/22/console
https://jenkins.qa.ubuntu.com/view/Raring/view/Smoke%20Testing/job/raring-server-i386-smoke-floodlight/21/console

Are some examples

Related branches

Para Siva (psivaa)
Changed in utah:
importance: Undecided → Critical
Changed in utah:
status: New → Triaged
assignee: nobody → Max Brustkern (nuclearbob)
Changed in utah:
status: Triaged → Fix Committed
Changed in utah:
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.