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.
Description of problem:
Some users have reported that the CV version page is excessively slow. Querying certain attributes of a task can generate a large number of SQL queries. The queries themselves are very fast, but buildup and teardown can take some time given the # of queries.
Version-Release number of selected component (if applicable): 6.2.1, dynflow 0.8.11
How reproducible: every time, given correct initial data set
Steps to Reproduce:
1. in terminal #1, foreman-rake console
2. in terminal #2, strace -tt -s999 -e trace=network -f -p <console pid> 2>&1 | grep 'SELECT \* FROM'
3. in terminal #1, run: ForemanTasks::Task.find('<id>').progress
Actual results: 10+ seconds to load progress, and many queries
Expected results: < 1 sec to load the task, ideally less than 100msec
Additional info:
example query output:
[pid 12404] 13:13:41.079970 sendto(14, "Q\0\0\0\202SELECT * FROM \"dynflow_steps\" WHERE ((\"execution_plan_uuid\" = '4c601f6d-0e4c-4725-8131-cd5fd2686558') AND (\"id\" = 1)) LIMIT 1\0", 131, MSG_NOSIGNAL, NULL, 0) = 131
[pid 12404] 13:13:41.081277 sendto(14, "Q\0\0\0\202SELECT * FROM \"dynflow_steps\" WHERE ((\"execution_plan_uuid\" = '4c601f6d-0e4c-4725-8131-cd5fd2686558') AND (\"id\" = 2)) LIMIT 1\0", 131, MSG_NOSIGNAL, NULL, 0) = 131
[pid 12404] 13:13:41.082095 sendto(14, "Q\0\0\0\202SELECT * FROM \"dynflow_steps\" WHERE ((\"execution_plan_uuid\" = '4c601f6d-0e4c-4725-8131-cd5fd2686558') AND (\"id\" = 3)) LIMIT 1\0", 131, MSG_NOSIGNAL, NULL, 0) = 131
[pid 12404] 13:13:41.082863 sendto(14, "Q\0\0\0\202SELECT * FROM \"dynflow_steps\" WHERE ((\"execution_plan_uuid\" = '4c601f6d-0e4c-4725-8131-cd5fd2686558') AND (\"id\" = 4)) LIMIT 1\0", 131, MSG_NOSIGNAL, NULL, 0) = 131
*snip*
[pid 12404] 13:13:54.914686 sendto(14, "Q\0\0\0\206SELECT * FROM \"dynflow_steps\" WHERE ((\"execution_plan_uuid\" = '4c601f6d-0e4c-4725-8131-cd5fd2686558') AND (\"id\" = 16410)) LIMIT 1\0", 135, MSG_NOSIGNAL, NULL, 0) = 135
[pid 12404] 13:13:54.915411 sendto(14, "Q\0\0\0\206SELECT * FROM \"dynflow_steps\" WHERE ((\"execution_plan_uuid\" = '4c601f6d-0e4c-4725-8131-cd5fd2686558') AND (\"id\" = 16411)) LIMIT 1\0", 135, MSG_NOSIGNAL, NULL, 0) = 135
[pid 12404] 13:13:54.916185 sendto(14, "Q\0\0\0\206SELECT * FROM \"dynflow_steps\" WHERE ((\"execution_plan_uuid\" = '4c601f6d-0e4c-4725-8131-cd5fd2686558') AND (\"id\" = 16412)) LIMIT 1\0", 135, MSG_NOSIGNAL, NULL, 0) = 135
[pid 12404] 13:13:54.916917 sendto(14, "Q\0\0\0\206SELECT * FROM \"dynflow_steps\" WHERE ((\"execution_plan_uuid\" = '4c601f6d-0e4c-4725-8131-cd5fd2686558') AND (\"id\" = 16413)) LIMIT 1\0", 135, MSG_NOSIGNAL, NULL, 0) = 135
Comment 7Waldirio M Pinheiro
2016-09-02 14:50:31 UTC
After more digging, it also turned out the content view publish process was generating many unnecessary steps, which lead to more more that 100x bigger execution plans, which lead to more time for the task to run, as well as to show details. More detail, as well as proposed fix at http://projects.theforeman.org/issues/16499
RHEL7 Hotfix RPMs available for Satellite 6.2.1 only:
http://people.redhat.com/~mmccune/1372073/1372073-hotfix.tar
Installation instructions:
1) download tar above to your Satellite 6.2.1 RHEL7 server
2) extract and 'rpm -Uvh <rpms in archive>'
3) katello-service restart
4) Download cleanup script from this bug to your Satellite
curl https://bugzilla.redhat.com/attachment.cgi?id=1199470 > cleanup_repos.rb
5) foreman-rake console < ~/clean_update_repos.rb
6) proceed with normal operations
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/RHBA-2016:1993
Comment 24Zach Huntington-Meath
2016-10-28 14:28:51 UTC
*** Bug 1260141 has been marked as a duplicate of this bug. ***
Description of problem: Some users have reported that the CV version page is excessively slow. Querying certain attributes of a task can generate a large number of SQL queries. The queries themselves are very fast, but buildup and teardown can take some time given the # of queries. Version-Release number of selected component (if applicable): 6.2.1, dynflow 0.8.11 How reproducible: every time, given correct initial data set Steps to Reproduce: 1. in terminal #1, foreman-rake console 2. in terminal #2, strace -tt -s999 -e trace=network -f -p <console pid> 2>&1 | grep 'SELECT \* FROM' 3. in terminal #1, run: ForemanTasks::Task.find('<id>').progress Actual results: 10+ seconds to load progress, and many queries Expected results: < 1 sec to load the task, ideally less than 100msec Additional info: example query output: [pid 12404] 13:13:41.079970 sendto(14, "Q\0\0\0\202SELECT * FROM \"dynflow_steps\" WHERE ((\"execution_plan_uuid\" = '4c601f6d-0e4c-4725-8131-cd5fd2686558') AND (\"id\" = 1)) LIMIT 1\0", 131, MSG_NOSIGNAL, NULL, 0) = 131 [pid 12404] 13:13:41.081277 sendto(14, "Q\0\0\0\202SELECT * FROM \"dynflow_steps\" WHERE ((\"execution_plan_uuid\" = '4c601f6d-0e4c-4725-8131-cd5fd2686558') AND (\"id\" = 2)) LIMIT 1\0", 131, MSG_NOSIGNAL, NULL, 0) = 131 [pid 12404] 13:13:41.082095 sendto(14, "Q\0\0\0\202SELECT * FROM \"dynflow_steps\" WHERE ((\"execution_plan_uuid\" = '4c601f6d-0e4c-4725-8131-cd5fd2686558') AND (\"id\" = 3)) LIMIT 1\0", 131, MSG_NOSIGNAL, NULL, 0) = 131 [pid 12404] 13:13:41.082863 sendto(14, "Q\0\0\0\202SELECT * FROM \"dynflow_steps\" WHERE ((\"execution_plan_uuid\" = '4c601f6d-0e4c-4725-8131-cd5fd2686558') AND (\"id\" = 4)) LIMIT 1\0", 131, MSG_NOSIGNAL, NULL, 0) = 131 *snip* [pid 12404] 13:13:54.914686 sendto(14, "Q\0\0\0\206SELECT * FROM \"dynflow_steps\" WHERE ((\"execution_plan_uuid\" = '4c601f6d-0e4c-4725-8131-cd5fd2686558') AND (\"id\" = 16410)) LIMIT 1\0", 135, MSG_NOSIGNAL, NULL, 0) = 135 [pid 12404] 13:13:54.915411 sendto(14, "Q\0\0\0\206SELECT * FROM \"dynflow_steps\" WHERE ((\"execution_plan_uuid\" = '4c601f6d-0e4c-4725-8131-cd5fd2686558') AND (\"id\" = 16411)) LIMIT 1\0", 135, MSG_NOSIGNAL, NULL, 0) = 135 [pid 12404] 13:13:54.916185 sendto(14, "Q\0\0\0\206SELECT * FROM \"dynflow_steps\" WHERE ((\"execution_plan_uuid\" = '4c601f6d-0e4c-4725-8131-cd5fd2686558') AND (\"id\" = 16412)) LIMIT 1\0", 135, MSG_NOSIGNAL, NULL, 0) = 135 [pid 12404] 13:13:54.916917 sendto(14, "Q\0\0\0\206SELECT * FROM \"dynflow_steps\" WHERE ((\"execution_plan_uuid\" = '4c601f6d-0e4c-4725-8131-cd5fd2686558') AND (\"id\" = 16413)) LIMIT 1\0", 135, MSG_NOSIGNAL, NULL, 0) = 135