Description
Downgrading ESM from 4.5.10 or newer down to 4.5.9 or earlier can cause the following error. Also the installer fails not able to communicate with database.
ERROR [installer:74] Exception in run_backward_migrations: Traceback (most recent call last):
File "", line 40, in run_migration_command
File "south_utils\run_migrations.py", line 127, in run_backward_migrations
File "south_utils\run_migrations.py", line 45, in run_migration_command
File "site-packages\django\core\management\__init__.py", line 120, in call_command
File "site-packages\django\core\management\base.py", line 445, in execute
File "site-packages\django\core\management\commands\migrate.py", line 222, in handle
File "site-packages\django\db\migrations\executor.py", line 112, in migrate
File "site-packages\django\db\migrations\executor.py", line 168, in unapply_migration
File "site-packages\django\db\migrations\migration.py", line 162, in unapply
File "site-packages\django\db\migrations\operations\fields.py", line 206, in database_backwards
File "site-packages\django\db\migrations\operations\fields.py", line 201, in database_forwards
File "site-packages\django\db\backends\base\schema.py", line 484, in alter_field
File "site-packages\django\db\backends\postgresql_psycopg2\schema.py", line 113, in _alter_field
File "site-packages\django\db\backends\base\schema.py", line 656, in _alter_field
File "site-packages\django\db\backends\base\schema.py", line 111, in execute
File "site-packages\django\db\backends\utils.py", line 64, in execute
File "site-packages\django\db\utils.py", line 98, in __exit__
File "site-packages\django\db\backends\utils.py", line 64, in execute
OperationalError: cannot ALTER TABLE "organization_enterpriseuser" because it has pending trigger events
<br>
Version Introduced
4.5.10
<br>
Platform
ESM with Postgres 9.2
<br>
Steps to reproduce
- Setup ESM with Postgres 9.2
- Install 4.5.10 or later
- Add a new user to ESM
- Downgrade ESM to 4.5.9 or earlier
<br>
Expected result
Successful downgrade.
<br>
Actual result
Failed downgrade with the error above
<br>
Work Around
- Connect to db
- Set ‘last_login’ for all users in table ‘organization_enterpriseuser’
<br>
Version Fixed
4.5.17