Snapcraft

snapcraft run fails with: cannot determine partition label for rootfs

Bug #1484720 reported by Leo Arias
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snapcraft
Fix Released
Undecided
Unassigned
Snapcraft 0.2

Bug Description

When I execute snapcraft run I get the following error:
unable to update grub: Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
ERROR: cannot determine partition label for rootfs /dev/mapper/loop1p3

elopio@calchas:~/workspace/canonical/snapcraft/trunk/examples/godd$ ./../../bin/snapcraft run
[sudo] password for elopio:
Malĝuste. Reprovu.
[sudo] password for elopio:
Determining oem configuration
Starting download of generic-amd64
41.70 KB / 41.70 KB [====================================] 100.00 % 118.57 KB/s
Done
Starting download of icon for package
38.97 KB / 38.97 KB [====================================] 100.00 % 193.56 KB/s
Done
Fetching information from server...
Downloading and setting up...
Installing generic-amd64
Starting download of generic-amd64
41.70 KB / 41.70 KB [====================================] 100.00 % 129.79 KB/s
Done
Starting download of icon for package
38.97 KB / 38.97 KB [====================================] 100.00 % 188.06 KB/s
Done
unable to update grub: Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
ERROR: cannot determine partition label for rootfs /dev/mapper/loop1p3

ssh: connect to host localhost port 8022: Connection refused
Waiting for device
ssh_exchange_identification: read: Connection reset by peer
Waiting for device

Tags: first-steps
Leo Arias (elopio)
no longer affects: goget-ubuntu-touch (Ubuntu)
Revision history for this message
Daniel Holbach (dholbach) wrote :

For me it is:

daniel@daydream:~/dev/apps/bwm-ng.snap$ ../../snappy/snapcraft/bin/snapcraft runUsing the following ssh key: /home/daniel/.ssh/ubuntudevice_0149BDCB0C009017_id_rsa
[sudo] Passwort für daniel:
Determining oem configuration
Starting download of generic-amd64
41.70 KB / 41.70 KB [====================================] 100.00 % 271.04 KB/s
Done
Starting download of icon for package
38.97 KB / 38.97 KB [===========================================================================================================] 100.00 % 527.74 KB/s
Done
Fetching information from server...
Downloading and setting up...
error while executing external command kpartx -ds /home/daniel/dev/apps/bwm-ng.snap/image/15.04.img: device-mapper: remove ioctl on loop0p5 failed: Device or resource busy
loop deleted : /dev/loop0

Running: ssh -i /home/daniel/.ssh/ubuntudevice_0149BDCB0C009017_id_rsa -oStrictHostKeyChecking=no -oUserKnownHostsFile=/tmp/tmpuptxxb01 -oKbdInteractiveAuthentication=no ubuntu@localhost -p 8022 true
ssh: connect to host localhost port 8022: Connection refused
Waiting for device

(process:12323): GLib-WARNING **: /build/glib2.0-3tdlHy/glib2.0-2.45.6/./glib/gmem.c:482: custom memory allocation vtable not supported
Running: ssh -i /home/daniel/.ssh/ubuntudevice_0149BDCB0C009017_id_rsa -oStrictHostKeyChecking=no -oUserKnownHostsFile=/tmp/tmpuptxxb01 -oKbdInteractiveAuthentication=no ubuntu@localhost -p 8022 true
ssh_exchange_identification: read: Connection reset by peer
Waiting for device

tags: added: first-steps
Revision history for this message
Leo Arias (elopio) wrote :

Daniel, I no longer have this issue. Do you still have it?

I have this instead: https://bugs.launchpad.net/snapcraft/+bug/1497108

Changed in snapcraft:
status: New → Incomplete
Revision history for this message
Daniel Holbach (dholbach) wrote :

Yep, fixed for me.

Changed in snapcraft:
status: Incomplete → Fix Committed
milestone: none → 0.2
Daniel Holbach (dholbach)
Changed in snapcraft:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.