Bug 1448831
Summary: | Issues with automating the configuration of VMs (cloud-init) | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Olimp Bockowski <obockows> | |
Component: | ovirt-engine | Assignee: | jniederm | |
Status: | CLOSED ERRATA | QA Contact: | Vladimir <vshypygu> | |
Severity: | medium | Docs Contact: | ||
Priority: | high | |||
Version: | 4.0.6 | CC: | apinnick, lsurette, mgoldboi, michal.skrivanek, mtessun, obockows, rbalakri, Rhev-m-bugs, srevivo, tjelinek, vshypygu, ykaul | |
Target Milestone: | ovirt-4.2.0 | Keywords: | ZStream | |
Target Release: | --- | Flags: | lsvaty:
testing_plan_complete-
|
|
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | rhevm‑4.2‑ga | Doc Type: | Bug Fix | |
Doc Text: |
Previously, when creating a new virtual machine from a template with cloud-init configured, the virtual machine was created but the stored root password was not copied over. In the current release, the stored root password is copied to the new virtual machine.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1463597 (view as bug list) | Environment: | ||
Last Closed: | 2018-05-15 17:42:49 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1463597 |
Description
Olimp Bockowski
2017-05-08 10:43:03 UTC
Do you have cloud-init logs when it failed? The payload? Just to report on the progress of this issue: - I have succeeded to simulate this issue on 4.1 while creating a VM from template on a template tab (happened only once and only in this flow, in no others) - it is not related to cloud init directly, it is an engine issue because while creating a VM from template, vm init configuration was not properly copied from the template to the VM (in the database) - the payload was correctly created and attached to the VM according to the configuration which was in the DB. Given the configuration for some reason did not contain the password, it was not in the payload. I don't yet know why and if it is a frontend or backend issue - keep investigating. The issue is that when adding a VM from template with cloud-init configured, the cloud-init password needs to be updated by calling: vmHandler.updateVmInitFromDB(template, false); - nota bene the second param which tells that the password has to be loaded too. For pools I have not found a case where it is not loaded properly but for VMs made from template it happens. But, if the VM is based on the latest template, and the template is updated, the VM will get also the password from the latest template. So, we need to make sure the vmHandler.updateVmInitFromDB(template, false); is properly called always when creating a VM from template with password stored. Steps to reproduce: 1. Create a linux template with 'Initial Run' > 'Password' set 2. Create a VM based on the template 3. Run the VM 4. Run on host: strings </var/run/vdsm/payload/path-to-cloudinit-disk> | grep password: Check value of printed password. I didn't met any problems with pools. As mentioned in comment 8 VM pools might not work with cloudinit root password if they were based on broken template. Verified on 4.2.0-0.5.master.el7 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. https://access.redhat.com/errata/RHEA-2018:1488 BZ<2>Jira Resync sync2jira sync2jira sync2jira sync2jira |