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 1392390 - virt-who default interval has changed
Summary: virt-who default interval has changed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virt-who
Version: 7.3
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Patrick Creech
QA Contact: Eko
URL:
Whiteboard:
: 1403141 (view as bug list)
Depends On:
Blocks: 1420851
TreeView+ depends on / blocked
 
Reported: 2016-11-07 12:23 UTC by Martijn ten Heuvel
Modified: 2024-06-13 20:44 UTC (History)
9 users (show)

Fixed In Version: virt-who-0.19-1.el7.noarch
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 19:24:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github virt-who virt-who pull 40 0 None None None 2020-07-13 03:43:19 UTC
Red Hat Product Errata RHBA-2017:2084 0 normal SHIPPED_LIVE virt-who bug fix and enhancement update 2017-08-01 18:14:28 UTC

Description Martijn ten Heuvel 2016-11-07 12:23:41 UTC 
Description of problem:
nodes running virt-who run this every 60 minutes as per:

With the latest release (rhel7.3, virt-who 0.17.10-el7, this is back to every minute:
[root@satellite62 ~]# systemctl status virt-who.service -l
● virt-who.service - Daemon for reporting virtual guest IDs to subscription-manager
   Loaded: loaded (/usr/lib/systemd/system/virt-who.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri 2016-11-04 09:20:13 CET; 11h ago
 Main PID: 1117 (virt-who)
   CGroup: /system.slice/virt-who.service
           ├─1117 /usr/bin/python /usr/bin/virt-who
           └─2786 /usr/bin/python /usr/bin/virt-who

Nov 04 20:34:00 satellite62.mobile.mth /usr/bin/virt-who[1117]: [INFO] @executor.py:250 - Report for config "libvirt_laptop" hasn't changed, not sending
Nov 04 20:35:00 satellite62.mobile.mth /usr/bin/virt-who[1117]: [INFO] @executor.py:250 - Report for config "libvirt_laptop" hasn't changed, not sending
Nov 04 20:36:01 satellite62.mobile.mth /usr/bin/virt-who[1117]: [INFO] @executor.py:250 - Report for config "libvirt_laptop" hasn't changed, not sending
Nov 04 20:37:01 satellite62.mobile.mth /usr/bin/virt-who[1117]: [INFO] @executor.py:250 - Report for config "libvirt_laptop" hasn't changed, not sending
Nov 04 20:38:01 satellite62.mobile.mth /usr/bin/virt-who[1117]: [INFO] @executor.py:250 - Report for config "libvirt_laptop" hasn't changed, not sending
Nov 04 20:39:01 satellite62.mobile.mth /usr/bin/virt-who[1117]: [INFO] @executor.py:250 - Report for config "libvirt_laptop" hasn't changed, not sending
Nov 04 20:40:01 satellite62.mobile.mth /usr/bin/virt-who[1117]: [INFO] @executor.py:250 - Report for config "libvirt_laptop" hasn't changed, not sending
Nov 04 20:41:01 satellite62.mobile.mth /usr/bin/virt-who[1117]: [INFO] @executor.py:250 - Report for config "libvirt_laptop" hasn't changed, not sending
Nov 04 20:42:01 satellite62.mobile.mth /usr/bin/virt-who[1117]: [INFO] @executor.py:250 - Report for config "libvirt_laptop" hasn't changed, not sending
Nov 04 20:43:01 satellite62.mobile.mth /usr/bin/virt-who[1117]: [INFO] @executor.py:250 - Report for config "libvirt_laptop" hasn't changed, not sending


Version-Release number of selected component (if applicable):
[root@satellite62 ~]# yum list installed | grep virt-who
virt-who.noarch              0.17-10.el7       @rhel-7-server-rpm

Additional info:
after changing interval setting in /etc/sysconfig/virt-who, issue is resolved.
[root@satellite62 ~]# egrep -v "^#|^$" /etc/sysconfig/virt-who
VIRTWHO_DEBUG=0
VIRTWHO_INTERVAL=1800
Comment 2 Radek Novacek 2016-11-09 08:47:45 UTC 
This is expected behavior. virt-who now doesn't send unchanged reports and the default checking interval is lowered to 60 seconds. This is done to prevent long delays between creation of new virtual machine and it's availability in Customer Portal / Satellite.

The interval can be changed using VIRTWHO_INTERVAL configuration option as you figured out.

Please reopen the bug if you have a usecase that doesn't work with the new behavior.
Comment 4 Chris Snyder 2016-12-22 16:58:18 UTC 
The fix here will be to change the default interval, but not the minimum (as some might still have a need to set it lower). The default should be set to 60min.
Comment 6 yuefliu 2017-03-30 10:22:07 UTC 
verified the bug with RHEL-7.4-20170324.n.0, the default interval value is 60min (3600s).

- virt-who-0.19-1.el7.noarch
- subscription-manager-1.19.4-1.el7.x86_64
- python-rhsm-1.19.2-1.el7.x86_64
Comment 7 Chris Snyder 2017-07-11 18:44:46 UTC 
*** Bug 1403141 has been marked as a duplicate of this bug. ***
Comment 8 errata-xmlrpc 2017-08-01 19:24:47 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-2017:2084
Note You need to log in before you can comment on or make changes to this bug.