Bug 1773313

Summary: RHV Metric store installation fails with error: "You need to install \"jmespath\" prior to running json_query filter"
Product: Red Hat Enterprise Virtualization Manager Reporter: Gajanan <gchakkar>
Component: ovirt-engine-metricsAssignee: Shirly Radco <sradco>
Status: CLOSED ERRATA QA Contact: Guilherme Santos <gdeolive>
Severity: high Docs Contact:
Priority: high    
Version: 4.3.0CC: mkalinin, mperina, mtessun, pelauter, sbonazzo
Target Milestone: ovirt-4.4.0   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-04 13:21:16 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: 1779587    

Description Gajanan 2019-11-17 14:50:37 UTC
Description of problem:

RHV Metric store installation fails with error: "You need to install \"jmespath\" prior to running json_query filter"

Environment:

ovirt-engine-4.3.6.7-0.1.el7.noarch
ansible-2.9.0-2.el7.noarch
Ovirt-engine-metrics-1.3.4.1-1.el7ev.noarch

Issue:

Installing Metric Store installation fails at "TASK: [oVirt.vm-infra : Apply tags from VM profiles] " with below message: 

~~~
TASK [oVirt.vm-infra : Apply tags from VM profiles] ***************************************************************************************************************************************************************
task path: /usr/share/ansible/roles/ovirt.vm-infra/tasks/vm_state_present.yml:111
fatal: [localhost]: FAILED! => {
    "msg": "You need to install \"jmespath\" prior to running json_query filter"
}
~~~

Its at step: 2.1. Create the Metrics Store virtual machines
~~~
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html-single/metrics_store_installation_guide/index#Creating_the_metrics_store_virtual_machines
~~~

Fix : 

Installing the "python2-jmespath" package on rhvm and then running above fixed the issue.

Comment 1 Shirly Radco 2019-11-18 09:14:34 UTC
Hi,

Can I add to require python2-jmespath to the oVirt metrics spec file?
I believe Ansible removed this from their dependencies.

Comment 2 Martin Perina 2019-11-18 09:47:43 UTC
(In reply to Shirly Radco from comment #1)
> Hi,
> 
> Can I add to require python2-jmespath to the oVirt metrics spec file?
> I believe Ansible removed this from their dependencies.

Yes, you need to do it to ensure compatibility with Ansible 2.9

Comment 3 Sandro Bonazzola 2019-11-20 07:27:06 UTC
I would consider backporting this bug to 4.3.7/4.3.8 since ansible 2.9 is now included for 4.3 users too

Comment 4 Shirly Radco 2019-11-24 15:15:15 UTC
I will backport this to 4.3.8, since if the users have Ansible 2.8 they will need this package.
Do we want to also bump 4.3.8 to Ansible 2.9?

Comment 5 Sandro Bonazzola 2019-12-11 13:57:15 UTC
(In reply to Shirly Radco from comment #4)
> I will backport this to 4.3.8, since if the users have Ansible 2.8 they will
> need this package.
> Do we want to also bump 4.3.8 to Ansible 2.9?

I don't think we need to require it but Ansible 2.9 will be available as well on 4.3.8.

Comment 6 Guilherme Santos 2020-02-11 15:57:41 UTC
Verified on:
ovirt-engine-metrics-1.3.6-1.el7ev
ovirt-engine-setup-4.4.0-0.14.master.el7
ansible-2.9.4-1.el7ae

Steps:
1. # yum install ovirt-engine-metrics

Results:
python2-jmespath shown as dependency to be isntalled

Comment 7 Guilherme Santos 2020-02-11 15:59:19 UTC
Obs.
Only ansible-2.9.4-1.el7ae was installed.
ovirt-engine-metrics-1.3.6-1.el7ev and ovirt-engine-setup-4.4.0-0.14.master.el7 weren't installed, but the repo available point to them in these specific versions

Comment 10 errata-xmlrpc 2020-08-04 13:21:16 UTC
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 (Important: RHV Manager (ovirt-engine) 4.4 security, bug fix, and enhancement update), 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/RHSA-2020:3247