Bug 1620236 - Running metrics playbook for cleanup with Ansible 2.2.3 fails about field 'args' including invalid value
Summary: Running metrics playbook for cleanup with Ansible 2.2.3 fails about field 'ar...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.6.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.9.z
Assignee: John Sanda
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On: 1550680
Blocks: 1620234
TreeView+ depends on / blocked
 
Reported: 2018-08-22 18:51 UTC by John Sanda
Modified: 2018-11-20 18:31 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1550680
Environment:
Last Closed: 2018-11-20 18:31:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 1 Stephen Cuppett 2018-08-23 16:45:13 UTC 
https://github.com/openshift/openshift-ansible/pull/9721
Comment 2 Junqi Zhao 2018-09-12 01:00:16 UTC 
This need not be fixed in 3.9, since 3.9 openshift-ansible Requires: ansible >= 2.4.3, it does not work with ansible = 2.2.3.0-1.el7 now, see error:


Error: Package: openshift-ansible-3.9.43-1.git.0.d0bc600.el7.noarch (Installer-311)
           Requires: ansible >= 2.4.3
           Installed: ansible-2.2.3.0-1.el7.noarch (@Installer-39)
               ansible = 2.2.3.0-1.el7
**********************************************************************
yum can be configured to try to resolve such errors by temporarily enabling
disabled repos and searching for missing dependencies.
To enable this functionality please set 'notify_only=0' in /etc/yum/pluginconf.d/search-disabled-repos.conf
**********************************************************************

Error: Package: openshift-ansible-3.9.43-1.git.0.d0bc600.el7.noarch (Installer-311)
           Requires: ansible >= 2.4.3
           Installed: ansible-2.2.3.0-1.el7.noarch (@Installer-39)
               ansible = 2.2.3.0-1.el7
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
Comment 3 Stephen Cuppett 2018-11-20 18:31:02 UTC 
There appear to be no active cases related to this bug. As such we're closing this bug in order to focus on bugs that are still tied to active customer cases. Please re-open this bug if you feel it was closed in error or a new active case is attached.
Note You need to log in before you can comment on or make changes to this bug.