-
Notifications
You must be signed in to change notification settings - Fork 590
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
CRDs not updated by awx-operator helm deployment #1855
Labels
Comments
@pombaer |
Thank your for clarifying this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please confirm the following
Bug Summary
I tried to upgrade from awx-operator 2.12.2 with postgres-13 to awx-operator 2.16.1 using postgres-15 and received error:
"spec.postgres_init_container_commands"
The postgresql-15 pod logged following error:
"mkdir: cannot create directory '/var/lib/pgsql/data/userdata': Permission denied"
I also tried installing all operator version between 2.12.2 and 2.16.1 to get a working 2.16.1 operator, but always same errors.
After a lot of debugging and searching i realized that the CRDs were always still the old ones and were not updated by newly installed operators and also were not deleted on unistalling the awx-operator using
helm uninstall
.After deleting all CRDs:
and redeploying the helm awx-operator chart everything worked as expected.
I don't know if this is a Bug or this is a normal behavior but it took a lot of time for me to find this issue, so i report it as issue, so please delete if this is a known behavior or if i did something wrong.
AWX Operator version
2.16.1
AWX version
latest
Kubernetes platform
other (please specify in additional information)
Kubernetes/Platform version
rke2 1.26
Modifications
no
Steps to reproduce
Install awx-operator 2.12.2 with helm
Upgrade to 2.26.1 with helm
Expected results
CRD's should be updated on redeployment with helm or should be deleted when running
helm uninstall
Actual results
CRD's are not updated and are always first installed version.
Additional information
No response
Operator Logs
No response
The text was updated successfully, but these errors were encountered: