missing ramdisks in latest amd64 kernel snap

[Federico Gimenez]

While running the snapd suite using the amd64 kernel snap from the beta channel (rev 59) we got this error running [1]:

2017-03-30 09:36:41 Error preparing linode:ubuntu-core-16-64:tests/main/snap-auto-mount :
-----
[ ... ]
Create a ramdisk with the testrootorg-store.account-key assertion
+ mkfs.vfat /dev/ram0
/dev/ram0: No such file or directory
mkfs.fat 3.0.28 (2015-05-16)

There are no /dev/ram* files on the ubuntu-core system, not sure if this is intended and we should adapt to it. It was created with:

$ sudo /snap/bin/ubuntu-image --image-size 3G -c beta -O . ./models/pc-amd64.model

and, once logged to the ubuntu-core system, the version:

$ $ cat /proc/version_signature
Ubuntu 4.4.0-67.88-generic 4.4.49

Thanks,

[1] https://github.com/snapcore/snapd/blob/master/tests/main/snap-auto-mount/task.yaml

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1677622

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Federico Gimenez (fgimenez)]

The oroblem happens on an amd64 ubuntu-core system, no apport-collect in there, please let me know how can I get the required logs on that system.

[Paolo Pisati (p-pisati)]

I don't understand if it's a regression you are pointing out or what else, because i see a consistent behaviour on my destktop: the mkfs.extX cmd, if it doesn't find a ramdisk, it creates one, while mkfs.vfat simply fails out - so you either runs that test with a ramdisk previously created, or you change you change the filesystem, or it will forever fail with vfat. Was that test run before? What was the environment?

mkfs.ext2 /dev/ram7 8192:
...
open("/dev/ram7", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/dev/ram7", O_RDONLY|O_CREAT, 0666) = 3

mkfs.vfat /dev/ram8 8192:
...
open("/dev/ram8", O_RDONLY) = -1 ENOENT (No such file or directory)
dup(2) = 3
fcntl(3, F_GETFL) = 0x8001 (flags O_WRONLY|O_LARGEFILE)
close(3) = 0
write(2, "/dev/ram8: No such file or direc"..., 37/dev/ram8: No such file or directory
) = 37

[Federico Gimenez (fgimenez)]

Yes, the same test is currently passing on rev 55 (edge) [1], the /dev/ramX files are there after booting [2], and starting with rev 59 that files are missing and the tests fail [3].

[1] https://travis-ci.org/snapcore/spread-cron/builds/216734158
[2] http://paste.ubuntu.com/24306876/
[3] https://travis-ci.org/snapcore/spread-cron/builds/211518618

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]