Package: fai Version: 3.4.8 Severity: normal Tags: patch I've uploaded a change to ubuntu with the following changelog:
fai (3.4.8ubuntu2) precise; urgency=low
* In the case FAI is started in an Upstart environment, check if an
upstart job udevtrigger exists. If it does, we really need to start
this job so that "missed" kernel events are replayed. Otherwise may
miss block events. This results in block devices having "wrong" owners
and confuses the FAI "disk-info" utility, which in turn breaks the
disk detection completely. LP: #941959
-- Reinhard Tartler <siret...@tauware.de> Tue, 20 Mar 2012 10:46:12 +0100
Bug filed in ubuntu as https://bugs.launchpad.net/ubuntu/+source/fai/+bug/941959
Please consider this attached patch:
https://launchpadlibrarian.net/97523991/fai_3.4.8ubuntu1_3.4.8ubuntu2.diff.gz
-- System Information:
Debian Release: wheezy/sid
APT prefers precise-updates
APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500,
'precise-proposed'), (500, 'precise')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-19-generic (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
fai_3.4.8ubuntu1_3.4.8ubuntu2.diff.gz
Description: GNU Zip compressed data
