Bug 1547381 - [gdeploy] Upgrading ansible 2.3 to version ansible-2.4.2.0-2 is failing with python2-jmespath dependency
Summary: [gdeploy] Upgrading ansible 2.3 to version ansible-2.4.2.0-2 is failing with ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gdeploy
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: RHGS 3.3.1 Async
Assignee: Ramakrishna Reddy Yekulla
QA Contact: Manisha Saini
URL:
Whiteboard:
Depends On:
Blocks: 1581561
TreeView+ depends on / blocked
 
Reported: 2018-02-21 08:43 UTC by Manisha Saini
Modified: 2018-06-21 03:34 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-21 03:33:15 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:1958 0 None None None 2018-06-21 03:34:48 UTC

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
Note You need to log in before you can comment on or make changes to this bug.