Re: [Pulp-list] pulp 3.3 migration error

2020-05-29 Thread Bin Li (BLOOMBERG/ 120 PARK)
Thanks Daniel. We will soon start testing on 3.4.

From: dal...@redhat.com At: 05/29/20 17:18:41To:  Bin Li (BLOOMBERG/ 120 PARK ) 
Cc:  dkli...@redhat.com,  pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.3 migration error

Hello Bin,

Unfortunately it looks like when we fixed the migration from 3.3.0 -> 3.3.1, we 
accidentally broke the migration from 3.2.z -> 3.3.z.  This is my fault since I 
tested the various migration paths for that patch - including migrating from 
3.2.0 - but I must have missed something when doing so.

On Monday we will be releasing Pulp RPM 3.4.0 which should fix the migration 
issues permanently. We're also considering entirely removing the 3.3.z releases 
of the RPM plugin from PyPI to avoid anyone else experiencing this issue going 
forwards, and investigating automated upgrade testing to catch this kind of 
problem earlier.

I apologize for the headache this has probably been, but we really appreciate 
the effort you've put into reporting these issues, it is of tremendous value to 
the project!

Thank you,
Daniel

On Thu, May 28, 2020 at 11:26 PM Bin Li (BLOOMBERG/ 120 PARK) 
 wrote:

Yes, we are trying to upgrade to 3.3.2.

From: dkli...@redhat.com At: 05/28/20 17:13:05To:  Bin Li (BLOOMBERG/ 120 PARK 
) 
Cc:  pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.3 migration error

Are you upgrading to pulp-rpm 3.3.2? 

On Thu, May 28, 2020 at 5:08 PM Bin Li (BLOOMBERG/ 120 PARK) 
 wrote:

Hi All,Getting a new error when migrate from 3.2 to 3.3. Please advise if this 
can be fixed manually.

TASK [pulp_database : Run database migrations] 

fatal: [pulpp-ob-581]: FAILED! => {"changed": true, "cmd": 
["/opt/utils/venv/pulp/3.7.3/bin/django-admin", "migrate", "--no-input"], 
"delta": "0:00:01.768909", "end": "2020-05-28 17:02:22.996242", "msg": 
"non-zero return code", "rc": 1, "start": "2020-05-28 17:02:21.227333", 
"stderr": "Traceback (most recent call last):\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 84, in _execute\nreturn self.cursor.execute(sql, 
params)\npsycopg2.errors.NotNullViolation: column \"last_sync_revision_number\" 
contains null values\n\n\nThe above exception was the direct cause of the 
following exception:\n\nTraceback (most recent call last):\n  File 
\"/opt/utils/venv/pulp/3.7.3/bin/django-admin\", line 8, in \n
sys.exit(execute_from_command_line())\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
 line 381, in execute_from_command_line\nutility.execute()\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
 line 375, in execute\n
self.fetch_command(subcommand).run_from_argv(self.argv)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
 line 323, in run_from_argv\nself.execute(*args, **cmd_options)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
 line 364, in execute\noutput = self.handle(*args, **options)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
 line 83, in wrapped\nres = handle_func(*args, **kwargs)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/commands/migrate.py\",
 line 234, in handle\nfake_initial=fake_initial,\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
 line 117, in migrate\nstate = self._migrate_all_forwards(state, plan, 
full_plan, fake=fake, fake_initial=fake_initial)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
 line 147, in _migrate_all_forwards\nstate = self.apply_migration(state, 
migration, fake=fake, fake_initial=fake_initial)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
 line 245, in apply_migration\nstate = migration.apply(state, 
schema_editor)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/migration.py\",
 line 124, in apply\noperation.database_forwards(self.app_label, 
schema_editor, old_state, project_state)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/operations/fields.py\",
 line 112, in database_forwards\nfield,\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/sche

Re: [Pulp-list] pulp 3.3 migration error

2020-05-29 Thread Daniel Alley
Hello Bin,

Unfortunately it looks like when we fixed the migration from 3.3.0 ->
3.3.1, we accidentally broke the migration from 3.2.z -> 3.3.z.  This is my
fault since I tested the various migration paths for that patch - including
migrating from 3.2.0 - but I must have missed something when doing so.

On Monday we will be releasing Pulp RPM 3.4.0 which should fix the
migration issues permanently. We're also considering entirely removing the
3.3.z releases of the RPM plugin from PyPI to avoid anyone else
experiencing this issue going forwards, and investigating automated upgrade
testing to catch this kind of problem earlier.

I apologize for the headache this has probably been, but we really
appreciate the effort you've put into reporting these issues, it is of
tremendous value to the project!

Thank you,
Daniel

On Thu, May 28, 2020 at 11:26 PM Bin Li (BLOOMBERG/ 120 PARK) <
bli...@bloomberg.net> wrote:

> Yes, we are trying to upgrade to 3.3.2.
>
> From: dkli...@redhat.com At: 05/28/20 17:13:05
> To: Bin Li (BLOOMBERG/ 120 PARK ) 
> Cc: pulp-list@redhat.com
> Subject: Re: [Pulp-list] pulp 3.3 migration error
>
> Are you upgrading to pulp-rpm 3.3.2?
>
> On Thu, May 28, 2020 at 5:08 PM Bin Li (BLOOMBERG/ 120 PARK) <
> bli...@bloomberg.net> wrote:
>
>> Hi All,
>> Getting a new error when migrate from 3.2 to 3.3. Please advise if this
>> can be fixed manually.
>>
>> TASK [pulp_database : Run database migrations]
>> 
>> fatal: [pulpp-ob-581]: FAILED! => {"changed": true, "cmd":
>> ["/opt/utils/venv/pulp/3.7.3/bin/django-admin", "migrate", "--no-input"],
>> "delta": "0:00:01.768909", "end": "2020-05-28 17:02:22.996242", "msg":
>> "non-zero return code", "rc": 1, "start": "2020-05-28 17:02:21.227333",
>> "stderr": "Traceback (most recent call last):\n File
>> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
>> line 84, in _execute\n return self.cursor.execute(sql,
>> params)\npsycopg2.errors.NotNullViolation: column
>> \"last_sync_revision_number\" contains null values\n\n\nThe above exception
>> was the direct cause of the following exception:\n\nTraceback (most recent
>> call last):\n File \"/opt/utils/venv/pulp/3.7.3/bin/django-admin\", line 8,
>> in \n sys.exit(execute_from_command_line())\n File
>> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
>> line 381, in execute_from_command_line\n utility.execute()\n File
>> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
>> line 375, in execute\n
>> self.fetch_command(subcommand).run_from_argv(self.argv)\n File
>> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
>> line 323, in run_from_argv\n self.execute(*args, **cmd_options)\n File
>> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
>> line 364, in execute\n output = self.handle(*args, **options)\n File
>> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
>> line 83, in wrapped\n res = handle_func(*args, **kwargs)\n File
>> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/commands/migrate.py\",
>> line 234, in handle\n fake_initial=fake_initial,\n File
>> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
>> line 117, in migrate\n state = self._migrate_all_forwards(state, plan,
>> full_plan, fake=fake, fake_initial=fake_initial)\n File
>> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
>> line 147, in _migrate_all_forwards\n state = self.apply_migration(state,
>> migration, fake=fake, fake_initial=fake_initial)\n File
>> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
>> line 245, in apply_migration\n state = migration.apply(state,
>> schema_editor)\n File
>> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/migration.py\",
>> line 124, in apply\n operation.database_forwards(self.app_label,
>> schema_editor, old_state, project_state)\n File
>> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migra

Re: [Pulp-list] pulp 3.3 migration error

2020-05-28 Thread Bin Li (BLOOMBERG/ 120 PARK)
Yes, we are trying to upgrade to 3.3.2.

From: dkli...@redhat.com At: 05/28/20 17:13:05To:  Bin Li (BLOOMBERG/ 120 PARK 
) 
Cc:  pulp-list@redhat.com
Subject: Re: [Pulp-list] pulp 3.3 migration error

Are you upgrading to pulp-rpm 3.3.2? 

On Thu, May 28, 2020 at 5:08 PM Bin Li (BLOOMBERG/ 120 PARK) 
 wrote:

Hi All,Getting a new error when migrate from 3.2 to 3.3. Please advise if this 
can be fixed manually.

TASK [pulp_database : Run database migrations] 

fatal: [pulpp-ob-581]: FAILED! => {"changed": true, "cmd": 
["/opt/utils/venv/pulp/3.7.3/bin/django-admin", "migrate", "--no-input"], 
"delta": "0:00:01.768909", "end": "2020-05-28 17:02:22.996242", "msg": 
"non-zero return code", "rc": 1, "start": "2020-05-28 17:02:21.227333", 
"stderr": "Traceback (most recent call last):\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 84, in _execute\nreturn self.cursor.execute(sql, 
params)\npsycopg2.errors.NotNullViolation: column \"last_sync_revision_number\" 
contains null values\n\n\nThe above exception was the direct cause of the 
following exception:\n\nTraceback (most recent call last):\n  File 
\"/opt/utils/venv/pulp/3.7.3/bin/django-admin\", line 8, in \n
sys.exit(execute_from_command_line())\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
 line 381, in execute_from_command_line\nutility.execute()\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
 line 375, in execute\n
self.fetch_command(subcommand).run_from_argv(self.argv)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
 line 323, in run_from_argv\nself.execute(*args, **cmd_options)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
 line 364, in execute\noutput = self.handle(*args, **options)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
 line 83, in wrapped\nres = handle_func(*args, **kwargs)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/commands/migrate.py\",
 line 234, in handle\nfake_initial=fake_initial,\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
 line 117, in migrate\nstate = self._migrate_all_forwards(state, plan, 
full_plan, fake=fake, fake_initial=fake_initial)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
 line 147, in _migrate_all_forwards\nstate = self.apply_migration(state, 
migration, fake=fake, fake_initial=fake_initial)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
 line 245, in apply_migration\nstate = migration.apply(state, 
schema_editor)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/migration.py\",
 line 124, in apply\noperation.database_forwards(self.app_label, 
schema_editor, old_state, project_state)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/operations/fields.py\",
 line 112, in database_forwards\nfield,\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py\",
 line 447, in add_field\nself.execute(sql, params)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py\",
 line 137, in execute\ncursor.execute(sql, params)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 67, in execute\nreturn self._execute_with_wrappers(sql, params, 
many=False, executor=self._execute)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 76, in _execute_with_wrappers\nreturn executor(sql, params, many, 
context)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 84, in _execute\nreturn self.cursor.execute(sql, params)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/utils.py\",
 line 89, in __exit__\nraise dj_exc_value.with_traceback(traceback) from 
exc_value\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 84, in _ex

Re: [Pulp-list] pulp 3.3 migration error

2020-05-28 Thread Dennis Kliban
Are you upgrading to pulp-rpm 3.3.2?

On Thu, May 28, 2020 at 5:08 PM Bin Li (BLOOMBERG/ 120 PARK) <
bli...@bloomberg.net> wrote:

> Hi All,
> Getting a new error when migrate from 3.2 to 3.3. Please advise if this
> can be fixed manually.
>
> TASK [pulp_database : Run database migrations]
> 
> fatal: [pulpp-ob-581]: FAILED! => {"changed": true, "cmd":
> ["/opt/utils/venv/pulp/3.7.3/bin/django-admin", "migrate", "--no-input"],
> "delta": "0:00:01.768909", "end": "2020-05-28 17:02:22.996242", "msg":
> "non-zero return code", "rc": 1, "start": "2020-05-28 17:02:21.227333",
> "stderr": "Traceback (most recent call last):\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
> line 84, in _execute\n return self.cursor.execute(sql,
> params)\npsycopg2.errors.NotNullViolation: column
> \"last_sync_revision_number\" contains null values\n\n\nThe above exception
> was the direct cause of the following exception:\n\nTraceback (most recent
> call last):\n File \"/opt/utils/venv/pulp/3.7.3/bin/django-admin\", line 8,
> in \n sys.exit(execute_from_command_line())\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
> line 381, in execute_from_command_line\n utility.execute()\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
> line 375, in execute\n
> self.fetch_command(subcommand).run_from_argv(self.argv)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
> line 323, in run_from_argv\n self.execute(*args, **cmd_options)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
> line 364, in execute\n output = self.handle(*args, **options)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
> line 83, in wrapped\n res = handle_func(*args, **kwargs)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/commands/migrate.py\",
> line 234, in handle\n fake_initial=fake_initial,\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
> line 117, in migrate\n state = self._migrate_all_forwards(state, plan,
> full_plan, fake=fake, fake_initial=fake_initial)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
> line 147, in _migrate_all_forwards\n state = self.apply_migration(state,
> migration, fake=fake, fake_initial=fake_initial)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
> line 245, in apply_migration\n state = migration.apply(state,
> schema_editor)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/migration.py\",
> line 124, in apply\n operation.database_forwards(self.app_label,
> schema_editor, old_state, project_state)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/operations/fields.py\",
> line 112, in database_forwards\n field,\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py\",
> line 447, in add_field\n self.execute(sql, params)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py\",
> line 137, in execute\n cursor.execute(sql, params)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
> line 67, in execute\n return self._execute_with_wrappers(sql, params,
> many=False, executor=self._execute)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
> line 76, in _execute_with_wrappers\n return executor(sql, params, many,
> context)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
> line 84, in _execute\n return self.cursor.execute(sql, params)\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/utils.py\",
> line 89, in __exit__\n raise dj_exc_value.with_traceback(traceback) from
> exc_value\n File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
> line 84, in _execute\n return self.cursor.execute(sql,
> params)\ndjango.db.utils.IntegrityError: column
> \"last_sync_revision_number\" contains null values", "stderr_lines":
> ["Traceback (most recent call last):", " File
> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
> line 84, in _execute", " return self.cursor.execute(sql, params)",
> "psycopg2.errors.NotNullViolation: column \"last_sync_revision_number\"
> contains null values", "", "", "The above exception was the direct cause of
> the following exception:", "", "Traceback (most

[Pulp-list] pulp 3.3 migration error

2020-05-28 Thread Bin Li (BLOOMBERG/ 120 PARK)
Hi All,Getting a new error when migrate from 3.2 to 3.3. Please advise if this 
can be fixed manually.

TASK [pulp_database : Run database migrations] 

fatal: [pulpp-ob-581]: FAILED! => {"changed": true, "cmd": 
["/opt/utils/venv/pulp/3.7.3/bin/django-admin", "migrate", "--no-input"], 
"delta": "0:00:01.768909", "end": "2020-05-28 17:02:22.996242", "msg": 
"non-zero return code", "rc": 1, "start": "2020-05-28 17:02:21.227333", 
"stderr": "Traceback (most recent call last):\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 84, in _execute\nreturn self.cursor.execute(sql, 
params)\npsycopg2.errors.NotNullViolation: column \"last_sync_revision_number\" 
contains null values\n\n\nThe above exception was the direct cause of the 
following exception:\n\nTraceback (most recent call last):\n  File 
\"/opt/utils/venv/pulp/3.7.3/bin/django-admin\", line 8, in \n
sys.exit(execute_from_command_line())\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
 line 381, in execute_from_command_line\nutility.execute()\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/__init__.py\",
 line 375, in execute\n
self.fetch_command(subcommand).run_from_argv(self.argv)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
 line 323, in run_from_argv\nself.execute(*args, **cmd_options)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
 line 364, in execute\noutput = self.handle(*args, **options)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/base.py\",
 line 83, in wrapped\nres = handle_func(*args, **kwargs)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/core/management/commands/migrate.py\",
 line 234, in handle\nfake_initial=fake_initial,\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
 line 117, in migrate\nstate = self._migrate_all_forwards(state, plan, 
full_plan, fake=fake, fake_initial=fake_initial)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
 line 147, in _migrate_all_forwards\nstate = self.apply_migration(state, 
migration, fake=fake, fake_initial=fake_initial)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/executor.py\",
 line 245, in apply_migration\nstate = migration.apply(state, 
schema_editor)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/migration.py\",
 line 124, in apply\noperation.database_forwards(self.app_label, 
schema_editor, old_state, project_state)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/migrations/operations/fields.py\",
 line 112, in database_forwards\nfield,\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py\",
 line 447, in add_field\nself.execute(sql, params)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/base/schema.py\",
 line 137, in execute\ncursor.execute(sql, params)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 67, in execute\nreturn self._execute_with_wrappers(sql, params, 
many=False, executor=self._execute)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 76, in _execute_with_wrappers\nreturn executor(sql, params, many, 
context)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 84, in _execute\nreturn self.cursor.execute(sql, params)\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/utils.py\",
 line 89, in __exit__\nraise dj_exc_value.with_traceback(traceback) from 
exc_value\n  File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 84, in _execute\nreturn self.cursor.execute(sql, 
params)\ndjango.db.utils.IntegrityError: column \"last_sync_revision_number\" 
contains null values", "stderr_lines": ["Traceback (most recent call last):", " 
 File 
\"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/django/db/backends/utils.py\",
 line 84, in _execute", "return self.cursor.execute(sql, params)", 
"psycopg2.errors.NotNullViolation: column \"last_sync_revision_number\" 
contains null values", "", "", "The above exception was the direct cause of the 
following exception:", "", "Traceback (most recent call last):", "  File 
\"/opt/utils/venv/pulp/3.7.3/bin/django-admin\", line 8, in ", "
sys.exit(execute_from_