Pulp

First off, can you upload the error log in text? I can't read docx.

Secondly, it sounds like you have a repo (or repos?) with repo_id of null. Here's how you can clean that up:

mongo pulp_database
> db.repos.deleteMany({"repo_id": null})

Not sure what could have caused this since the pulp code doesn't allow repo_id to be null. Maybe an old bug?

I see the problem. It looks like in 2.8, we renamed the id field to repo_id:

https://github.com/pulp/pulp/blob/2-master/server/pulp/server/db/migrations/0019_repo_collection_id.py

However, manage.py calls ensure_database_indexes:

https://github.com/pulp/pulp/blob/2-master/server/pulp/server/db/manage.py#L157

This tries to create an index on repo_id before the field is renamed. Can you try upgrading to 2.8 first and then to 2.18?

Sure will give a try on this to update first to 2.8 and then to 2.18,one doubt here as we upgraded from 2.7 that will id field to repo_id will not be changed?.As i see in the servers has same info as mentioned in the links that were provided,so can you please let me know on that.

manage.py has ensure_database_indexes: info.

Thanks for the reply.

I'm not sure I fully understand your question. When you upgrade from 2.7 to 2.8, id will be renamed to repo_id for repositories.

I think you should be able to upgrade from 2.8 to 2.18 in one step.

I am not sure about how long it will take to upgrade. These pulp versions predate my time with Pulp. Maybe someone else on the Pulp team can weigh in on which version upgrades might take a long time?

Alternatively, can you clone your production environment and then attempt to upgrade the clone? Then you could get an pretty accurate idea of how long it will take and what issues you might encounter.

I started updating the dev environment version by version,now i am in Pulp 2.12 and application works fine without issues,so going version version tells me which version is blocking me here.

I can take a clone of production and do the testing but here problem is it has large chunk from NAS share,and puppet code need to be changed as well there.Once i update my dev environment to version 2.18 and mongodb to 4.0 version

i will see if the clone option works fine in my case as we have cluster of servers it is not a standalone environment.But that is good way of testing on production.

From my observation while doing upgrade from 2.11 to 2.12 there are few migrations of units that occurred in rpm plugin migrations and to complete pulp-manage-db it took 5 mins in my case.

Can you please let me know what exactly it is migrating here.

Migration to pulp_rpm.plugins.migrations version 38 complete.
Applying pulp_rpm.plugins.migrations version 39
*********************************************************************************

• NOTE: This migration may take some time depending on the size of your Pulp content. *
  *********************************************************************************
• Migrating RPM content...
• Migrated units: 5637 of 56377
• Migrated units: 11274 of 56377
• Migrated units: 16911 of 56377
• Migrated units: 22548 of 56377
• Migrated units: 28185 of 56377
• Migrated units: 33822 of 56377
• Migrated units: 39459 of 56377
• Migrated units: 45096 of 56377
• Migrated units: 50733 of 56377
• Migrated units: 56370 of 56377
• Migrated units: 56377 of 56377
• Migrating SRPM content...
• Migrated units: 2 of 27
• Migrated units: 4 of 27
• Migrated units: 6 of 27
• Migrated units: 8 of 27
• Migrated units: 10 of 27
• Migrated units: 12 of 27
• Migrated units: 14 of 27
• Migrated units: 16 of 27
• Migrated units: 18 of 27
• Migrated units: 20 of 27
• Migrated units: 22 of 27
• Migrated units: 24 of 27
• Migrated units: 26 of 27
• Migrated units: 27 of 27
  *********************************************************************************

As always thanks for your time and help on this.

FWIW, I don't know if MongoDB 4.0 is working correctly with Pulp, but definitely MongoDB from 2.4 and up to 3.6 is supported.

As for your migrations question, 0039 migration solves the problem for [S]RPMs with huge metadata by compressing it before storing in DB.
https://github.com/pulp/pulp_rpm/blob/2-master/plugins/pulp_rpm/plugins/migrations/0039_gzip_repodata.py

Thanks for the info ttereshc, we are running mongodb 2.6 so we are good with pulp 2.18 version coming to the supported version.Please confirm.