Open benapetr opened 4 years ago
@benapetr,
Interesting. This doesn't look like a failure to run migrations, it looks like awx-manage createsuperuser
and awx-manage create_preload_data
are running (when they don't need to).
This could be a bug in the installer? Given the warnings above, though, if your install is working, it's probably harmless.
I also noted that after upgrade there was massive SQL traffic, about 200MB/s writes to disks caused by some massive inserts and deletes, which kept lasting until I killed the VM. SQL storage grew by few GB.
We recently added code that auto-migrates certain tables to use a bigint
as their primary key, and this happens automatically on upgrade, so I expect this is what you were seeing:
https://github.com/ansible/awx/issues/6010 https://github.com/ansible/awx/pull/6032
If you've got a larger dataset (lots of historical job output), it may take awhile post-upgrade for the migration to finish.
I am facing the same issue.
Operations to perform: Apply all migrations: auth, conf, contenttypes, main, oauth2_provider, sessions, sites, social_django, sso, taggit Running migrations: No migrations to apply. Traceback (most recent call last): File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) psycopg2.IntegrityError: duplicate key value violates unique constraint "auth_user_username_key" DETAIL: Key (username)=(admin) already exists.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
Due to this, my AWX instance is not working properly. I can login to AWX web portal but it shows error message as: "Failed to get dashboard: 500 A server error has occurred."
If I scroll down in logs, I see another error as:
2020-09-22 12:33:26,939 ERROR awx.main.tasks Failed to rebuild schedule Cleanup Job Schedule_t1_1_2020-09-27 16:02:38+00:00. Traceback (most recent call last): File "/var/lib/awx/venv/awx/lib64/python3.6/site-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) psycopg2.ProgrammingError: relation "main_channelgroup" does not exist LINE 1: ...oup"."group", "main_channelgroup"."channels" FROM "main_chan...
Any guidance what could be an issue here and how to resolve?
The same issue after awx_task image update
Same issue, anyone manage to solve this?
Howdy, you guys might need to due some version jumping instead, try going from AWX 8 to 9 to 11. etc
I have a huge AWX deployment with version 9 which I managed to upgrade to version 23.2.0 without any issues. It did took me some time to find the right versions to jump to.
ISSUE TYPE
SUMMARY
ENVIRONMENT
STEPS TO REPRODUCE
Install 11.2.0 over 8.0.0 - I don't think this can be easily reproduced
EXPECTED RESULTS
Flawless update
ACTUAL RESULTS
This exception in awx_task container
ADDITIONAL INFORMATION
AWX however did start up and was probably operational to certain degree, I don't know if it was safe to continue with DB which clearly failed to upgrade, so I rolled back the VM snapshot
I would love some feedback on this exception, if it can be ignore or if it's something to fix. I also noted that after upgrade there was massive SQL traffic, about 200MB/s writes to disks caused by some massive inserts and deletes, which kept lasting until I killed the VM. SQL storage grew by few GB.