Bug 1728692

Summary: Virt-who should send reports even when there's no update on hypervisor
Product: Red Hat Enterprise Linux 8 Reporter: William Poteat <wpoteat>
Component: virt-whoAssignee: candlepin-bugs
Status: CLOSED ERRATA QA Contact: Eko <hsun>
Severity: low Docs Contact:
Priority: high    
Version: 8.1CC: bcourt, cdonnell, csnyder, hsun, ktordeur, kuhuang, mhulan, wchadwic, wpoteat, yuefliu
Target Milestone: rcKeywords: Triaged
Target Release: 8.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1447633 Environment:
Last Closed: 2019-11-05 20:56:28 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: 1447633, 1652549    
Bug Blocks: 1183740, 1623674    
Attachments:
Description Flags
attachment on July 24
none
screenshot20190910 none

Comment 2 William Poteat 2019-07-16 14:43:01 UTC 
call is made a new candlepin endpoint if the candlepin version has the capability 'hypervisors_heartbeat'.

"/hypervisors/{owner}/heartbeat"
Comment 5 yuefliu 2019-07-24 10:12:38 UTC 
Created attachment 1593094 [details]
attachment on July 24
Comment 10 William Poteat 2019-08-29 17:51:38 UTC 
The code for this is in the builds for RHEL 8.1. It got delayed because the Candlpin/Portal/Satellite builds were not ready in time to verify the behavior.

It has been promised in RHEL 8.1 and needs to be fixed for usage against the aforementioned products.
Comment 13 yuefliu 2019-09-10 12:45:45 UTC 
Created attachment 1613575 [details]
screenshot20190910
Comment 15 errata-xmlrpc 2019-11-05 20:56:28 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-2019:3372