Bug 1491010
Summary: | [ovirt-ansible-roles] ovirt-vm-infra: When VM already exists in environment, role should left that VM in the same running state | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Petr Kubica <pkubica> |
Component: | ovirt-ansible-roles | Assignee: | Ondra Machacek <omachace> |
Status: | CLOSED ERRATA | QA Contact: | Petr Kubica <pkubica> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.6 | CC: | mperina, omachace, pstehlik |
Target Milestone: | ovirt-4.2.2 | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ovirt-ansible-vm-infra-1.1.5 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-15 18:00:33 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Petr Kubica
2017-09-12 18:32:17 UTC
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 BZ<2>Jira Resync |