+++ This bug was initially created as a clone of Bug #1051041 +++
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
--- Additional comment from Shahar Havivi on 2014-01-09 11:03:10 EST ---
--- Additional comment from Shahar Havivi on 2014-01-09 11:04:16 EST ---
Verified in 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.
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
Root Password: 654321
Verify Root Password: 654321
SSH Authorized Keys: ssh-rsa vm-init-persistent-sshpubkey root@localhost
Regenerate SSH Keys: True
DNS Servers: 10.20.30.40
DNS Search Domains: domain.example.com
Use DHCP: True
Start on Boot: True
- content: |
# THIS IS MY TEXT FILE
Some Content for my file
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.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.