[Pulp-list] Failed DB migrations in upgrade to 3.14.2
David Davis
daviddavis at redhat.com
Fri Jul 16 19:44:40 UTC 2021
Hi Marcin,
I was able to reproduce this and filed a bug:
https://pulp.plan.io/issues/9102
I have also opened a fix:
https://github.com/pulp/pulp_file/pull/538/files#diff-6c586b4d1d0bff684f9c6a196269a636cb8f91d1f536f25d27ba392f86ea4ea6
You should be able to apply this patch locally (use `pip show pulp_file` to
find where the pulp_file package is on your system) and then re-run the
installer.
Let me know if that works or not for you.
David
On Thu, Jul 15, 2021 at 5:31 AM Marcin Kotarba <sq9onh at gmail.com> wrote:
> Hi,
>
> I was trying to migrate from pulp 3.13.0 to pulp 3.14.2. and Ansible
> playbook fails on running DB migrations with the following error:
>
> TASK [pulp.pulp_installer.pulp_database_config : Run database migrations] **************************************************************************
> fatal: [pulp01]: FAILED! => {
> "changed": true,
> "cmd": [
> "/usr/local/lib/pulp/bin/pulpcore-manager",
> "migrate",
> "--no-input"
> ],
> "delta": "0:00:02.374177",
> "end": "2021-07-15 10:14:56.170246",
> "rc": 1,
> "start": "2021-07-15 10:14:53.796069"}
>
> STDOUT:
>
> Operations to perform:
> Apply all migrations: admin, auth, contenttypes, core, file, guardian, sessions
> Running migrations:
> Applying file.0012_delete_filefilesystemexporter...
>
>
> STDERR:
>
> Traceback (most recent call last):
> File "/usr/local/lib/pulp/lib64/python3.6/site-packages/django/db/backends/base/base.py", line 240, in _commit
> return self.connection.commit()
> psycopg2.errors.InternalError_: could not find trigger 17726
>
>
> The above exception was the direct cause of the following exception:
>
> Traceback (most recent call last):
> File "/usr/local/lib/pulp/bin/pulpcore-manager", line 8, in <module>
> sys.exit(manage())
> File "/usr/local/lib/pulp/lib64/python3.6/site-packages/pulpcore/app/manage.py", line 11, in manage
> execute_from_command_line(sys.argv)
> File "/usr/local/lib/pulp/lib64/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
> utility.execute()
> File "/usr/local/lib/pulp/lib64/python3.6/site-packages/django/core/management/__init__.py", line 375, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
> File "/usr/local/lib/pulp/lib64/python3.6/site-packages/django/core/management/base.py", line 323, in run_from_argv
> self.execute(*args, **cmd_options)
> File "/usr/local/lib/pulp/lib64/python3.6/site-packages/django/core/management/base.py", line 364, in execute
> output = self.handle(*args, **options)
> File "/usr/local/lib/pulp/lib64/python3.6/site-packages/django/core/management/base.py", line 83, in wrapped
> res = handle_func(*args, **kwargs)
> File "/usr/local/lib/pulp/lib64/python3.6/site-packages/django/core/management/commands/migrate.py", line 234, in handle
> fake_initial=fake_initial,
> File "/usr/local/lib/pulp/lib64/python3.6/site-packages/django/db/migrations/executor.py", line 117, in migrate
> state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
> File "/usr/local/lib/pulp/lib64/python3.6/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
> state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
> File "/usr/local/lib/pulp/lib64/python3.6/site-packages/django/db/migrations/executor.py", line 247, in apply_migration
> migration_recorded = True
> File "/usr/local/lib/pulp/lib64/python3.6/site-packages/django/db/backends/base/schema.py", line 112, in __exit__
> self.atomic.__exit__(exc_type, exc_value, traceback)
> File "/usr/local/lib/pulp/lib64/python3.6/site-packages/django/db/transaction.py", line 240, in __exit__
> connection.commit()
> File "/usr/local/lib/pulp/lib64/python3.6/site-packages/django/db/backends/base/base.py", line 262, in commit
> self._commit()
> File "/usr/local/lib/pulp/lib64/python3.6/site-packages/django/db/backends/base/base.py", line 240, in _commit
> return self.connection.commit()
> File "/usr/local/lib/pulp/lib64/python3.6/site-packages/django/db/utils.py", line 89, in __exit__
> raise dj_exc_value.with_traceback(traceback) from exc_value
> File "/usr/local/lib/pulp/lib64/python3.6/site-packages/django/db/backends/base/base.py", line 240, in _commit
> return self.connection.commit()
> django.db.utils.InternalError: could not find trigger 17726
>
>
> MSG:
>
> non-zero return code
>
>
> I checked and services are up and running. Is it something that can be
> ignored or do I have to perform any manual steps to make it work?
>
> Any help will be appreciated.
>
> Best regards,
> Marcin
>
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://listman.redhat.com/mailman/listinfo/pulp-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20210716/958f3fa6/attachment.htm>
More information about the Pulp-list
mailing list