Bug 1599752 - virt-who failed to upload data to satellite 6 if VM count is more than 17000
Summary: virt-who failed to upload data to satellite 6 if VM count is more than 17000
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscriptions - virt-who
Version: 6.3.2
Hardware: All
OS: Linux
high
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Kunxin Huang
URL:
Whiteboard:
: 1624531 (view as bug list)
Depends On: 1601517 1674544 1674546
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-10 13:48 UTC by Sunayana
Modified: 2023-09-07 19:14 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1601517 (view as bug list)
Environment:
Last Closed: 2019-05-09 20:14:23 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1599725 1 None None None 2023-09-07 19:14:05 UTC
Red Hat Bugzilla 1603706 0 urgent CLOSED multiple virt-who configurations create multiples users == *undefined method `[]' for nil:NilClass* error on Hypervisor ... 2023-03-24 14:09:43 UTC
Red Hat Bugzilla 1624531 0 unspecified CLOSED virt-who issue when pushing the information *for fail in result_data.get('failedUpdate', []):* 2023-03-24 14:13:18 UTC
Red Hat Knowledge Base (Solution) 3638281 0 None None None 2018-10-03 16:00:09 UTC

Internal Links: 1599725 1603706 1624531 1693249

Description Sunayana 2018-07-10 13:48:08 UTC 
Description of problem:

virt-who failed to upload data to satellite 6 in case  VM count is more than 17000

Version-Release number of selected component (if applicable):
satellite-6.3.2


Steps to Reproduce:
virt-who is configured on satellite and number of hosts which are reporting are more than 17000

virt-who -d -o output is showing below error:
2018-07-06 00:23:39,455 [virtwho.destination_-2538080013810018285 INFO] MainProcess(31176):Thread-14 @virt.py:_send_data:553 - Error report received
2018-07-06 00:23:39,455 [virtwho.destination_-2538080013810018285 DEBUG] MainProcess(31176):Thread-14 @virt.py:run:402 - Thread 'destination_-2538080013810018285' stopped after running once
2018-07-06 00:23:39,569 [virtwho.main DEBUG] MainProcess(31176):MainThread @__main__.py:main:23 - virt-who terminated
2018-07-06 00:23:39,569 [virtwho.main DEBUG] MainProcess(31176):MainThread @executor.py:terminate:222 - virt-who is shutting down

When number of hosts which are reporting are less than 17000, report are successfully uploaded to satellite and no error in "virt-who -d -o"


Actual results:

virt-who -d -o output is showing below error:
2018-07-06 00:23:39,455 [virtwho.destination_-2538080013810018285 INFO] MainProcess(31176):Thread-14 @virt.py:_send_data:553 - Error report received
2018-07-06 00:23:39,455 [virtwho.destination_-2538080013810018285 DEBUG] MainProcess(31176):Thread-14 @virt.py:run:402 - Thread 'destination_-2538080013810018285' stopped after running once
2018-07-06 00:23:39,569 [virtwho.main DEBUG] MainProcess(31176):MainThread @__main__.py:main:23 - virt-who terminated
2018-07-06 00:23:39,569 [virtwho.main DEBUG] MainProcess(31176):MainThread @executor.py:terminate:222 - virt-who is shutting down

Expected results:

virt-who -d -o output should not show any error and satellite should receive reports for all VMs successfully
Comment 7 Kevin Howell 2018-07-16 14:24:42 UTC 
Note: we suspect we're generating SQL too large for Postgres.
Comment 13 Kevin Howell 2018-09-17 14:06:51 UTC 
*** Bug 1624531 has been marked as a duplicate of this bug. ***
Comment 15 ironiq 2018-11-23 10:39:08 UTC 
We also run into the problem that was marked as duplicate of this (#1624531), but here i could identify a problem: there is a "fake" hypervisor with id but without even name or version or any guests. I think this can also cause a problem.
Comment 16 William Poteat 2019-05-09 20:14:23 UTC 
As per

https://bugzilla.redhat.com/show_bug.cgi?id=1694809#c1

This is not a virt-who issue, but one in candlepin
Note You need to log in before you can comment on or make changes to this bug.