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.
DescriptionManikandan Somasundaram
2016-08-26 09:59:11 UTC
Created attachment 1194278[details]
Foreman-Debug with sql log
Description of problem:
Customer is facing a web UI slowness issue on all operations regardless of specific once, their Hardware specification matched more them the prerequisite,
Sar report shows the CPU is idle by 72% approx, however we can see postgres is consuming high cpu
Customer issue starts the case 01688646, where they are note be able to upgrade a capsule once they have upgraded their satellite server from 6.1 to 6.2, they end up asking them to register the capsule server with Satellite 6.2
please analysis the case
Version-Release number of selected component (if applicable): 6.2
How reproducible:
Steps to Reproduce:
1. upgrade satellite from 6.1 to 6.2
2. check the performance of satellite 6.2
Actual results:
Satellite UI is too slow during all the operations the customer tries to do
Expected results:
Smooth UI operation
Additional info:
We have collected foreman-debug with DB log enabled, which has attached in this bug
I am closing this bug (1370426) in favor of those listed in comment #3.
There is no "closed/broke up into multiple bugs", so I'm marking as closed/notabug.
If the bugs in #3 don't cover the issues you see, let me know and we can investigate further to see if the issue is covered by an existing bug, or needs a new one.
Created attachment 1194278 [details] Foreman-Debug with sql log Description of problem: Customer is facing a web UI slowness issue on all operations regardless of specific once, their Hardware specification matched more them the prerequisite, Sar report shows the CPU is idle by 72% approx, however we can see postgres is consuming high cpu Customer issue starts the case 01688646, where they are note be able to upgrade a capsule once they have upgraded their satellite server from 6.1 to 6.2, they end up asking them to register the capsule server with Satellite 6.2 please analysis the case Version-Release number of selected component (if applicable): 6.2 How reproducible: Steps to Reproduce: 1. upgrade satellite from 6.1 to 6.2 2. check the performance of satellite 6.2 Actual results: Satellite UI is too slow during all the operations the customer tries to do Expected results: Smooth UI operation Additional info: We have collected foreman-debug with DB log enabled, which has attached in this bug