On 09/05/2014 10:46 AM, Sven Kieske wrote:
>
>
> Am 05.09.2014 10:27, schrieb Juan Hernandez:
>> Trying to make an example for this I discovered that the "custom_script"
>> element is currently ignored if the "cloud_init" element is present.
>> Instead we are taking the content of the first "file" element from the
>> "cloud_init" element and appending it to the cloud-init configuration
>> file. I believe that this is a bug, as it breaks backwards compatibility:
>>
>>   https://bugzilla.redhat.com/1138564
>
> Thanks for the report, I just proposed this as a blocker for the 3.4.4
> release as it is a clear regression.
> Also I rely on this functionality in my 3.3. setup and I want to upgrade
> to 3.4 so I can't upgrade until this is fixed and released.

Agree, I set the bug as a blocker for 3.4.4.

>>
>> However, you can exploit this bug to do what you want. This is an example:
>
> Well I guess this is a pretty bad idea, because it will just work
> until the bug is fixed?
>

No, what I proposed in the example is to put the custom script in both
the first "file" inside "clud_init" and in the "custom_script" element.
That should work with the current status and also if/when we fix the bug.

--
Dirección Comercial: C/Jose Bardasano Baos, 9, Edif. Gorbea 3, planta
3ºD, 28016 Madrid, Spain
Inscrita en el Reg. Mercantil de Madrid – C.I.F. B82657941 - Red Hat S.L.

_______________________________________________
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users