Desktop installation type not correctly detected in daily image
Bug #1043174 reported by
Javier Collado
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| UTAH |
Fix Released
|
Medium
|
Javier Collado | ||
Bug Description
When trying to use the desktop daily image to provision a VM, I get the following error:
bsdtar: ./install/vmlinuz: Not found in archive
bsdtar: Error exit delayed from previous errors.
When debugging the code, I see that the real problem is that the installation type is set to `alternate` instead of `desktop`. With more investigation, I see that the output from utah.iso.listfiles contains `./casper` in an old image while the output for the new ones contains `casper` and thus the test to get the installation type fails and it considers it to be an alternate image.
Related branches
lp:~javier.collado/utah/bug1043174
- Max Brustkern (community): Approve
-
Diff: 17 lines (+2/-2)1 file modifiedutah/iso.py (+2/-2)
| Changed in utah: | |
| status: | New → In Progress |
| importance: | Undecided → Medium |
| assignee: | nobody → Javier Collado (javier.collado) |
| Changed in utah: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
