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:
To properly monitor that virt-who regularly scans hypervisors and send results to Satellite 6 (or any other backend) it would be useful if virt-who sent report also when there's no change on hypervisor. Sending kind of empty arrays would probably make Candlepin think that no VM is present on hypervisor but I think the API could be enhanced so virt-who would indicate that this report is kind of "heartbeat". Or it could use entirely different API endpoint.
This way we could in Satellite 6 monitor the desired interval and last report time and notify user if we stopped receiving updates from virt-who.
Version-Release number of selected component (if applicable):
all
How reproducible:
100%
Steps to Reproduce:
1. run virt-who
2. wait until next run while you don't make any changes on hypervisor
3. see "Report for config "virt-who-config-2" hasn't changed, not sending" in the log
Actual results:
No report is sent
Expected results:
Some heartbeat would be sent instead to configured remote server.
Additional info:
This would be extra useful in Satellite 6 "foreman_virt_who_configure" plugin. This way we could distinguish whether the report didn't come because of no change or because of some issue with the virt-who worker or connectivity between it and Satellite 6. Note that this heartbeat should not be sent in case there's any issue with the hypervisor communication.
The entry in the /etc/virt-who.conf file will be defined as a default variable.
It can also be applied to individual conf files andthe setting can be different for each.
The name is 'rhsn_no_proxy' as the proxy is used in the subscription manager communication with the entitlement server and cdn.
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-2020:0990