On 05.05.14 11:01, Tamás Millián wrote:

Hey,

I noticed that if I create a template and virtual machine based on that template the cloud-init configuration of the VM will always mirror the template's. It can not even be changed in the VM's settings. This is not very handy for the network part where static IP's may be set. This seems to apply to the "run-once" option too, even if I specify different options, half of them just seem to get lost in the process. Hey, What are the lost options that you referring to?

The steps I did to end up here: 1, import the CentOS machine (7df3c30) from the public ovirt-image repository as a template 2, update the template configuration and enable cloud-init with some settings and a custom script 3, create a VM based on the template 4, try to edit the VM and change the cloud-init configuration <-- the dialog disappears after saving, but the settings are unchanged 5, try to run the vm with the run-once options and change the cloud-init configuration in the pop-up <-- the vm starts and the configuration does not seem to have changed I just try similar scenario from upstream code, Created a new Linux template - set the cloud-init with hostname, Dns-Server, Dns-Search domain, and a static IP with subnet and gateway. Created a VM from this template and edited all the above fields, The VM new fields was saved. I also try the Run Once dialog and saw all the values that I set.

You may encounter an error in the saving process that prevent you from saving the new values, you can try by looking at the engines log: ovirt/var/log/ovirt-engine/engine.log You can also try to update other values in the same update such as the VM name and look if the VM was updated. Shahar Havivi.

Is this the expected behaviour or am I doing something wrong?

Thanks,

Tamás

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