Bug 1447633

Summary: Virt-who should send reports even when there's no update on hypervisor
Product: Red Hat Enterprise Linux 7 Reporter: Marek Hulan <mhulan>
Component: virt-whoAssignee: Chris Snyder <csnyder>
Status: CLOSED ERRATA QA Contact: Eko <hsun>
Severity: low Docs Contact:
Priority: high    
Version: 7.4CC: bcourt, cdonnell, ktordeur, redakkan, wpoteat, yuefliu
Target Milestone: rcKeywords: Triaged
Target Release: 7.8   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
: 1728692 (view as bug list) Environment:
Last Closed: 2020-03-31 19:08:44 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:
Bug Depends On: 1652549    
Bug Blocks: 1183740, 1623674, 1728692    
Attachments:
Description Flags
pictures20191024 none

Description Marek Hulan 2017-05-03 11:16:56 UTC 
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.
Comment 2 William Poteat 2019-02-21 14:20:05 UTC 
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.
Comment 3 William Poteat 2019-02-21 14:23:41 UTC 
Disregard Comment #2. Was entered on the wrong BZ.
Comment 4 William Poteat 2019-05-23 15:52:09 UTC 
We are using Satellite bug as the information source for this:

https://bugzilla.redhat.com/show_bug.cgi?id=1652549
Comment 5 William Poteat 2019-07-16 14:43:47 UTC 
call is made a new candlepin endpoint if the candlepin version has the capability 'hypervisors_heartbeat'.

"/hypervisors/{owner}/heartbeat"
Comment 8 yuefliu 2019-10-29 02:09:20 UTC 
Created attachment 1629942 [details]
pictures20191024
Comment 10 errata-xmlrpc 2020-03-31 19:08:44 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-2020:0990