Bug 1377247 - Most options in /etc/virt-who.conf are not available
Summary: Most options in /etc/virt-who.conf are not available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-who
Version: 7.3
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Chris Snyder
QA Contact: Eko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-19 09:49 UTC by Eko
Modified: 2021-03-11 14:42 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 12:40:46 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2070 0 None None None 2019-08-06 12:40:56 UTC

Description Eko 2016-09-19 09:49:59 UTC
Description of problem:
try to configure some options in /etc/virt-who.conf, only interval and hypervisor_id options can work well, other options are invalid. 

Version-Release number of selected component (if applicable):
virt-who-0.17-10.el7.noarch
subscription-manager-1.17.15-1.el7.x86_64
python-rhsm-1.17.9-1.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. Set interval in /etc/virt-who.conf
[global]
interval=3600

2. restart virt-who and check rhsm.log [PASS]
2016-09-19 05:37:14,823 [virtwho.main DEBUG] MainProcess(27629):MainThread @executor.py:run:171 - Starting infinite loop with 3600 seconds interval

3. Set hypervisor_id in /etc/virt-who.conf
[defaults]
hypervisor_id=hostname

4. restart virt-who and check rhsm.log [PASS]
    "localhost": [
        {
            "guestId": "737638c0-c0ae-b9f9-329b-42aec64933d5", 
            "state": 1, 
            "attributes": {
                "active": 1, 
                "virtWhoType": "xen"
            }
        }
    ]
}

5. set other options in /etc/virt-who.conf
[global]
interval=3600
#reporter_id=
debug=False
oneshot=True
log_per_config=False
log_dir=/tmp
log_file=virtwho.log
configs=/root/hyperv.conf

[defaults]
owner=ACME_Corporation
env=Library
hypervisor_id=hostname

6. restart virt-who and check virtwho.log as above settings [FAILED]
debug=False   ==> invalid
oneshot=True  ==> invalid
log_per_config=False       ==> invalid
log_dir=/tmp               ==> invalid
log_file=virtwho.log       ==> invalid
configs=/root/hyperv.conf  ==> invalid

owner=ACME_Corporation  ==> invalid
env=Library             ==> invalid

Comment 2 Eko 2017-03-28 07:17:20 UTC
/etc/virt-who.conf is supported or not? 
if supported, our QE team need to design new cases for it, now most of the options are invalid.

Comment 3 Chris Snyder 2017-05-03 19:55:25 UTC
I believe the above should be working. I will look into this.

Comment 5 Chris Snyder 2017-06-07 20:25:42 UTC
As this is not a regression nor an exception, I am deferring this to 7.5

Comment 10 errata-xmlrpc 2019-08-06 12:40:46 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-2019:2070


Note You need to log in before you can comment on or make changes to this bug.