Re: [Pulp-list] db migration with pulp update to 2.18.0 failed

2018-12-04 Thread David Davis
Jim, Thanks for the response. I opened the following bug for the error you hit: https://pulp.plan.io/issues/4225 I also wanted to suggest that you think about upgrading mongo to a 3.x release. 2.6 reached its end of life in 2016. David On Tue, Dec 4, 2018 at 6:21 PM Jim Davis wrote: > #

Re: [Pulp-list] db migration with pulp update to 2.18.0 failed

2018-12-04 Thread Jim Davis
# rpm -qa | grep mongo python-pymongo-gridfs-3.2-2.el7.x86_64 python-pymongo-3.2-2.el7.x86_64 python-mongoengine-0.10.5-1.el7.noarch mongodb-server-2.6.12-6.el7.x86_64 Applied the changes from below and re-ran the migration: … Applying pulp.server.db.migrations version 29

Re: [Pulp-list] db migration with pulp update to 2.18.0 failed

2018-12-04 Thread David Davis
Jim, What version of pymongo and mongodb do you have on your system? You can check with: rpm -qa | grep mongo. I think you could make the following fix in /usr/lib/python2.7/site-packages/pulp/server/db/migrations/0029_applicability_schema_change.py:

[Pulp-list] db migration with pulp update to 2.18.0 failed

2018-12-04 Thread Jim Davis
The yum update worked without errors but the db migration failed. Any ideas from the output?? # sudo -u apache pulp-manage-db Attempting to connect to localhost:27017 Attempting to connect to localhost:27017 Write concern for Mongo connection: {} Loading content types. Loading type descriptors

[Pulp-list] Pulp Community Demo - Dec 5th

2018-12-04 Thread Brian Bouterse
On Wednesday, the Pulp community demo will be broadcast live via YouTube. The tentative agenda is: * Pulp3 Lazy Sync, bmbouter, 3.0 * Pulp3 Docker Sync and Publish, dkliban, 3.0 When: Dec 5th at 3pm UTC [0] Where: https://www.youtube.com/watch?v=IeY4lI8jG38 Interact: Chat during the event on the