Cloud-init doesn't work with the RHV provider.

[oysterme1ster]

I have two VM provision and customization scenarios:

Scenario №1: Provision a VM from a Generic Service
Scenario №2: Provision a VM from an RHV Service.

In Scenario №1, when I provision a virtual machine through a Generic Service,

cloud-init customization doesn't work. The template for customization is selected in the redhat_CustomizeRequest method and is passed to miq_provision.options, which can be verified by calling object_walker in the corresponding method:

Customization options are passed to the provision_request, but the customization doesn't work in practice, and according to the cloud-init logs, the configuration CD is not mounted during VM creation.

In Scenario №2, I order a virtual machine from the same VM template and apply the same customization_template to it, but I do it through an RHV-type service:

and in this case, everything works. In the object_walker output, I see the same customization parameter values:

And in the Cloud-Init logs, it can be seen that a disk with customization configuration is mounted to the VM.

Question:
Why are the customization_template parameters passed to miq_provision in both scenarios, but customization doesn't work in the first scenario?

[oysterme1ster]

resolved:
prov.set_option(:sysprep_enabled, ["fields, "Specication"])

[Fryguy]

Typo - should probably be

prov.set_option(:sysprep_enabled, ["fields, "Specification"])

[Fryguy]

Thanks @oysterme1ster .

cc @agrare Is this kind of what we ran into the other day?