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.
Hi Eko,
The Package Versions:
virt-what-1.18-4.el7.x86_64
tfm-rubygem-hammer_cli_foreman_virt_who_configure-0.0.3-2.el7sat.noarch
tfm-rubygem-foreman_virt_who_configure-0.2.2-1.el7sat.noarch
Also, I don't see any logs under satellites /var/log/rhsm/rhsm.log during posting.
Note:
------
I can easily post upto 30 virt guests, but the issue comes when it is more than or equal to 40.
Hi Jitendra,
it's not virt-what package, it should be virt-who, please check again.
and /var/log/rhsm/rhsm.log should be in the host which virt-who was installed.
After discussing with Jitendra, virt-who package never be installed and used for this issue, so I'm afraid it's not a virt-who bug.
According to the error log message, I will move it to the candlepin component to check again.
This does appear to be natively in Candlepin, after posting directly to the virt-who API endpoint the error occurs easily.
We can tune around this via configs in server.xml, I had to get up into the 100MB range before 100 hosts would work:
maxHttpHeaderSize="100000"
that is quite a bit more than the default of 4MB which indicates to me that something isn't really working correctly in formulating the response back to the API call.
Customers with 1000 virtual machines in a virt-who transaction would overwhelm the server and require 1G+ ram in the response which .. is a bit much for a HTTP response.
We need to examine how we are formulating the response headers in this API call.
FailedQA!
Steps:
--------
1. Post 1000/300/200 hypervisors json to rhsm/hypervisors using https://hub.docker.com/r/jacobcallahan/genvirt
Observation:
--------------
500 ISE Error : https://pastebin.com/YrpBeArD
Note:
------------
The post of 100 hypervisors json works.
Already discussed and shared details with jsherrill, crog.
tested this with 5k hosts without error:
# docker run -e "SATHOST=sat-r220-01.lab.eng.rdu2.redhat.com" -e "COUNT=5000" jacobcallahan/genvirt
...
Generating data with 5000 hosts.
Submitting data to sat-r220-01.lab.eng.rdu2.redhat.com. This may take a while...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 771k 0 4 100 771k 0 494 0:26:39 0:26:38 0:00:01 0
nullUnregistering from Satellite
Unregistering from: sat-r220-01.lab.eng.rdu2.redhat.com:443/rhsm
System has been unregistered.
Done!
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/RHSA-2018:2927