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.
Description of problem:
(I follow bugzilla template for this RFE since it is partially a bug as well)
Since some recent change in virt-who (rebase to 0.17?), it does check-in triggered by any action performed on the virt back-end (this can happen with max. frequency of 1 minute). While this change makes actions from back-end propagated to RHSM much faster, it makes VIRTWHO_INTERVAL parameter almost ridiculous on deployments with frequent changes. Such frequent reporting might not be necessary / welcomed in all cases, since it causes redundantly higher load or makes bad user experience:
E.g. in Satellite6, each such report generates a task. Adding or removing a VM every minute or two, Satellite gets an auxiliary&uninteresting (from user point of view) task every minute or two. Therefore, task list is full of such dummy tasks and one has to use filters from beginning to see more important tasks there.
My proposal is to add an option (disabled by default) that prevents triggering of sending the report on every action on the virt back-end.
Version-Release number of selected component (if applicable):
virt-who 0.17-10
How reproducible:
100%
Steps to Reproduce:
1. Configure virt-who with any back-end with any VIRTWHO_INTERVAL
2. Create a VM or delete a VM frequently
3. Monitor frequency of reports sent to RHSM.
4. Have a configuration ability to see jsut reports every VIRTWHO_INTERVAL seconds but not more often.
Actual results:
3. (almost) Every action in 2 trigers a report
4. no such config option
Expected results:
4. there is such config option
Additional info:
See https://bugzilla.redhat.com/show_bug.cgi?id=1369082#c9 .
Hi,
I think you can try the VIRTWHO_DEBUG option,
if VIRTWHO_DEBUG=1, it will report the hypervisors/guest json info
if VIRTWHO_DEBUG=1, no json info get out
There seems to be a user story where the extra virt-who reporting activities reporting to candlepin in Sat6 flooded katello_event_queue in qpidd - katello was not fast enough to consume the messages, causing candlepin performance issues.
Behavior has changed as of virt-who-0.19-3, virt-who now respects the interval specified regardless of the source of information. There is no option to toggle this behavior. If you feel strongly that there should be, please reopen this RFE.