-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
awx-migration-24.3.1 failing #15189
Comments
Note the last upgrade to 24.0.0 appeared to run the migration pod with no issues. migration-24.0.0: Also tested a brand new deployment via AWX operator and latest version deploys with no issues. |
is this problem still reproducible in your environment? do you have a backup of your database pre-upgrade? |
I'd expect this message to happen if somehow the unique constraint for the team model's |
Yes it is. I was able to restore from backup and get my instance upgraded to 24.2.0 however it appears even with the version i am on trying to upgrade to 24.3.1 has the same issue. |
Interesting, any ideas on how to resolve? I'm looking at the postgres db and i see the table in question but nothing looks out of the ordinary. Could i manually set the primary_key back to id? Interesting thing is i don't see a unique constraint listed at the bottom of the table output. |
FYI - I "resolved" the issue by following these steps. Probably not the cleanest way but i needed to get my instance up and running with the latest release.
Any thoughts on if this is a terrible idea or if this should be ok? |
I'm almost completely convinced that something messed up the indices of your team table. I think you have a great strategy for the immediate issue. My only concern would be whether the constraints of other tables also got corrupted. Looking into the obvious tools for this, it seems we already have django-extensions installed so https://gist.github.com/AlanCoding/dcd9e67e02423e5524450b8150a4d6d8 So you could run that and cross-reference against mine. If you have other tables which dropped constraints, I wonder if it might still be obvious enough you can compare and see it. |
Please confirm the following
security@ansible.com
instead.)Bug Summary
Hello when upgrading from 24.0.0 to 24.3.1 i am getting the following error in my migration pod.
AWX version
24.3.1
Select the relevant components
Installation method
openshift
Modifications
no
Ansible version
No response
Operating system
No response
Web browser
No response
Steps to reproduce
Perform awx upgrade via operator from 24.0.0 to 24.3.1
Expected results
Migration pod to finish and new version of AWX to be running
Actual results
Migration pod failing
Additional information
No response
The text was updated successfully, but these errors were encountered: