New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cloud-init switch has no function #642
Comments
Thank you for report. This bug doesn't depends on templates, thus even if create new VM with empty template and start it with VmPortal it still gonna not work. Created bug on Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1593239 |
@leistnerova engine master has been fixed. Can you test this? |
cloud init script (some write_files) ran successfully for new VM created in the VM portal tested in ovirt-engine-4.3.0-0.0.master.20180802141038.gitd9dc74f.el7.noarch |
Thanks @leistnerova! I think ovirt-web-ui-1.3.6-1.el7.centos.noarch is the latest in the repo (due to a bug), but it's best to test with the latest version, which is 1.4.1. Until we fix the repo issue, you can grab the latest rpms from https://github.com/oVirt/ovirt-web-ui/releases currently 1.4.1 = https://github.com/oVirt/ovirt-web-ui/releases/tag/1.4.1 Would you mind retesting with the latest? :) |
No problem, file on new VM created with cloud-init also in ovirt-web-ui-1.4.1-1.fc28.noarch |
awesome, thanks @leistnerova! |
description
Cloud-init doesn't work. Enabling this setting does not pass down the settings to virtual machine
Expected results
Virtual machine should have an additional cdrom drive attached with config-2 labeled cd containing the given cloud-init user settings, so cloud-init service would pick up that data and perfom required steps.
Actual results:
Vm is started without the emulated config-2 drive, so cloud-init can't find user specified settings. (check
blkid
commandSteps to reproduce:
1.1. create a linux based (cloud-init enabled but not yet run) vm
1.2. create a template based on this vm (seal template enabled)
1.3. enable cloud-init (with empty hostname, prefill custom-script) on this template
2.1. create a new vm based on the given template
2.2. checke cloud-init is enabled an a proper hostname (copied from vm-name) is set
2.3. start vm by clicking "run"
Affected Version
Remarks
This may be a engine problem too, as cloud-init config drive isn't created when started "run" instead of "run once" even if cloud-init/sysprep is enabled in vm settings
The text was updated successfully, but these errors were encountered: