-
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
null value in column "ip_address" of relation "main_instance" violates not-null constraint #14486
Comments
I have the same issue. |
Same here |
when the task containers come up they should be adding an IP address based on the MY_POD_IP container environment variable Can someone shell into the task container and do a |
also, can folks who are experiencing this let us know _which _ version you are upgrading from and which you are going to? also please provide output of this will help us dig into this |
okay I know the problem now when a conflicting IP address is detected, we set the old one to null instead of "" |
@erik-de-neve workaround If that doesn't work, follow these steps
Now the new pod should be able to come online and provision itself |
Thanks, it worked for me deleting pod |
Please confirm the following
[email protected]
instead.)Bug Summary
AWX upgraded from 22.6.0 to 23.2.0 but awx-task is crashing and restarting after deploy with below error:
As workaround I'm dropping not null column in ip_address for the table main_instance and AWX stop crashing. This is the table data:
AWX version
23.2.0
Select the relevant components
Installation method
kubernetes
Modifications
yes
Ansible version
No response
Operating system
No response
Web browser
Firefox, Chrome, Edge
Steps to reproduce
kustomization.yml
awxsmt-deploy.yml
Stopped awx:
Started awx with new images:
Expected results
Actual results
No workaround:
With workaround:
Additional information
Images are used by local registry with no changes in the images
awx-ee image are updated with below:
requirements.txt
requirements.yml
The text was updated successfully, but these errors were encountered: