uncloud-init updates.tar doesn't work

Bug #871297 reported by Ed Swierk
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Fix Released
Low
Unassigned
cloud-init (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

uncloud-init apparently tries to allow updating the filesystem from an updates.tar tarball (itself contained within the xupdate tarball or filesystem image).

But in the updateFrom function, it ignores updates.tar unless it's a directory:

  if [ -d "${mp}/updates.tar" ]; then
    ...

This looks like a copy-and-paste bug from the code above, which is checking for a directory called updates. The obvious fix is to change the -d to -f.

Related branches

Revision history for this message
Scott Moser (smoser) wrote :

fixed in revision 460.

Changed in cloud-init:
status: New → Fix Committed
importance: Undecided → Low
Changed in cloud-init (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Scott Moser (smoser) wrote :

This is borderline of low and wishlist.
uncloud-init should not be used. It is really a legacy hack.

We need to
a.) change documentation at https://help.ubuntu.com/community/UEC/Images to not reference uncloud-init
b.) provide tools or documentation to use the fully functional and more easily supported OVF transport for doing "non-cloud" tests.

Scott Moser (smoser)
Changed in cloud-init:
status: Fix Committed → Fix Released
Revision history for this message
Scott Moser (smoser) wrote :

fix-released with 0.6.2-0ubuntu1

Scott Moser (smoser)
Changed in cloud-init (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
James Falcon (falcojr) wrote :
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.