Bug 1721581

Summary: Ansible 2.8 needed for ovirt-metrics
Product: [oVirt] ovirt-engine-metrics Reporter: Charles Thao <cthao>
Component: GenericAssignee: Shirly Radco <sradco>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Novotny <pnovotny>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: bugs, emarcus, lleistne, mperina, omachace, pnovotny, rbarry, sradco
Target Milestone: ovirt-4.3.5Flags: pm-rhel: ovirt-4.4+
Target Release: 1.3.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-metrics-1.3.3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-30 14:08:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Metrics RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1723786    
Attachments:
Description Flags
log none

Description Charles Thao 2019-06-18 15:17:09 UTC
Created attachment 1581765 [details]
log

Description of problem: Unsupported parameters for (yum) module: lock_timeout Supported parameters include: allow_downgrade, autoremove, bugfix, conf_file, disable_excludes, disable_gpg_check, disable_plugin, disablerepo, download_only, enable_plugin, enablerepo, exclude, install_repoquery, installroot, list, name, releasever, security, skip_broken, state, update_cache, update_only, use_backend, validate_certs

Version-Release number of selected component (if applicable): 4.4


How reproducible: 100%


Steps to Reproduce:
1. Deploy a master engine
2. Attach a stable 4.3 ovirt-node host

Comment 1 Charles Thao 2019-06-18 15:18:20 UTC
Problem: Current ansible is >= 2.7.3

Resolution: Install ansible 2.8.1 on both host and engine

Comment 2 Sandro Bonazzola 2019-06-19 06:17:50 UTC
Martin was it planned to bump requirement on ansible to >= 2.8.1? Or is it a regression in our ansible code?

Comment 3 Martin Perina 2019-06-19 11:24:20 UTC
(In reply to Sandro Bonazzola from comment #2)
> Martin was it planned to bump requirement on ansible to >= 2.8.1? Or is it a
> regression in our ansible code?

No, we still require only ansible >= 2.7.2, although we expect that everyone has their systems up-to-date, so they should use ansible 2.8 already.

The problematic code has been added as a part of BZ1713223, Shirly could you please take a look?

Comment 4 Charles Thao 2019-06-24 12:55:44 UTC
Ansible 2.8.1 isn't available in yum or dnf (tested on fc28 and centos8). I had to download it directly from Ansible's github page and install manually to get ovirt-engine to work.

Comment 5 Martin Perina 2019-06-26 09:26:56 UTC
(In reply to Charles Thao from comment #4)
> Ansible 2.8.1 isn't available in yum or dnf (tested on fc28 and centos8). I
> had to download it directly from Ansible's github page and install manually
> to get ovirt-engine to work.

Fedora 28 is end of life from May 28th and CentOS 8 is not supposted oVirt distribution (it's not yet even released). So CentOS 7 is the only supported platform for oVirt 4.3 and here we have Ansible 2.8 available as a part of EPEL:

https://dl.fedoraproject.org/pub/epel/7/x86_64/Packages/a/ansible-2.8.1-1.el7.noarch.rpm

Comment 6 Charles Thao 2019-06-26 20:35:03 UTC
Sorry I meant Centos 7. I couldn't find ansible 2.8.1 when I first spun up the Centos VM. Again, it's not automatically installed. The requirements should have said >=2.8.0 instead of 2.7.3 and assuming the users have the latest versions of Ansible.

Comment 7 Sandro Bonazzola 2019-06-27 08:17:30 UTC
ansible 2.8.1 has been shipped in EPEL 5 days ago https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-8b0a066052
we are consuming it in oVirt.

Comment 8 Pavel Novotny 2019-07-16 16:10:36 UTC
Verified in
ovirt-engine-4.3.5.4-0.1.el7.noarch
ovirt-engine-metrics-1.3.3.2-1.el7ev.noarch

ansible >= 2.8.1 is now needed by ovirt-engine-metrics:


# rpm -qR ovirt-engine-metrics | grep ansible
ansible >= 2.8.1
ovirt-ansible-image-template >= 1.1.11
ovirt-ansible-vm-infra >= 1.1.19

Comment 9 Sandro Bonazzola 2019-07-30 14:08:21 UTC
This bugzilla is included in oVirt 4.3.5 release, published on July 30th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.5 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.