Fails to create a snappy image when using --install

Bug #1464054 reported by Ricardo Salveti
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Snappy
Status tracked in Trunk
15.04
Fix Released
Undecided
Sergio Schvezov
Trunk
Fix Released
Undecided
Sergio Schvezov
goget-ubuntu-touch (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Using ubuntu-device-flash 0.23-0ubuntu2 on vivid, I can't create a snappy image using the extra --install parameter (to bundle a snap from the store).

It works fine without using --install.

$ sudo ubuntu-device-flash core 15.04 --channel stable --oem beagleblack --install=hello-world --enable-ssh --output ubuntu-15.04-snappy-armhf-bbb.img
Determining oem configuration
Starting download of beagleblack
280.75 KB / 280.75 KB [===========================================================================] 100.00 % 69.87 KB/s
Done
Fetching information from server...
Downloading and setting up...
Installing beagleblack
Starting download of beagleblack
280.75 KB / 280.75 KB [===========================================================================] 100.00 % 96.10 KB/s
Done
Installing hello-world
Starting download of hello-world
21.55 KB / 21.55 KB [===========================================================================] 100.00 % 77.02 KB/s
Done
panic: unable to unmount dir for image: umount: /tmp/diskimage898827634/system: target is busy
        (In some cases useful info about processes that
         use the device is found by lsof(8) or fuser(1).)

goroutine 1 [running, locked to thread]:
launchpad.net/goget-ubuntu-touch/diskimage.(*CoreUBootImage).Unmount(0xc2080e4420, 0x0, 0x0)
 /build/buildd/goget-ubuntu-touch-0.23/obj-x86_64-linux-gnu/src/launchpad.net/goget-ubuntu-touch/diskimage/core_uboot.go:115 +0x67d
main.func·006()
 /build/buildd/goget-ubuntu-touch-0.23/obj-x86_64-linux-gnu/src/launchpad.net/goget-ubuntu-touch/ubuntu-device-flash/core.go:341 +0x120
main.(*CoreCmd).setup(0xcf0920, 0x7efd782dbd80, 0xc2080e4420, 0xc2082a0720, 0x3, 0x0, 0x0)
 /build/buildd/goget-ubuntu-touch-0.23/obj-x86_64-linux-gnu/src/launchpad.net/goget-ubuntu-touch/ubuntu-device-flash/core.go:405 +0x1753
main.func·004(0x0, 0x0)
 /build/buildd/goget-ubuntu-touch-0.23/obj-x86_64-linux-gnu/src/launchpad.net/goget-ubuntu-touch/ubuntu-device-flash/core.go:280 +0x171
main.(*CoreCmd).Execute(0xcf0920, 0xc20800a0b0, 0x1, 0xb, 0x0, 0x0)
 /build/buildd/goget-ubuntu-touch-0.23/obj-x86_64-linux-gnu/src/launchpad.net/goget-ubuntu-touch/ubuntu-device-flash/core.go:285 +0x20d9
github.com/jessevdk/go-flags.(*Parser).ParseArgs(0xc2080566c0, 0xc20800a000, 0xb, 0xb, 0x0, 0x0, 0x0, 0x0, 0x0)
 /build/buildd/goget-ubuntu-touch-0.23/obj-x86_64-linux-gnu/src/github.com/jessevdk/go-flags/parser.go:241 +0x8b8
main.main()
 /build/buildd/goget-ubuntu-touch-0.23/obj-x86_64-linux-gnu/src/launchpad.net/goget-ubuntu-touch/ubuntu-device-flash/main.go:62 +0x3ac

goroutine 5 [syscall]:
os/signal.loop()
 /usr/lib/go/src/os/signal/signal_unix.go:21 +0x1f
created by os/signal.init·1
 /usr/lib/go/src/os/signal/signal_unix.go:27 +0x35

goroutine 6 [chan receive]:
launchpad.net/snappy/partition.func·005()
 /build/buildd/goget-ubuntu-touch-0.23/obj-x86_64-linux-gnu/src/launchpad.net/snappy/partition/partition.go:270 +0x52
created by launchpad.net/snappy/partition.setupSignalHandler
 /build/buildd/goget-ubuntu-touch-0.23/obj-x86_64-linux-gnu/src/launchpad.net/snappy/partition/partition.go:275 +0x21e

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
 /usr/lib/go/src/runtime/asm_amd64.s:2232 +0x1

goroutine 58 [chan receive]:
main.func·003()
 /build/buildd/goget-ubuntu-touch-0.23/obj-x86_64-linux-gnu/src/launchpad.net/goget-ubuntu-touch/ubuntu-device-flash/core.go:261 +0x1e8
created by main.(*CoreCmd).Execute
 /build/buildd/goget-ubuntu-touch-0.23/obj-x86_64-linux-gnu/src/launchpad.net/goget-ubuntu-touch/ubuntu-device-flash/core.go:264 +0x2015

Related branches

description: updated
Revision history for this message
Sergio Schvezov (sergiusens) wrote :

Can I get the output of lsblk?

Revision history for this message
Sergio Schvezov (sergiusens) wrote :

and the mount table before and after this happens?

Changed in goget-ubuntu-touch (Ubuntu):
status: New → Incomplete
Revision history for this message
Ricardo Salveti (rsalveti) wrote :
Download full text (14.3 KiB)

rsalveti@evasys:/tmp/snappy/new/stable$ mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=8159036k,nr_inodes=2039759,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1635104k,mode=755)
/dev/sdb1 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb,release_agent=/run/cgmanager/agents/cgm-release-agent.hugetlb)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset,clone_children)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event,release_agent=/run/cgmanager/agents/cgm-release-agent.perf_event)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=23,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/mapper/sda2_crypt on /home type ext4 (rw,relatime,data=ordered)
cgmfs on /run/cgmanager/fs type tmpfs (rw,relatime,size=100k,mode=755)
lxcfs on /var/lib/lxcfs type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1635104k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
rsalveti@evasys:/tmp/snappy/new/stable$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 190M 0 part
├─sda2 8:2 0 1K 0 part
└─sda5 8:5 0 465.6G 0 part
  ├─vgroup-root 252:0 0 46.6G 0 lvm
  ├─vgroup-swap 252:1 0 1.9G 0 lvm
  └─vgroup-home 252:2 0 417.2G 0 lvm
sdb ...

Changed in goget-ubuntu-touch (Ubuntu):
status: Incomplete → Confirmed
Changed in snappy:
status: New → Fix Committed
assignee: nobody → Sergio Schvezov (sergiusens)
Revision history for this message
Ash Charles (ashcharles) wrote :

Is there an updated version of the package available? I'm also seeing this on 0.23-0ubuntu2 of the ubuntu-device-flash package but I couldn't see if a more recent version had been made available in a PPA that includes this fix.

Revision history for this message
Ash Charles (ashcharles) wrote :

I used the package version 0.27-0ubuntu1 from https://launchpad.net/~snappy-dev/+archive/ubuntu/tools-proposed which included the fix.

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.