Hide Forgot
Description of problem: Given an instance of virt-who configured to report on multiple sources to multiple destinations (for example a satellite 6 instance and hosted rhsm), it will take number_of_sources * number_of_destinations * interval amount of time (at a minimum) to send all reports. As an example if there are 4 sources and we use the default interval of 4 hours, going just to one destination it will take 16 hours to send at least one update on all sources. Additional info: See upstream virt-who branch feature/interval_design (https://github.com/virt-who/virt-who/tree/feature/interval_design) for current work on this feature
The posted PR has been merged upstream. Moving to POST.
it still exists with virt-who-0.19-4
update comment3, check the bug with virt-who-0.19-4, the steps and result as below: packages: virt-who-0.19-4.el7.noarch subscription-manager-1.19.12-1.el7.x86_64 python-rhsm-1.19.6-1.el7.x86_64 steps: 1. configure virt-who run in ESX & HYPERV sources against Stage Candlepin server and Libvirt & XEN sources against Satellite6.2.9 server, refer to attachment for config file. 2. start virt-who with 300s interval, it will send all sources mapping info to their server immediately the first run. # virt-who -d -i 300 3. make 'shutdown/power off' trigger for guest of each hypervisor source, the mapping update info of the four hypervisors cannot be sent together after 300s, some are sent one by one each 300s. Please refer to attachment - "rhsm log and virt-who config file"
Created attachment 1277340 [details] rhsm log and virt-who config file
Verified the bug with virt-who-0.19-5, when configure virt-who run in multi hypervisor modes, after restart virt-who service, it can fetch and send all the hypervisors mapping to server in the first interval, no time delay.
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