Red Hat Bugzilla – Bug 1491010
[ovirt-ansible-roles] ovirt-vm-infra: When VM already exists in environment, role should left that VM in the same running state
Last modified: 2018-05-15 14:01:05 EDT
Description of problem: When VM already exists in environment, role should left that VM in the same running state (so for example, in stopped state) User can have some VMs down for a good reason (VM was created before by this role and variables are still present in playbook), role should only add VMs from templates and configure them or update these existing VMs. If user will want run them or change their running state, he will use 'state' variable. example of some good reason: - VM as backup old databases, - VM using same IP as another VM or same MAC - Security reason ... Version-Release number of selected component (if applicable): ovirt-ansible-roles-1.0.3-1.el7ev.noarch ansible-2.3.2.0-2.el7.noarch
This has been tracked upstream in https://github.com/ansible/ansible/issues/27382, and will be in Ansible 2.4. Please re-verify with Ansible 2.4, once released.
The default state of the VM is running for ovirt-vm-infra role. If user don't want to touch the VM state just make sure it's present', he should change state to present. If he want to make sure the VMs are stopped, he should change state to stopped.
I think that default state for ovirt-vm-infra should be present, not running
I can be. Let's change it, so we'll be consistent with the recent change in ovirt_vms module. Either move this bug back to ASSIGNED or create new one, thanks.
Verified in ansible-2.5.0-0.3.rc1.el7ae.noarch ovirt-ansible-vm-infra-1.1.5-1.el7ev.noarch
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:1534