Bug 1486577
| Summary: | [downstream clone - 4.1.6] [RFE] Introduce Ansible role to set up a VM | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
| Component: | ovirt-ansible-roles | Assignee: | Ondra Machacek <omachace> |
| Status: | CLOSED ERRATA | QA Contact: | Petr Kubica <pkubica> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.1.0 | CC: | lsvaty, mperina, trichard, ylavi |
| Target Milestone: | ovirt-4.1.6 | Keywords: | FutureFeature, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-ansible-roles-1.0.3 | Doc Type: | Enhancement |
| Doc Text: |
This Ansible role can be used to automate creating a virtual machine. More information can be found at https://github.com/oVirt/ovirt-ansible/blob/ovirt-ansible-1.0/roles/ovirt-vm-infra/README.md
Please note that currently Ansible has the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=1487113
Because of this bug you should avoid calling multiple oVirt Ansible roles in a single playbook, or calling oVirt Ansible modules prior to calling oVirt Ansible roles in a single playbook (the working solution is to call the modules from the pre_tasks).
|
Story Points: | --- |
| Clone Of: | 1486249 | Environment: | |
| Last Closed: | 2017-09-19 07:15:45 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1482104, 1486249, 1489888, 1489893 | ||
| Bug Blocks: | |||
|
Description
rhev-integ
2017-08-30 08:02:56 UTC
Verified in ovirt-ansible-roles-1.0.3-1.el7ev.noarch ansible-2.3.2.0-2.el7.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-2017:2742 |