Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1051041

Summary:	cloud-init options persistence / unification with sysprep options
Product:	[Retired] oVirt	Reporter:	Michal Skrivanek <michal.skrivanek>
Component:	ovirt-engine-webadmin	Assignee:	Shahar Havivi <shavivi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Novotny <pnovotny>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.4	CC:	acathrow, ecohen, iheim, mavital, mgoldboi, yeylon
Target Milestone:	---	Keywords:	Triaged
Target Release:	3.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:	ovirt-3.4.0-beta2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1057998 (view as bug list)		Environment:
Last Closed:	2014-03-31 12:23:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1057998

Description Michal Skrivanek 2014-01-09 15:41:17 UTC

cloud-init options are currently only in Run Once.

Feature is about making it fully persistent (in Edit VM dialog) and also to unify with the existing Windows solution (sysprep). Refactor to reuse code and provide
cloud-init for Linux-based OSes and Sysprep for Windows with similar look and feel and similar set of options and possibilities for customization

Comment 1 Shahar Havivi 2014-01-09 16:03:10 UTC

posted at:
http://gerrit.ovirt.org/23020
http://gerrit.ovirt.org/23021
http://gerrit.ovirt.org/23022
http://gerrit.ovirt.org/23023

Comment 2 Shahar Havivi 2014-01-09 16:04:16 UTC

Feature page:
http://www.ovirt.org/Features/vm-init-persistent

Comment 3 Pavel Novotny 2014-03-20 18:10:35 UTC

Verified in downstream rhevm-3.4.0-0.9.beta1.el6ev (av3.1).

Cloud-Init data (sysprep data for Windows-based VMs) can be now persistently saved as part of VM the profile.

Verification:
1. In GUI create a Linux-based VM with following Cloud-Init data (under Initial Run section):
-~-
VM Hostname: vm-cloud-init-persistent
Time Zone: Hawaiian Standard Time
/Authentication/
Root Password: 654321
Verify Root Password: 654321
SSH Authorized Keys: ssh-rsa vm-init-persistent-sshpubkey root@localhost
Regenerate SSH Keys: True
/Networks/
DNS Servers: 10.20.30.40
DNS Search Domains: domain.example.com
Network: eth0
Use DHCP: True
Start on Boot: True
Custom Script:
write_files:
-   content: |
        # THIS IS MY TEXT FILE
        Some Content for my file
    path: /tmp/myfile
    permissions: '0644'
-~-
2. Open VM run once dialog and check parameters in the Initial Run section. They should be the same as defined on the VM - Initial Run in step 1. Note that no sensitive data should be disclosed here (user passwords).
3. Submit the dialog (run the VM) and after VM is up, log in and check that all parameters set in step 1 were applied.

Additional notes: there is known bug 1063518, where user is not allowed to log in to the guest with provided SSH public key.

Comment 4 Sandro Bonazzola 2014-03-31 12:23:13 UTC

this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released