Snappy

upgrade wily/edge 199->201 failed

Bug #1505682 reported by John Lenton on 2015-10-13
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
​ Snappy
Invalid
Critical
Unassigned
Also affects project (?) Also affects distribution/package Nominate for series

Bug Description

snappy is calling system-image on / instead of /writable/cache/system because /writable/cache/system/etc/system-image/config.d/00_default.ini is a dangling symlink. We should (probably?) test for 20_snappy.ini instead.

/writable/cache/system/ is 197.

See original description
Michael Vogt (mvo) on 2015-10-13
Changed in snappy:
status: New → Triaged
importance: Undecided → Critical
milestone: none → 15.04.4
milestone: 15.04.4 → none
description: updated
John Lenton (chipaca) wrote :

and http://people.canonical.com/~john/wily.img.xz has the image I was using, via:
kvm -vga qxl -snapshot -redir :8022::22 -redir :4200::4200 -redir :8080::8080 -m 2048 wily.img

Michael Vogt (mvo) wrote :

<barry> mvo: cool. si 3.0.2 in wily at least no longer crashes on dangling symlinks, but i don't think we ever tracked down why the symlink is dangling
<barry> (don't think it is on touch)

Leo Arias (elopio) wrote :

we are no longer using system-image for snappy updates.

Changed in snappy:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.
Subscribing...

Other bug subscribers