Bug 1072764

Summary:	Cloud-init is enabled in the UI for non-Linux hosts but it doesn't do anything
Product:	[Retired] oVirt	Reporter:	Oved Ourfali <oourfali>
Component:	ovirt-engine-core	Assignee:	Shahar Havivi <shavivi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Novotny <pnovotny>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.4	CC:	gklein, herrold, iheim, mavital, ofrenkel, rbalakri, shavivi, s.kieske, yeylon
Target Milestone:	---	Keywords:	Triaged
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:	ovirt-3.5.0-alpha1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-10-17 12:41:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Oved Ourfali 2014-03-05 07:26:00 UTC

Description of problem:
When you choose "Other OS" in the UI, you still get an option to configure cloud-init, but when you launch the VM it doesn't really do anything

How reproducible:
Always

Steps to Reproduce:
1. Create a VM, with Other OS type
2. Set cloud-init properties
3. Run the VM (either via run or run-once. If using run-once set the cloud-init properties there).

Actual results:
Nothing happens with regards to cloud-init

Expected results:
When the option exist in the UI then it should pass it to the VM. So we should either decide to block it also for "Other OS", or pass it to the VM.

Additional info:
Didn't test other OS types.

Comment 1 Sven Kieske 2014-03-05 15:30:30 UTC

I would suggest to pass the data to the vm (maybe ad a warning that you need cloud-init inside the vm), because other systems may rely on this function, e.g.
*BSD variants.

By not allowing this you would raise a high barrier for autoconfiguration
of other vm os types.

Comment 2 Omer Frenkel 2014-03-06 09:02:28 UTC

basically there is no reason to use "Other OS", even for *BSD i would choose "Linux"
but i agree we can send cloud init to "Other" as well, specially that we display the UI for the user..

Comment 3 Oved Ourfali 2014-03-06 09:29:22 UTC

(In reply to Omer Frenkel from comment #2)
> basically there is no reason to use "Other OS", even for *BSD i would choose
> "Linux"
> but i agree we can send cloud init to "Other" as well, specially that we
> display the UI for the user..

I'm okay with either "protecting" the user, and just not showing that in the UI for non-linux OS, or just show and send it, but I prefer the former.

Comment 4 Shahar Havivi 2014-03-09 15:25:41 UTC

the cloud init should be enable for non windows os for now

Comment 5 Pavel Novotny 2014-08-01 13:57:47 UTC

Verified in ovirt-engine-3.5.0-0.0.master.20140722232058.git8e1babc.el6.noarch (beta2).

The config drive CD with cloud-init data is attached for all VMs with OS type different than Windows, i.e., currently for Debian, FreeBSD, Linux, OtherOS, RHEL, SUSE and Ubuntu.

Comment 6 Sandro Bonazzola 2014-10-17 12:41:22 UTC

oVirt 3.5 has been released and should include the fix for this issue.