Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Created attachment 1193457[details]
rhsm.log for 100 configure files
Description of problem:
We try to create 100 same configure files in /etc/virt-who.d for rhevm mode performance testing, that means virt-who will create 100 PIDs and fetch the hosts/guests info from RHEVM Server, some of the PIDs failed with "Unable to connect to RHEV-M server: 503 Server Error: Service Unavailable"
Version-Release number of selected component (if applicable):
virt-who-0.17-7.el7.noarch
subscription-manager-1.17.10-1.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1.create 100 configure files in /etc/virt-who.d for rhevm mode
2.run virt-who with oneshot option and check rhsm.log, many PIDs failed due to the following error:
2016-08-22 22:27:14,698 [virtwho.test-rhevm_1 ERROR] RhevM-1(8732):MainThread @virt.py:run:375 - Virt backend 'test-rhevm_1' fails with error: Unable to connect to RHEV-M server: 503 Server Error: Service Unavailable
Actual results:
some of the PIDs failed with "Unable to connect to RHEV-M server: 503 Server Error: Service Unavailable"
Expected results:
All the virt-who PIDs can fetch the host/guests info normally
Additional info:
Given that virt-who connects to the same hypervisor 100 times in parallel, it's quite expected that one hypervisor won't be able to handle all the requests.
Please retry with more than one hypervisor. As I see it now, this is not a bug.
Created attachment 1193457 [details] rhsm.log for 100 configure files Description of problem: We try to create 100 same configure files in /etc/virt-who.d for rhevm mode performance testing, that means virt-who will create 100 PIDs and fetch the hosts/guests info from RHEVM Server, some of the PIDs failed with "Unable to connect to RHEV-M server: 503 Server Error: Service Unavailable" Version-Release number of selected component (if applicable): virt-who-0.17-7.el7.noarch subscription-manager-1.17.10-1.el7.x86_64 How reproducible: always Steps to Reproduce: 1.create 100 configure files in /etc/virt-who.d for rhevm mode 2.run virt-who with oneshot option and check rhsm.log, many PIDs failed due to the following error: 2016-08-22 22:27:14,698 [virtwho.test-rhevm_1 ERROR] RhevM-1(8732):MainThread @virt.py:run:375 - Virt backend 'test-rhevm_1' fails with error: Unable to connect to RHEV-M server: 503 Server Error: Service Unavailable Actual results: some of the PIDs failed with "Unable to connect to RHEV-M server: 503 Server Error: Service Unavailable" Expected results: All the virt-who PIDs can fetch the host/guests info normally Additional info: