Bug 1271252

The sending of the information twice was a configuration mistake. Both the new style /etc/virt-who.d and the legacy environment variables were defined.
After removing the legacy environment variables it is now send only once

Based on Comemnt 1, closing this out.

Re-opening the comment 1 was only about second remark of the duplicate sending. 

The interval being 15minutes instead of 60minutes is still the issue, even with only 1 ESX server defined:

# grep hypervisors_update /var/log/foreman/production.log
2015-10-14 03:42:00 [I] Processing by Katello::Api::Rhsm::CandlepinProxiesController#hypervisors_update as JSON
2015-10-14 03:57:01 [I] Processing by Katello::Api::Rhsm::CandlepinProxiesController#hypervisors_update as JSON
2015-10-14 04:12:01 [I] Processing by Katello::Api::Rhsm::CandlepinProxiesController#hypervisors_update as JSON
2015-10-14 04:27:01 [I] Processing by Katello::Api::Rhsm::CandlepinProxiesController#hypervisors_update as JSON
2015-10-14 04:42:02 [I] Processing by Katello::Api::Rhsm::CandlepinProxiesController#hypervisors_update as JSON
2015-10-14 04:57:02 [I] Processing by Katello::Api::Rhsm::CandlepinProxiesController#hypervisors_update as JSON
2015-10-14 05:12:02 [I] Processing by Katello::Api::Rhsm::CandlepinProxiesController#hypervisors_update as JSON
2015-10-14 05:27:02 [I] Processing by Katello::Api::Rhsm::CandlepinProxiesController#hypervisors_update as JSON
2015-10-14 05:42:03 [I] Processing by Katello::Api::Rhsm::CandlepinProxiesController#hypervisors_update as JSON
2015-10-14 05:57:03 [I] Processing by Katello::Api::Rhsm::CandlepinProxiesController#hypervisors_update as JSON
2015-10-14 06:12:03 [I] Processing by Katello::Api::Rhsm::CandlepinProxiesController#hypervisors_update as JSON
2015-10-14 06:27:04 [I] Processing by Katello::Api::Rhsm::CandlepinProxiesController#hypervisors_update as JSON
2015-10-14 06:42:04 [I] Processing by Katello::Api::Rhsm::CandlepinProxiesController#hypervisors_update as JSON
2015-10-14 06:57:04 [I] Processing by Katello::Api::Rhsm::CandlepinProxiesController#hypervisors_update as JSON

Moving to the virt-who component.

Upstream virt-who (that will get to 7.3 by rebase) is now sending host/guest association to candlepin only when it changes. The interval now only determines how often should virt-who look for changes in hypervisors.

There is also a rate-limit that will throttle reports going to candlepin which should also reduce the load.

Fixed in virt-who-0.17-1.el7.

We are using RHEL6.8. How about RHEL6 virt-who?

Peter, this should be already fixed in RHEL-6.8. The fix there is the same as in RHEL-7:

Upstream virt-who is now sending host/guest association to candlepin only when it changes. The interval now only determines how often should virt-who look for changes in hypervisors.

There is also a rate-limit that will throttle reports going to candlepin which should also reduce the load.

Confirmed it is fixed in RHEL6.8. Below is my log of sending of the hosts-to-guests, after the upgrade to RHEl6.8 there was only 3 times an update being send instead of every 15 minutes:

2016-05-17 11:21:53,501 [INFO]  @subscriptionmanager.py:146 - Sending update in hosts-to-guests mapping: {
2016-05-17 11:36:53,875 [INFO]  @subscriptionmanager.py:146 - Sending update in hosts-to-guests mapping: {
2016-05-17 11:51:54,262 [INFO]  @subscriptionmanager.py:146 - Sending update in hosts-to-guests mapping: {
2016-05-17 12:06:54,647 [INFO]  @subscriptionmanager.py:146 - Sending update in hosts-to-guests mapping: {
2016-05-17 12:11:14,571 [INFO]  @subscriptionmanager.py:146 - Sending update in hosts-to-guests mapping: {
2016-05-17 12:26:14,903 [INFO]  @subscriptionmanager.py:146 - Sending update in hosts-to-guests mapping: {
2016-05-17 12:41:15,234 [INFO]  @subscriptionmanager.py:146 - Sending update in hosts-to-guests mapping: {
2016-05-17 12:56:15,546 [INFO]  @subscriptionmanager.py:146 - Sending update in hosts-to-guests mapping: {
2016-05-17 13:11:15,914 [INFO]  @subscriptionmanager.py:146 - Sending update in hosts-to-guests mapping: {
2016-05-17 13:25:43,886 [INFO]  @subscriptionmanager.py:146 - Sending update in hosts-to-guests mapping: {
2016-05-17 13:28:19,524 [INFO]  @subscriptionmanager.py:146 - Sending update in hosts-to-guests mapping: {
2016-05-17 13:33:46,036 [INFO]  @subscriptionmanager.py:146 - Sending update in hosts-to-guests mapping: {
2016-05-17 13:48:19,905 [INFO]  @subscriptionmanager.py:146 - Sending update in hosts-to-guests mapping: {
2016-05-17 13:56:06,391 [INFO]  @subscriptionmanager.py:146 - Sending update in hosts-to-guests mapping: {
2016-05-17 14:11:06,700 [INFO]  @subscriptionmanager.py:146 - Sending update in hosts-to-guests mapping: {

<<< Upgrade to RHEL6.8 >>>>>
$ sudo grep virt-who /var/log/yum.log
May 17 14:14:27 Updated: virt-who-0.16-8.el6.noarch

2016-05-17 14:15:50,043 [INFO]  @subscriptionmanager.py:185 - Sending update in hosts-to-guests mapping for config "li-vcenterd01.hilti.com": 4 hypervisors and 117 guests found
2016-05-18 09:49:02,682 [INFO]  @subscriptionmanager.py:185 - Sending update in hosts-to-guests mapping for config "li-vcenterd01.hilti.com": 4 hypervisors and 117 guests found
2016-05-18 10:00:42,509 [INFO]  @subscriptionmanager.py:185 - Sending update in hosts-to-guests mapping for config "li-vcenterd01.hilti.com": 4 hypervisors and 117 guests found

That should work if they don't need updates in the meantime. I'm not aware of any other workaround.

Verified it on virt-who-0.17-2.el7.noarch since virt-who can refresh host/guest association as configure interval(every 1 hour). Therefore, verify it.

Verified version:
virt-who-0.17-2.el7.noarch
subscription-manager-1.17.6-1.el7.x86_64
python-rhsm-1.17.2-1.el7.x86_64

Verified process:
1. register system to satellite6.2
2. Configure virt-who run at esx mode and refresh interval is 3600s
[root@dell-per920-02 ~]# cat /etc/sysconfig/virt-who  | grep -v ^# | grep -v ^$
VIRTWHO_DEBUG=1
VIRTWHO_INTERVAL=3600

[root@dell-per920-02 ~]# cat /etc/virt-who.d/virt 
[test-esx1]
type=esx
server=10.73.2.95
username=Administrator
password=Welcome1!
owner=ACME_Corporation
env=Library
3. Restart virt-who service and check virt-who's log after 1h.
2016-06-02 01:55:20,184 [virtwho.test-esx1 DEBUG] Esx-1(86984):MainThread @virt.py:enqueue:357 - Report for config "test-esx1" gathered, putting to queue for sending
2016-06-02 01:55:20,204 [virtwho.main DEBUG] MainProcess(86977):MainThread @subscriptionmanager.py:_connect:123 - Authenticating with certificate: /etc/pki/consumer/cert.pem
2016-06-02 01:55:22,013 [virtwho.main DEBUG] MainProcess(86977):MainThread @subscriptionmanager.py:hypervisorCheckIn:171 - Checking if server has capability 'hypervisor_async'
2016-06-02 01:55:23,817 [virtwho.main DEBUG] MainProcess(86977):MainThread @subscriptionmanager.py:hypervisorCheckIn:183 - Server does not have 'hypervisors_async' capability
2016-06-02 01:55:23,818 [virtwho.main INFO] MainProcess(86977):MainThread @subscriptionmanager.py:hypervisorCheckIn:194 - Sending update in hosts-to-guests mapping for config "test-esx1": 2 hypervisors and 1 guests found
2016-06-02 01:55:23,818 [virtwho.main DEBUG] MainProcess(86977):MainThread @subscriptionmanager.py:hypervisorCheckIn:195 - Host-to-guest mapping: {
    "3e504d56-3982-037b-f3e6-669289892fa1": [
        {
            "guestId": "4206405a-4133-bd0c-f8a5-9c7bc1355837", 
            "state": 1, 
            "attributes": {
                "active": 1, 
                "virtWhoType": "esx"
            }
        }
    ], 
    "60554d56-20cb-f25e-7ab9-33e7e330dc15": []
}
2016-06-02 01:55:25,917 [virtwho.main DEBUG] MainProcess(86977):MainThread @executor.py:send_report:101 - Report for config "test-esx1" sent

===============After 1h, virt-who check mapping info================
2016-06-02 02:55:20,428 [virtwho.test-esx1 DEBUG] Esx-1(86984):MainThread @virt.py:enqueue:357 - Report for config "test-esx1" gathered, putting to queue for sending
2016-06-02 02:55:20,434 [virtwho.main INFO] MainProcess(86977):MainThread @executor.py:run:250 - Report for config "test-esx1" hasn't changed, not sending

Result:
virt-who won't refresh every 15mins, it refresh host/guest association every 1 hour.

Confirmed that sending only updates to sat6 when changes are there is working in RHEL7.2

2016-10-14 14:02:51,817 [INFO] @executor.py:250 - Report for config "Library::li-vcenterd01.hilti.com" hasn't changed, not sending
2016-10-14 14:02:51,852 [INFO] @executor.py:250 - Report for config "Library::li-vcenterd01.hilti.com" hasn't changed, not sending
2016-10-14 14:02:51,881 [INFO] @executor.py:250 - Report for config "Library::li-vcenterd01.hilti.com" hasn't changed, not sending
2016-10-14 14:02:51,912 [INFO] @executor.py:250 - Report for config "Library::li-vcenterd01.hilti.com" hasn't changed, not sending
2016-10-14 14:02:51,943 [INFO] @executor.py:250 - Report for config "Library::li-vcenterd01.hilti.com" hasn't changed, not sending
2016-10-14 14:17:58,374 [INFO] @executor.py:250 - Report for config "Library::li-vcenterd01.hilti.com" hasn't changed, not sending
2016-10-14 14:21:19,203 [INFO] @executor.py:250 - Report for config "Library::li-vcenterd01.hilti.com" hasn't changed, not sending
2016-10-14 15:21:19,206 [INFO] @executor.py:250 - Report for config "Library::li-vcenterd01.hilti.com" hasn't changed, not sending

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://rhn.redhat.com/errata/RHBA-2016-2387.html