Bug 1493581 - Upgrade ansible to version 2.4.1.0
Summary: Upgrade ansible to version 2.4.1.0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ansible
Version: 4.1.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.1.8
: ---
Assignee: Sandro Bonazzola
QA Contact: Pavol Brilla
URL:
Whiteboard:
Depends On: 1494113 1494117
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-20 14:25 UTC by Sandro Bonazzola
Modified: 2017-12-12 09:20 UTC (History)
3 users (show)

Fixed In Version: ansible-2.4.1.0-1.el7
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Rebased package(s) to version: 2.4.1.0.
Clone Of:
Environment:
Last Closed: 2017-12-12 09:20:49 UTC
oVirt Team: Integration
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:3408 0 normal SHIPPED_LIVE ansible bug fix and enhancement update 2017-12-12 14:13:47 UTC

Description Sandro Bonazzola 2017-09-20 14:25:21 UTC 
Rebase on upstream 2.4.0.0
Comment 1 Sandro Bonazzola 2017-10-13 08:57:51 UTC 
Need to rebase to ansible-2.4.0.0-5.el7
Comment 2 Sandro Bonazzola 2017-11-15 12:31:32 UTC 
Rebased on ansible-2.4.1.0-1.el7
Comment 5 Emma Heftman 2017-11-29 12:48:07 UTC 
Hi Sandro. Should the release notes text really say 2.4.0.0 or should it be 2.4.1.0?
thanks
Comment 6 Sandro Bonazzola 2017-11-30 08:12:09 UTC 
(In reply to Emma Heftman from comment #5)
> Hi Sandro. Should the release notes text really say 2.4.0.0 or should it be
> 2.4.1.0?
> thanks

Sorry, updated.
Comment 9 errata-xmlrpc 2017-12-12 09:20:49 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-2017:3408
Note You need to log in before you can comment on or make changes to this bug.