Bug 1620236

Summary: Running metrics playbook for cleanup with Ansible 2.2.3 fails about field 'args' including invalid value
Product: OpenShift Container Platform Reporter: John Sanda <jsanda>
Component: InstallerAssignee: John Sanda <jsanda>
Status: CLOSED DEFERRED QA Contact: Johnny Liu <jialiu>
Severity: high Docs Contact:
Priority: high    
Version: 3.6.1CC: aos-bugs, erjones, jialiu, jokerman, jsanda, juzhao, mmccomas, scuppett
Target Milestone: ---Keywords: Unconfirmed
Target Release: 3.9.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1550680 Environment:
Last Closed: 2018-11-20 18:31:02 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: 1550680    
Bug Blocks: 1620234    

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.