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.
We should log a message to let the user know that the interval is an invalid value. Current behavior of just logging used interval doesn't tell user *why*. The message should include what they specified, minimum, and the effective interval.
according to our test result:
setting interval time by /etc/sysconfig/virt-who:
#VIRTWHO_INTERVAL=0, the time is 3600s
VIRTWHO_INTERVAL=0 , the time is 60s
VIRTWHO_INTERVAL=10, the time is 60s
VIRTWHO_INTERVAL=60, the time is 60s
VIRTWHO_INTERVAL=61, the time is 61s
setting interval time by command lien:
without -i option, the time is 3600s
with -i 0 option, the time is 3600s
with -i 10 option, the time is 60s,
with -i 60 option, the time is 60s,
with -i 61 option, the time is 61s,
The test result shows:
the default time(no setting or setting to 0), should be 3600s,
if the setting value <=60, the time is 60s,
if the setting value >60, the time is the value.
so please change the default time for VIRTWHO_INTERVAL=0
I consider this as already fixed in current master branch of virt-who. I'm attaching link to PR request. I'm also attaching fragment of rhsm.conf to prove that default interval (3600s) is used in this case:
2018-01-09 14:36:56,986 [virtwho.rhsm_log WARNING] MainProcess(19292):MainThread @config.py:init_config:1395 - [global]: Value for "background" not set, using default: False
2018-01-09 14:36:56,986 [virtwho.rhsm_log WARNING] MainProcess(19292):MainThread @config.py:init_config:1395 - [global]: Value for "log_file" not set, using default: rhsm.log
2018-01-09 14:36:56,986 [virtwho.rhsm_log WARNING] MainProcess(19292):MainThread @config.py:init_config:1395 - [global]: Interval value can't be lower than 3600 seconds. Default value of 3600 seconds will be used.
2018-01-09 14:36:56,987 [virtwho.rhsm_log DEBUG] MainProcess(19292):MainThread @executor.py:__init__:52 - Using config named 'local_libvirt'
2018-01-09 14:36:56,987 [virtwho.rhsm_log INFO] MainProcess(19292):MainThread @main.py:main:158 - Using configuration "local_libvirt" ("libvirt" mode)
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-2018:3169
Description of problem: When config VIRTWHO_INTERVAL=0 in /etc/sysconfig/virt-who, virt-who's refresh interval is 60s. Version-Release number of selected component (if applicable): virt-who-0.19-2.el7sat.noarch How reproducible: Always Steps to Reproduce: 1. Register RHEL to satellite 6.2.9-sp1 2. Configure virt-who hasn't enabled VIRTWHO_INTERVAL as the following: [root@ibm-hs21-04 ~]# cat /etc/sysconfig/virt-who | grep -v ^# | grep -v ^$ VIRTWHO_DEBUG=1 VIRTWHO_INTERVAL=0 VIRTWHO_HYPERV=1 VIRTWHO_HYPERV_OWNER=Default_Organization VIRTWHO_HYPERV_ENV=Default_Organization VIRTWHO_HYPERV_SERVER=10.73.131.226 VIRTWHO_HYPERV_USERNAME=administrator VIRTWHO_HYPERV_PASSWORD=Welcome1 3. Restart virt-who and check virt-who's log Actual results: 2017-03-23 22:57:50,986 [virtwho.init INFO] MainProcess(30822):MainThread @main.py:main:165 - Using configuration "env/cmdline" ("hyperv" mode) 2017-03-23 22:57:50,986 [virtwho.init INFO] MainProcess(30822):MainThread @main.py:main:167 - Using reporter_id='ibm-hs21-04.lab.bos.redhat.com-dc4556b514744d9e99292896d3e52755' 2017-03-23 22:57:50,989 [virtwho.main DEBUG] MainProcess(30822):MainThread @executor.py:run:176 - Starting infinite loop with 60 seconds interval 2017-03-23 22:57:51,046 [virtwho.env_cmdline DEBUG] ====>Default interval is 60s Expected results: Since VIRTWHO_INTERVAL=0, virt-who should run in default interval 3600s Additional info: