UTAH provisioning failed with: UTAHProvisioningException: Failed to install client
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
UTAH |
Fix Released
|
High
|
Max Brustkern |
Bug Description
Provisioning a physical system with UTAH fails from time to time with:
"ERROR: Failed to install client. Writing empty reports."
For example the log attached is the installation of Raring Ubuntu Desktop on Hardware:
"""
[...]
+ ISO=/data/
+ run_utah_tests.py -m physical --name dx-autopilot-ati -i /data/iso/
[...]
2013-01-07 18:03:12,595 dx-autopilot-ati INFO: Running command through SSH: DEBIAN_
2013-01-07 18:03:13,994 dx-autopilot-ati WARNING: Return code: 1
Traceback (most recent call last):
File "/usr/lib/
machine.
File "/usr/lib/
raise UTAHProvisionin
UTAHProvisionin
2013-01-07 18:03:13,996 dx-autopilot-ati ERROR: Failed to install client. Writing empty reports.
[...]
"""
This is blocking daily testing of Unity.
summary: |
- UTAH failed to provision old images + UTAH provisioning failed with: UTAHProvisioningException: Failed to + install client |
description: | updated |
Changed in utah: | |
status: | Confirmed → In Progress |
tags: | added: ue-desktop |
I've recreated this issue in a UTAH-installed VM, but a manually installed VM worked fine. Something in the preseed we're using is resulting in a partially failed packaged installation. I'm trying to minimize the preseed involved to determine whether it's a dependency of UTAH or autopilot.