Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1591525

Summary: Customer would like to enable/disable warning on the RHSM log file
Product: Red Hat Enterprise Linux 7 Reporter: Waldirio M Pinheiro <wpinheir>
Component: virt-whoAssignee: William Poteat <wpoteat>
Status: CLOSED ERRATA QA Contact: Eko <hsun>
Severity: unspecified Docs Contact:
Priority: low    
Version: 7.5CC: khowell, rjerrido, wpoteat, yuefliu
Target Milestone: rcKeywords: FutureFeature, Reopened, Triaged
Target Release: ---   
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: 2019-08-06 12:40:51 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 Waldirio M Pinheiro 2018-06-15 00:17:36 UTC
Description of problem:
Actually virt-who generate some warnings which is not possible to disable via conf file */etc/virt-who.conf*

Version-Release number of selected component (if applicable):
0.21.7-1.el7_5
0.21.5-1.el7

How reproducible:
100%

Steps to Reproduce:
1. Install virt-who
2. Configure the file to connect on the vCenter for example
3. Execute the command virt-who -o

Actual results:
---
[root@wallsat63 virt-who.d]# virt-who -o
2018-06-14 19:35:00,113 [virtwho.rhsm_log DEBUG] MainProcess(4484):MainThread @config.py:all_drop_dir_config_sections:1245 - There are files in '/etc/virt-who.d/' not ending in '*.conf' is this intentional?
2018-06-14 19:35:00,214 [virtwho.rhsm_log WARNING] MainProcess(4484):MainThread @config.py:init_config:1395 - [vcenterhost]: Value for "simplified_vim" not set, using default: True
2018-06-14 19:35:00,214 [virtwho.rhsm_log WARNING] MainProcess(4484):MainThread @config.py:init_config:1395 - [vcenterhost]: Value for "is_hypervisor" not set, using default: True
2018-06-14 19:35:00,214 [virtwho.rhsm_log WARNING] MainProcess(4484):MainThread @config.py:init_config:1395 - [global]: Value for "interval" not set, using default: 3600
2018-06-14 19:35:00,214 [virtwho.rhsm_log WARNING] MainProcess(4484):MainThread @config.py:init_config:1395 - [global]: Value for "log_per_config" not set, using default: False
2018-06-14 19:35:00,214 [virtwho.rhsm_log WARNING] MainProcess(4484):MainThread @config.py:init_config:1395 - [global]: Value for "print_" not set, using default: False
2018-06-14 19:35:00,215 [virtwho.rhsm_log WARNING] MainProcess(4484):MainThread @config.py:init_config:1395 - [global]: Value for "reporter_id" not set, using default: wallsat63.usersys.redhat.com-b8c9ed997efd49c9882b5416130bc41e
2018-06-14 19:35:00,215 [virtwho.rhsm_log WARNING] MainProcess(4484):MainThread @config.py:init_config:1395 - [global]: Value for "log_dir" not set, using default: /var/log/rhsm
2018-06-14 19:35:00,215 [virtwho.rhsm_log WARNING] MainProcess(4484):MainThread @config.py:init_config:1395 - [global]: Value for "background" not set, using default: False
2018-06-14 19:35:00,215 [virtwho.rhsm_log WARNING] MainProcess(4484):MainThread @config.py:init_config:1395 - [global]: Value for "debug" not set, using default: False
2018-06-14 19:35:00,215 [virtwho.rhsm_log WARNING] MainProcess(4484):MainThread @config.py:init_config:1395 - [global]: Value for "configs" not set, using default: []
2018-06-14 19:35:00,215 [virtwho.rhsm_log WARNING] MainProcess(4484):MainThread @config.py:init_config:1395 - [global]: Value for "log_file" not set, using default: rhsm.log
2018-06-14 19:35:00,216 [virtwho.rhsm_log DEBUG] MainProcess(4484):MainThread @executor.py:__init__:52 - Using config named 'vcenterhost'
2018-06-14 19:35:00,216 [virtwho.rhsm_log INFO] MainProcess(4484):MainThread @main.py:main:158 - Using configuration "vcenterhost" ("esx" mode)
2018-06-14 19:35:00,216 [virtwho.rhsm_log INFO] MainProcess(4484):MainThread @main.py:main:160 - Using reporter_id='wallsat63.usersys.redhat.com-b8c9ed997efd49c9882b5416130bc41e'
2018-06-14 19:35:01,125 [virtwho.main INFO] MainProcess(4484):Thread-2 @virt.py:_send_data:924 - Report for config "vcenterhost" gathered, placing in datastore
2018-06-14 19:35:01,300 [virtwho.destination_-1383904886509854253 INFO] MainProcess(4484):Thread-3 @virt.py:_send_data:589 - Hosts-to-guests mapping for config "vcenterhost": 5 hypervisors and 112 guests found
2018-06-14 19:35:01,301 [virtwho.destination_-1383904886509854253 INFO] MainProcess(4484):Thread-3 @virt.py:_send_data:622 - Sending updated Host-to-guest mapping to "ACME" including 5 hypervisors and 112 guests
2018-06-14 19:35:58,119 [virtwho.destination_-1383904886509854253 INFO] MainProcess(4484):Thread-3 @subscriptionmanager.py:check_report_state:356 - Mapping for config "destination_-1383904886509854253" updated
---

Expected results:
---
[root@wallsat63 ~]# virt-who -o
2018-06-14 20:01:38,700 [virtwho.config ERROR] MainProcess(8565):MainThread @config.py:parse_file:381 - Configuration file /etc/virt-who.conf contains no section headers
2018-06-14 20:01:38,716 [virtwho.rhsm_log DEBUG] MainProcess(8565):MainThread @config.py:all_drop_dir_config_sections:1246 - There are files in '/etc/virt-who.d/' not ending in '*.conf' is this intentional?
2018-06-14 20:01:38,798 [virtwho.rhsm_log DEBUG] MainProcess(8565):MainThread @executor.py:__init__:52 - Using config named 'vcenterhost'
2018-06-14 20:01:38,798 [virtwho.rhsm_log INFO] MainProcess(8565):MainThread @main.py:main:158 - Using configuration "vcenterhost" ("esx" mode)
2018-06-14 20:01:38,798 [virtwho.rhsm_log INFO] MainProcess(8565):MainThread @main.py:main:160 - Using reporter_id='wallsat63.usersys.redhat.com-b8c9ed997efd49c9882b5416130bc41e'
2018-06-14 20:01:41,424 [virtwho.main INFO] MainProcess(8565):Thread-2 @virt.py:_send_data:922 - Report for config "vcenterhost" gathered, placing in datastore
2018-06-14 20:01:42,447 [virtwho.destination_-1383904886509854253 INFO] MainProcess(8565):Thread-3 @virt.py:_send_data:589 - Hosts-to-guests mapping for config "vcenterhost": 5 hypervisors and 112 guests found
2018-06-14 20:01:42,447 [virtwho.destination_-1383904886509854253 INFO] MainProcess(8565):Thread-3 @virt.py:_send_data:620 - Sending updated Host-to-guest mapping to "ACME" including 5 hypervisors and 112 guests
2018-06-14 20:02:14,902 [virtwho.destination_-1383904886509854253 INFO] MainProcess(8565):Thread-3 @subscriptionmanager.py:check_report_state:356 - Mapping for config "destination_-1383904886509854253" updated
---

Additional info:

Comment 5 William Poteat 2019-01-09 19:01:02 UTC
It is a low priority and is not worthy of a z-stream build to fix.
We will keep it in mind for improvement going forward.

Comment 6 William Poteat 2019-05-29 12:48:40 UTC
This has been corrected in virt-who-0.24.6-1.el7

https://bugzilla.redhat.com/show_bug.cgi?id=1522384

Comment 9 William Poteat 2019-06-12 18:00:40 UTC
It belongs in the the conf file for the esx managers. It is listed in the virt-who-conf man page as follows:

BACKEND SPECIFIC OPTIONS
   ESX BACKEND
       filter_host_parents
              Only  hosts  which  cluster  ID is specified in comma-separated list in this option will be reported. Put the name into the double-quotes if it contains
              special characters (like comma). PowerCLI command to find the domain names in VMware `Get-Cluster “ClusterName” | Select ID`

       exclude_host_parents
              Exclude hosts which cluster ID is specified in comma-separated list in this option will NOT be reported. Put the name into the double-quotes if it  con‐
              tains special characters (like comma). PowerCLI command to find the domain names in VMware `Get-Cluster “ClusterName” | Select ID`

       simplified_vim
              virt-who by default uses stripped-down version of vimService.wsdl file that contains vSphere SOAP API definition. Set this option to false to use server
              provided wsdl file that will be retrieved automatically.



Is that sufficient?

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