Open phemmer opened 3 years ago
This might be fixed in the next release of AWX. I'll try to follow up here when it goes live so you can test it out, or you can build your own images from devel.
@shanemcd i suppose the fix hasn't been committed yet.. as building the current version does not provide a fix.. Or if there is a workaround for this it would be more than welcome.. thnxs
Also seeing this error often in the logs:
psycopg2.errors.CheckViolation: no partition of relation "main_projectupdateevent" found for row
The fix seems to have introduced another bug described in https://github.com/ansible/awx/issues/10838, the public schema has been hardcoded..,
hi guys,
Is there a specific way of manually calling this migration script.. or have it run till the end
No errors in operator when upgrading or deploying..
https://github.com/ansible/awx/blob/0f6e221c14ec60fd6e492e583676511e040f469b/awx/main/migrations/0144_event_partitions.py
Each time i try a new upgrade i get the same
File "/var/lib/awx/venv/awx/lib64/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) django.db.utils.IntegrityError: no partition of relation "main_projectupdateevent" found for row DETAIL: Partition key of the failing row contains (job_created) = (2021-10-05 13:02:45.157503+00). During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/var/lib/awx/venv/awx/lib64/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) psycopg2.errors.CheckViolation: no partition of relation "main_projectupdateevent" found for row DETAIL: Partition key of the failing row contains (job_created) = (2021-10-05 13:02:45.157503+00).
migrating from awx 7.1.0 , operator 0.2.0 externaldb
migrating to: 19.4.0 ,operator 0.14.0
The migration occurs but only half way..
unpartitioned* tables are created, though even by manually purging the original tables and renaming the unpartitioned ones, you end up having tables without some columns like job_created.
| django.db.utils.ProgrammingError: column main_projectupdateevent.job_created does not exist | LINE 1: ..._update_id" FROM "main_projectupdateevent" WHERE ("main_proj..
I think this might have been fixed by https://github.com/ansible/awx/pull/11241
Thanks @shanemcd seems like the commit/merge was done after the build 19.4.0> About when could we expect a new build and if so could we make sure that 10838, is included.. Becomes a hustle if you are using an external db. As not good practice to use the public schema..
This is what i was talking about.. unfortunately build went out without it being fixed
I'm seeing this on 20.0.1.
Please confirm the following
Summary
After changing the execution environment of a inventory source, I received the following exception when trying to perform an inventory sync.
AWX version
19.2.2
Installation method
minikube
Modifications
no
Ansible version
2.10.11
Operating system
Debian Buster
Web browser
Chrome
Steps to reproduce
Not sure. The last thing I did prior to this was to change the execution environment on an inventory source.
Expected results
Jobs to run
Actual results
Additional information
No response