/etc/modules-load.d missing from writable-paths, used by snappy firstboot

Bug #1511464 reported by Simon Eisenmann on 2015-10-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snappy
Undecided
Unassigned

Bug Description

Oct 29 16:51:55 localhost.localdomain systemd[1]: Starting Run snappy firstboot setup...
Oct 29 16:51:55 localhost.localdomain snappy[799]: open /etc/modules-load.d/ubuntu-core.conf.tmQQxGVXiMGK: read-only file system
Oct 29 16:51:55 localhost.localdomain /usr/bin/snappy[799]: main.go:57: DEBUG: [/usr/bin/snappy firstboot] failed: open /etc/modules-load.d/ubuntu-core.conf.tmQQxGVXiMGK: read-only file system
Oct 29 16:51:55 localhost.localdomain systemd[1]: ubuntu-snappy.firstboot.service: main process exited, code=exited, status=1/FAILURE

This happens if an OEM snap contains load-kernel-modules to load some kernel modules on boot (15.04/stable).

Simon Eisenmann (longsleep) wrote :

From IRC we found that this was already patches recently (https://launchpadlibrarian.net/223054208/ubuntu-core-config_0.6.15%2Bppa24_0.6.15%2Bppa25.diff.gz) and will be in the next build.

Michael Vogt (mvo) wrote :

This is fixed in snappy 16

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

Other bug subscribers