This bug was fixed in the package fai - 3.4.8ubuntu2
---------------
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 <email address hidden> Tue, 20 Mar 2012 10:46:12 +0100
This bug was fixed in the package fai - 3.4.8ubuntu2
---------------
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 <email address hidden> Tue, 20 Mar 2012 10:46:12 +0100