Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1624531

Summary: virt-who issue when pushing the information *for fail in result_data.get('failedUpdate', []):*
Product: Red Hat Satellite Reporter: Waldirio M Pinheiro <wpinheir>
Component: Subscriptions - virt-whoAssignee: Barnaby Court <bcourt>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.3.2CC: fcami, hshukla, jsenkyri, khowell, rjerrido, wpoteat
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-17 14:06:51 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:

Description Waldirio M Pinheiro 2018-09-01 00:45:03 UTC
Description of problem:
The customer is facing an issue when pushing information related to the huge virtualization environment *267 hypervisors and 16723 guests found*

Version-Release number of selected component (if applicable):
6.3.x

How reproducible:
100%

Steps to Reproduce:
1. Using JSON customer file
2. Configure fake virt-who conf
3. virt-who -od

Actual results:
---
2018-08-31 20:44:11,229 [virtwho.destination_-4756648715778885625 ERROR] MainProcess(3194):Thread-3 @virt.py:run:388 - Thread 'destination_-4756648715778885625' fails with exception:
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/virtwho/virt/virt.py", line 379, in run
    self._run()
  File "/usr/lib/python2.7/site-packages/virtwho/virt/virt.py", line 335, in _run
    self._send_data(data_to_send)
  File "/usr/lib/python2.7/site-packages/virtwho/virt/virt.py", line 665, in _send_data
    self.dest.check_report_state(batch_host_guest_report)
  File "/usr/lib/python2.7/site-packages/virtwho/manager/subscriptionmanager/subscriptionmanager.py", line 353, in check_report_state
    for fail in result_data.get('failedUpdate', []):
AttributeError: 'unicode' object has no attribute 'get'
2018-08-31 20:44:11,229 [virtwho.destination_-4756648715778885625 INFO] MainProcess(3194):Thread-3 @virt.py:_send_data:553 - Error report received
---

Expected results:
No errors

Additional info:

Comment 3 Kevin Howell 2018-09-04 18:38:32 UTC
Waldirio, we looked into this, it seems our internal handling of in-clause batching generates SQL requests which are too large.

As a workaround, we successfully tried setting "db.config.in.operator.block.size = 1000" in candlepin.conf (default is 32767), and then candlepin will automatically break the resulting queries up into much smaller queries. We still need to do some further investigation in order to determine if there is a more optimal value, but this setting should suffice as a work-around in the meanwhile.

For reference, we run with a limit of 15000 when running against mariadb; we'll do some testing and change the postgre default as appropriate (I suspect either 1000 or 15000 will become the new default).

Comment 7 Kevin Howell 2018-09-17 14:06:51 UTC
Given that the workaround suggested in comment 3 works, marking as dupe.

*** This bug has been marked as a duplicate of bug 1599752 ***