Bug 1175616 - drop index on erratum title
Summary: drop index on erratum title
Alias: None
Product: Pulp
Classification: Retired
Component: rpm-support
Version: 2.5
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 2.6.1
Assignee: Barnaby Court
QA Contact: Preethi Thomas
: 1177160 1178127 1178834 (view as bug list)
Depends On:
Blocks: 1175620
TreeView+ depends on / blocked
Reported: 2014-12-18 08:14 UTC by Stephen Benjamin
Modified: 2019-02-15 13:57 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-02-03 00:23:44 UTC

Attachments (Terms of Use)
log of pulp failure (3.84 KB, text/plain)
2014-12-18 08:21 UTC, Stephen Benjamin
no flags Details

Description Stephen Benjamin 2014-12-18 08:14:42 UTC
Description of problem:
Some errata in EPEL use unreasonably long names, which causes Pulp syncing of the repo to fail (logs attached).

For an example, there is an erratum with this title:


Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Sync EPEL7

Actual results:
Sync fails

Expected results:
Sync succeeds

Additional info:
EPEL/Fedora have no intention of fixing this:

Comment 1 Stephen Benjamin 2014-12-18 08:21:11 UTC
Created attachment 970437 [details]
log of pulp failure

Comment 2 Justin Sherrill 2014-12-18 15:48:52 UTC
Related to:  https://bugzilla.redhat.com/show_bug.cgi?id=1161277

Comment 3 Barnaby Court 2015-01-02 20:12:05 UTC
*** Bug 1178127 has been marked as a duplicate of this bug. ***

Comment 4 Barnaby Court 2015-01-02 20:26:06 UTC
We are going to fix this in Pulp by dropping the index on the title field since it is not required.

Comment 5 Barnaby Court 2015-01-02 20:27:02 UTC
A workaround in the short term is to drop the index on the title field of erratum:

# mongo pulp_database
# db.units_erratum.dropIndex("title_1")

Comment 6 Sayli Karmarkar 2015-01-05 17:05:48 UTC
*** Bug 1177160 has been marked as a duplicate of this bug. ***

Comment 7 Sayli Karmarkar 2015-01-05 17:10:13 UTC
*** Bug 1178834 has been marked as a duplicate of this bug. ***

Comment 8 Barnaby Court 2015-01-06 21:26:18 UTC

Comment 9 Chris Duryee 2015-01-15 00:27:24 UTC
This was merged to 2.6-dev, which aligns to 2.6.1.

If you need it in 2.6.0, please create a new PR against 2.6-testing and set the target release back to 2.6.0.

Comment 10 Chris Duryee 2015-01-16 23:00:04 UTC
pulp 2.6.0 beta 5

Comment 12 Preethi Thomas 2015-01-30 18:51:31 UTC

[root@cloud-qe-4 ~]# rpm -qa pulp-server
[root@cloud-qe-4 ~]# 

[root@cloud-qe-4 ~]# pulp-admin rpm repo create --repo-id epel7 --feed http://mirror.karneval.cz/pub/linux/fedora/epel/7/x86_64/
Successfully created repository [epel7]

[root@cloud-qe-4 ~]# pulp-admin rpm repo sync run --repo-id epel7
                    Synchronizing Repository [epel7]

This command may be exited via ctrl+c without affecting the request.

Downloading metadata...
... completed

Downloading repository content...
[==================================================] 100%
RPMs:       7161/7161 items
Delta RPMs: 0/0 items

... completed

Downloading distribution files...
[==================================================] 100%
Distributions: 0/0 items
... completed

Importing errata...
... completed

Importing package groups/categories...
... completed

Task Succeeded

Waiting to begin...
Initializing repo metadata
... completed

Publishing Distribution files
... completed

Publishing RPMs
[==================================================] 100%
7161 of 7161 items
... completed

Publishing Delta RPMs
... skipped

Publishing Errata
[==================================================] 100%
1252 of 1252 items
... completed

Publishing Comps file
[==================================================] 100%
214 of 214 items
... completed

Publishing Metadata.
... completed

Closing repo metadata
... completed

Generating sqlite files
... skipped

Publishing files to web
... completed

Writing Listings File
... completed

Task Succeeded

Comment 13 Justin Sherrill 2015-02-03 00:23:44 UTC

*** This bug has been marked as a duplicate of bug 1161277 ***

Comment 14 Stephen Benjamin 2015-02-07 20:00:17 UTC
Why was this move changed from VERIFIED to DUPLICATE? This is the bug that was worked off of and verified by QA.  Perhaps the status should be changed on the other bug, but now everything is in weird state:

It's fixed but this says DUPLICATE, and the other one says NOTABUG.

I don't have permissions to change anything.

Comment 15 Michael Hrivnak 2015-05-04 13:50:56 UTC
Because of the incorrect state, this bug didn't get migrated to redmine initially. I have made the below redmine issue the new place to track this bug.


Comment 16 Justin Sherrill 2017-02-06 13:36:05 UTC
Clearing needinfo

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