Bug 1462811
Summary: | [RFE] Execute Ansible role ovirt-host-deploy as a part of host installation/reinstallation to allow customization of this flow | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Martin Perina <mperina> |
Component: | BLL.Infra | Assignee: | Ondra Machacek <omachace> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Pavol Brilla <pbrilla> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4.1.3.3 | CC: | bgraveno, bugs, lsvaty, mgoldboi, oourfali, pbrilla, sbonazzo |
Target Milestone: | ovirt-4.2.0 | Keywords: | FutureFeature, Reopened |
Target Release: | 4.2.0 | Flags: | rule-engine:
ovirt-4.2+
pbrilla: testing_plan_complete- mgoldboi: planning_ack+ mperina: devel_ack+ pbrilla: testing_ack+ |
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
The Ansible role ovirt-host-deploy[1] is now executed as part of the host installation/reinstallation flow. This role is included in ovirt-ansible-roles package and is installed on the Red Hat Virtualization Manager by default.
[1] /usr/share/doc/ansible/rols/ovirt-host-deploy/README.md
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-20 11:45:59 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: | |||
Bug Depends On: | 1462821 | ||
Bug Blocks: | 995362 |
Description
Martin Perina
2017-06-19 15:24:32 UTC
Testing has indicated this request is declined. You may appeal this decision by reopening this request. Ansible host-deploy playbook execution has successfully finished on host slot6c. ovirt-engine.noarch 4.2.0-0.5.master.el7 @rhv-4.2.0-latest This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |