Race condition on boot for Wi-Fi interfaces with wpa_supplicant

[vbooh]

Wi-Fi interfaces, that use configuration file /etc/network/interfaces and wpa_supplicant package, should be bring up after mounting /run, because wpa_supplicant uses /run mountpoint. In other case sometimes on boot Wi-Fi connection can be established properly, sometimes can not. In logs I can see:
/var/log/upstart/network-interface-wlan0.log

mkdir[ctrl_interface]: No such file or directory
wpa_supplicant: /sbin/wpa_supplicant daemon failed to start
run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1

Proposed patch is not the best solution, but I can not get working solution with "mounted MOUNTPOINT=/run" instead of "filesystem". If I use "mounted MOUNTPOINT=/run", I do not get any errors messages using "initctl check-config" and "init-checkconf -d /etc/init/network-interface.conf", init just does not want start on boot, there is black screen after bootloader even without 'quite splash' kernel parameters and with '--debug' kernel parameter, there is no records in logs.

Also there is another workaround or dirty hack, but it should not affect network filesystems mount, see attachment "network-interface.conf.workaround".

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "network-interface.conf.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

[Stéphane Graber (stgraber)]

The proposed patch won't work as it's not rare to have network filesystems which would make this patch cause a deadlock.

I also doubt that /run is the problem there, or you're running a very weird setup that's not really supported under Ubuntu...
Ubuntu mounts / and /run from the initrd before starting upstart, so in theory it's impossible to get kernel events before /run is mounted and writable.

[vbooh (vbooh-vbooh)]

Here is some system info.

[vbooh (vbooh-vbooh)]

Another workaround or dirty hack, but it should not affect network filesystems mount.