Closed dangoncalves closed 8 months ago
this likely means you have some data in your Settings that is not properly JSON (but may have been allowed on version 21.13.0)
the https:
indicates it is one of your URL related setting. One workaround might be to clear out your Settings in UI (the ones that have https in the values) and then restore them (after making them proper JSON)?
also if you can snapshot and redact your settings, we might be able to point out which one is the culprit
Hello @fosterseth,
Thank you for your help and your insights.
I cleared all my settings in ui and I cannot modify these:
awx setting list | grep -i https
"TOWER_URL_BASE": "https://my.domain.name.com",
"AUTOMATION_ANALYTICS_URL": "https://example.com",
"SOCIAL_AUTH_GOOGLE_OAUTH2_CALLBACK_URL": "https://my.domain.name.com/sso/complete/google-oauth2/",
"SOCIAL_AUTH_GITHUB_CALLBACK_URL": "https://my.domain.name.com/sso/complete/github/",
"SOCIAL_AUTH_GITHUB_ORG_CALLBACK_URL": "https://my.domain.name.com/sso/complete/github-org/",
"SOCIAL_AUTH_GITHUB_TEAM_CALLBACK_URL": "https://my.domain.name.com/sso/complete/github-team/",
"SOCIAL_AUTH_GITHUB_ENTERPRISE_CALLBACK_URL": "https://my.domain.name.com/sso/complete/github-enterprise/",
"SOCIAL_AUTH_GITHUB_ENTERPRISE_ORG_CALLBACK_URL": "https://my.domain.name.com/sso/complete/github-enterprise-org/",
"SOCIAL_AUTH_GITHUB_ENTERPRISE_TEAM_CALLBACK_URL": "https://my.domain.name.com/sso/complete/github-enterprise-team/",
"SOCIAL_AUTH_AZUREAD_OAUTH2_CALLBACK_URL": "https://my.domain.name.com/sso/complete/azuread-oauth2/",
"SOCIAL_AUTH_SAML_CALLBACK_URL": "https://my.domain.name.com/sso/complete/saml/",
"SOCIAL_AUTH_SAML_METADATA_URL": "https://my.domain.name.com/sso/metadata/saml/",
Unfortunately, it does not solve the issue.
Moreover, upgrading to 22.3.0 works while 22.4.0 breaks the upgrade with the migration error.
yeah 22.4.0 is where we switched over to django's built-in JSONField
nothing in those values look strange. In fact those are just the default values. I couldn't replicate the issue on my hand sadly
Hello @fosterseth
Unfortunately I wasn't able to reproduce on my side too. Something should be wrong in the settings but I can't figure out what. Any insight to help me finding the culprit setting?
Finally I was able to figure out what was going wrong. My TOWER_URL_BASE setting were corrupted in database: it were registered without quotes.
Many thanks for your help @fosterseth
Please confirm the following
security@ansible.com
instead.)Bug Summary
I try to upgrade AWX from 21.13.0 to 23.7.0. I upgrade the operator and the AWX versions at the same time. Then my upgrade is stuck at migration process. If I try to run migrations manually from a task pod I get the following error:
AWX version
21.13.0
Select the relevant components
Installation method
kubernetes
Modifications
no
Ansible version
No response
Operating system
No response
Web browser
No response
Steps to reproduce
kubectl exec -it <task_pod> -- bash
awx-manage migrate
Expected results
Migrations executes without any error
Actual results
Migration
conf.0010_change_to_JSONField
raise an exceptionAdditional information
No response