Bug 1757985

Summary: Virt-who one shot with '-c', should not run if we are in the wrong directory.
Product: Red Hat Enterprise Linux 8 Reporter: Raviraj Lavande <rlavande>
Component: virt-whoAssignee: Jiri Hnidek <jhnidek>
Status: CLOSED ERRATA QA Contact: Eko <hsun>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: bcourt, bkearney, cdonnell, csnyder, jhnidek, mhulan, redakkan, wpoteat, yuefliu
Target Milestone: rcKeywords: Triaged
Target Release: 8.2Flags: pm-rhel: mirror+
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 15:37:04 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 Raviraj Lavande 2019-10-02 21:15:16 UTC 
1. Proposed title of this feature request
[RFE] Virt-who one shot with '-c', should not run if we are in the wrong directory. 

3. What is the nature and description of the request?

If we run virt-who one shot with '-c' option when we are not in the proper directory, it should not run. As it is of no use.

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
No

8. Does the customer have any specific time-line dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
No

9. Is the sales team involved in this request and do they have any additional input?
Not yet

10. List any affected packages or components.
virt-who

11. Would the customer be able to assist in testing this functionality if implemented?
yes
Comment 7 Barnaby Court 2019-10-07 18:21:47 UTC 
Virt-who should fail if a configuration file is specified but we can not open it or parse it.
Comment 13 errata-xmlrpc 2020-04-28 15:37:04 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-2020:1592