Bug 1436617

Summary:	[RFE] Virt-who can check configuration for validity
Product:	Red Hat Enterprise Linux 7	Reporter:	Eko <hsun>
Component:	virt-who	Assignee:	Chris Snyder <csnyder>
Status:	CLOSED ERRATA	QA Contact:	Eko <hsun>
Severity:	low	Docs Contact:	Yehuda Zimmerman <yzimmerm>
Priority:	high
Version:	7.4	CC:	csnyder, hsun, jherrman, khowell, sgao, tbowling, yuefliu
Target Milestone:	rc	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	virt-who now provides configuration error information The virt-who utility now checks for common virt-who configuration errors and outputs log messages that specify the configuration items that caused these errors. As a result, it is easier for a user to correct virt-who configuration errors.	Story Points:	---
Clone Of:
Clones:	1500914 (view as bug list)		Environment:
Last Closed:	2018-04-10 16:19:53 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:
Bug Blocks:	1469152, 1500914

Comment 2 Kevin Howell 2017-03-30 15:02:46 UTC

Eko, can you please attach the config files used?
Please tell us which values in the config you believe should cause an error?
What error message/feedback do you expect?

Comment 4 Kevin Howell 2017-04-03 19:26:10 UTC

We are thinking that we would like to handle this as an RFE which does something like this: a virt-who subcommand that validates the config, reports any problems (including ignored keys), and validates connections with candlepin and virtualization backends.

Comment 5 Chris Snyder 2017-09-25 14:13:41 UTC

*** Bug 1490244 has been marked as a duplicate of this bug. ***

Comment 8 yuefliu 2017-11-02 10:53:17 UTC

The bug still exists with virt-who-0.21.0-1.el7.noarch.

Comment 14 errata-xmlrpc 2018-04-10 16:19:53 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-2018:0895