Bug 2223196 - CV publish too slow when using a simple exclude filter
Summary: CV publish too slow when using a simple exclude filter
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.14.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-16 13:29 UTC by mithun kalyat
Modified: 2023-08-14 12:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-14 12:17:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-19339 0 None None None 2023-08-02 18:05:47 UTC

Description mithun kalyat 2023-07-16 13:29:06 UTC
Description of problem:


Publish too slow when using a simple exclude filter.

CV with following repositories:

   Red Hat Enterprise Linux 8 for x86_64 - AppStream RPMs 8	
	
   Red Hat Enterprise Linux 8 for x86_64 - BaseOS RPMs 8

And the filter:

# hammer content-view filter info --id 1
Filter ID:    1
Name:         First
Type:         erratum
Inclusion:    false
Description:  
Repositories: 

Rules:        
 1) Id:         1
    Start Date: 2023-01-01T12:00:00.000Z
    End Date:   2023-07-16T12:00:00.000Z
    Types:      security, enhancement, bugfix
    Created:    2023/07/16 08:30:45
    Updated:    2023/07/16 08:31:07

And the publish task took more than an hour to complete.

========
Id:3f8724e6-7a8a-44b6-8b82-c924eeb37ee5
Label:Actions::Katello::ContentView::Publish
Duration:1 hour
========

I think it is taking too much time to complete "Actions::Katello::Repository::IndexContent" task.

Comment 1 Brad Buckingham 2023-07-17 12:05:39 UTC
Is this a regression in behavior from previous Satellite release?


Note You need to log in before you can comment on or make changes to this bug.