awx-operator
awx-operator copied to clipboard
Operator 0.19.0 throwing "relation "conf_setting" does not exist at character 158" on new install
ISSUE TYPE
- Bug Report
SUMMARY
A freshly launched awx object with operator 0.19.0 still
ENVIRONMENT
- AWX version: (unknown, default for operator 0.19.0)
- Operator version: 0.19.0
- Kubernetes version: 1.21.5
- AWX install method: kustomize to AWS EKS
STEPS TO REPRODUCE
Setup new AWS EKS cluster. Deploy AWX operator (0.19.0) using instructions in README. Deploy an awx object using same instructions. Check logs of postgresql and see that it is carping about relation not existing. Delete postgresql pod, and after it restarts awx web/task/ee pods will start working
EXPECTED RESULTS
A clean and current awx operator install should not have any initial error state that requires deleting a database pod manually, but if it can't be fixed then it should be documented.
ACTUAL RESULTS
New awx deploy was unreachable until postgresql pod was deleted to restart
ADDITIONAL INFORMATION
2022-03-30 05:52:13.812 UTC [117] STATEMENT: SELECT "conf_setting"."id", "conf_setting"."created", "conf_setting"."modified", "conf_setting"."key", "conf_setting"."value", "conf_setting"."user_id" FROM "conf_setting" WHERE ("conf_setting"."key" = 'OAUTH2_PROVIDER' AND "conf_setting"."user_id" IS NULL) ORDER BY "conf_setting"."id" ASC LIMIT 1
2022-03-30 05:52:13.813 UTC [117] ERROR: relation "conf_setting" does not exist at character 158
[wait-for-migrations] Attempt 9 of 30
[wait-for-migrations] Waiting 30 seconds before next attempt
DEBUG 2022/03/30 05:54:04 Sending service advertisement: &{awx-poc-787f4978f-xh7r2 control 2022-03-30 05:54:04.761636387 +0000 UTC m=+125.363569215 1 map[type:Control Service] [{local false} {kubernetes-runtime-auth false} {kubernetes-incluster-auth false}]}
AWX-OPERATOR LOGS
These logs are about 1400 lines long, please indicate if a gist should be created
I'm seeing the same issue with 0.20.0
Getting same messages until migration complete. It takes about 5 minutes in my environment.
I experienced same, v 0.21.0. @shanemcd your team need to check this error, this is fresh installation.
We're also seeing this on a fresh install (v0.21.0) in our environment. For us, deleting the postgres pod does not fix. This completely breaks awx with no work around.