Bug 1547381

Summary:	[gdeploy] Upgrading ansible 2.3 to version ansible-2.4.2.0-2 is failing with python2-jmespath dependency
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Manisha Saini <msaini>
Component:	gdeploy	Assignee:	Ramakrishna Reddy Yekulla <rreddy>
Status:	CLOSED ERRATA	QA Contact:	Manisha Saini <msaini>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	rhgs-3.3	CC:	amukherj, rcyriac, rhinduja, rhs-bugs, rreddy, sankarshan, smohan, storage-qa-internal
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.3.1 Async
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:	2018-06-21 03:33:15 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1581561

Description Manisha Saini 2018-02-21 08:43:22 UTC

Description of problem:
Upgrading ansible 2.3 to version ansible-2.4.2.0-2 is failing with python2-jmespath dependency 

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

# rpm -qa | grep gdeploy
gdeploy-2.0.2-22.el7rhgs.noarch

# rpm -qa | grep ansible
ansible-2.3.2.0-1.el7.noarch


How reproducible:
Consistent

Steps to Reproduce:
1.Upgrade ansible version from ansible-2.3.2.0-1.el7.noarch to ansible-2.4.2.0-2.el7


Actual results:
Upgrade fails because of python2-jmespath package dependency

Expected results:
Upgrade should pass

Additional info:

Comment 5 Ramakrishna Reddy Yekulla 2018-03-15 12:23:49 UTC

python2-jmespath dependency is now added to the builds page in Errata. Could you try installing it with the attached builds.

Comment 8 errata-xmlrpc 2018-06-21 03:33:15 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, 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-2018:1958