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.
I deleted all audit records and it loads pretty quick..Don't know if people could use that as a workaround while we get a fix in. It's definitely related to a change we added in 6.14 around auditing CV publishes but the querying for that needs to be improved based on number of audits we are looking at. Ex: 204600 on the repro before I cleared it..
Verified in 6.16.0 (Stream snap 60.0).
Steps to verify:
1. Import maifest and sync 30 RH repos.
2. Creat a CV and add all repos from 1.
3. Clone the CV 39x so that we end up with 40 CVs.
4. Creat 3 LCEs above the Library.
5. Publish all the CVs and promote them to all LCEs.
At this point you have ~38200 audits.
6. List the CVs via hammer and measure the time:
[root@sat ~]# time hammer content-view list
At the reproducer VM (6.14.3 snap 2.0) the listing took 7.754 seconds in average.
At the fixed VM (Stream snap 60.0) the listing took 2.429 seconds in average.
This means 3.19 times faster listing with the given setup and the ratio would be even higher for bigger setup with more repos/CVs/audits.
Unfortunately I can't say the same about the WebUI, which is actually slower than 6.14.3, but that should be tracked by https://bugzilla.redhat.com/show_bug.cgi?id=2274159
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.