Bug 1666290
| Summary: | Ansible 2.7.2 required for ovirt.disaster-recovery, ovirt.cluster-upgrade, ovirt.hosted-engine-setup and ovirt.shutdown-env roles | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Martin Perina <mperina> |
| Component: | ovirt-ansible-roles | Assignee: | Ondra Machacek <omachace> |
| Status: | CLOSED ERRATA | QA Contact: | Petr Kubica <pkubica> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.2.7 | CC: | apinnick, mgoldboi, mperina, stirabos |
| Target Milestone: | ovirt-4.2.8-1 | Keywords: | Rebase, ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-02-13 15:33:25 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
Martin Perina
2019-01-15 12:51:45 UTC
FAILED: # rpm -qR ovirt-ansible-hosted-engine-setup ansible >= 2.7 .. # rpm -qR ovirt-ansible-shutdown-env ansible >= 2.7 .. PASSED: # rpm -qR ovirt-ansible-cluster-upgrade ansible >= 2.7.2 .. # rpm -qR ovirt-ansible-disaster-recovery ansible >= 2.7.2 .. rpms: ovirt-ansible-disaster-recovery-1.1.4-1.el7ev.noarch ovirt-ansible-shutdown-env-1.0.2-2.el7ev.noarch ovirt-ansible-hosted-engine-setup-1.0.7-2.el7ev.noarch ovirt-ansible-cluster-upgrade-1.1.10-1.el7ev.noarch From QE point of view, there should be requirement on Ansible 2.7.2 in every role as mentioned in description. If Ansible 2.7 is enough for hosted-engine-setup and shutdown-env, please move it to verified. Thanks, Petr AFAIK for hosted-engine and shutdown roles use case - 2.7 is enough. We require it by other roles because of other features which that z-stream has. @Simone please correct me if I am wrong, thanks. 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-2019:0339 |