Bug 1559044

Summary:	Validator check-repo-availability.yaml generates a warning: "Consider using yum module rather than running yum"
Product:	Red Hat OpenStack	Reporter:	Beth White <beth.white>
Component:	openstack-tripleo-validations	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED EOL	QA Contact:	nlevinki <nlevinki>
Severity:	high	Docs Contact:
Priority:	medium
Version:	12.0 (Pike)	CC:	gchamoul, jjoyce, jrist, jschluet, nlevinki, slinaber, tvignaud, ukalifon
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	12.0 (Pike)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1519128	Environment:
Last Closed:	2019-01-11 16:26:38 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:	1519128
Bug Blocks:

Description Beth White 2018-03-21 15:09:35 UTC

+++ This bug was initially created as a clone of Bug #1519128 +++

Description of problem:
Validator check-repo-availability.yaml is running the 'yum' command directly, and the GUI user ends up seeing a warning instead of a successful result. When clicking on the validator to see the text of the warning, it turns out that it's just a recommendation to use the ansible yum module...


Version-Release number of selected component (if applicable):
openstack-tripleo-validations-7.4.2-1.el7ost.noarch


How reproducible:
100%


Steps to Reproduce:
1. Run the validator: "Check availability of current repositories"


Actual results:
Warning


Expected results:
Success, without warnings


Additional info:
A similar bug was filed for the validator "Check if ceph-ansible is installed on the undercloud". There is already a fix for that bug. See bug #1516397 for details.

--- Additional comment from Gaël Chamoulaud on 2017-12-07 09:22:34 EST ---

Ana is actually working on improving this validation [1] and this issue will be fixed with her patch [1]

[1] - https://review.openstack.org/#/c/515412/