Comment # 5 on bug 1093501 from Robert Schweikert

After receiving additional input and based on what was already known I have
decided to drop the generator from our package.

The generator, which in turn runs ds-identify, where the problem is created by
using blkid, speeds up the boot process in cases where cloud-init shold not be
running in the first place. The chain of events is as follows:

generator runs ds-identify
if ds-identify cannot find a data source the cloud-init services are disabled

With cloud-init disabled the boot is sped up as no Python code gets executed.

A reasonable assumption is that the person installing and enabling cloud-init
knows they run in environment where cloud-init is needed. Thus looking for the
data source twice, once in ds-identify and then again in the cloud-init Python
code is not really an advantage.

Dropping the generator avoids the problem with blkid and it avoids looking for
the data source twice, once in shell code and once in Python code.

Change is on the way to Factory