Bug 1654887

Summary:	[3.9] Remove unnecessary passlib check
Product:	OpenShift Container Platform	Reporter:	Candace Sheremeta <cshereme>
Component:	Installer	Assignee:	Scott Dodson <sdodson>
Installer sub component:	openshift-ansible	QA Contact:	Junqi Zhao <juzhao>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	aos-bugs, gpei
Version:	3.9.0
Target Milestone:	---
Target Release:	3.9.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Previously the metrics playbooks attempted to verify availability of the python-passlib library in a manner that was unpredictable. This library is also a dependency of the openshift-ansible packaging so there's no need for this additional check and it has been removed.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-12-13 19:27:16 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:

Description Candace Sheremeta 2018-11-29 23:15:24 UTC

Description of problem:
Please backport https://github.com/openshift/openshift-ansible/pull/9209 to 3.9

This backport was attempted here: https://github.com/openshift/openshift-ansible/pull/9209#issuecomment-412509547 but the merge failed, and I do not see any follow-up on this.

Comment 1 Scott Dodson 2018-11-30 16:09:09 UTC

https://github.com/openshift/openshift-ansible/pull/10800

Comment 3 Junqi Zhao 2018-12-03 02:37:32 UTC

python-passlib check is removed from roles/openshift_metrics/tasks/main.yaml and metrics works well

# rpm -qa | grep ansible
openshift-ansible-docs-3.9.57-1.git.0.9ece605.el7.noarch
ansible-2.4.6.0-1.el7ae.noarch
openshift-ansible-playbooks-3.9.57-1.git.0.9ece605.el7.noarch
openshift-ansible-3.9.57-1.git.0.9ece605.el7.noarch
openshift-ansible-roles-3.9.57-1.git.0.9ece605.el7.noarch

Comment 6 errata-xmlrpc 2018-12-13 19:27:16 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/RHBA-2018:3748