ansible / awx-operator

An Ansible AWX operator for Kubernetes built with Operator SDK and Ansible. 🤖
https://www.github.com/ansible/awx
Apache License 2.0
1.27k stars 633 forks source link

Error: Wait for Database to initialize #1966

Open eholderbach opened 2 months ago

eholderbach commented 2 months ago

Please confirm the following

Bug Summary

Description of the Problem: I am attempting to deploy Ansible AWX version 2.19.1 using AWS EKS. However, the database does not initialize correctly and enters a continuous loop, preventing the deployment of AWX web Pod.

AWX Operator version

2.19.1

AWX version

24.6.1

Kubernetes platform

kubernetes

Kubernetes/Platform version

1.3.0

Modifications

no

Steps to reproduce

AWS - EKS 1.3.0 Single node

apiVersion: awx.ansible.com/v1beta1 kind: AWX metadata: name: awx-internal-01 spec: service_type: nodeport no_log: false postgres_init_container_resource_requirements: {} postgres_data_volume_init: true replicas: 2 admin_user: admin ipv6_disabled: true

Expected results

The database should initialize correctly

Actual results

[cloudshell-user@ awx-operator]$ kubectl get pods -o wide --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES awx awx-internal-01-postgres-15-0 0/1 Pending 0 45m awx awx-operator-controller-manager-666ddcf9c5-6bslm 2/2 Running 0 46m 10.10.110.120 ip-10-10-110-253.ca-central-1.compute.internal kube-system aws-node-64p7n 2/2 Running 0 3h44m 10.x ip-10.x.ca-central-1.compute.internal kube-system aws-node-pmzf8 2/2 Running 0 77m 10.x ip-10.x.ca-central-1.compute.internal kube-system coredns-69b46c5f7b-dxvzr 1/1 Running 0 3h44m 10.x ip-10.x.ca-central-1.compute.internal kube-system coredns-69b46c5f7b-nz6t9 1/1 Running 0 3h44m 10.x ip-10.x.ca-central-1.compute.internal kube-system eks-pod-identity-agent-nz9rc 1/1 Running 0 77m 10.x ip-10.x.ca-central-1.compute.internal kube-system eks-pod-identity-agent-rkdf6 1/1 Running 0 3h44m 10.x ip-10.x.ca-central-1.compute.internal kube-system kube-proxy-sg9br 1/1 Running 0 77m 10.x ip-10.x.ca-central-1.compute.internal kube-system kube-proxy-vpd2j 1/1 Running 0 3h44m 10.x ip-10.x.ca-central-1.compute.internal

Additional information

I tried old version like: 2.19.0 and 2.18.0 and same results.

Operator Logs


{"level":"info","ts":"2024-09-26T18:49:06Z","logger":"proxy","msg":"cache miss: /v1, Kind=PodList err-Index with name field:status.phase does not exist"}

--------------------------- Ansible Task StdOut ------------------------------- {"level":"info","ts":"2024-09-26T18:49:06Z","logger":"logging_event_handler","msg":"[playbook task start]","name":"awx-internal-01","namespace":"awx","gvk":"awx.ansible.com/v1beta1, Kind=AWX","event_type":"playbook_on_task_start","job":"1331649654450938395","EventData.Name":"installer : Wait for Database to initialize if managed DB"}

TASK [installer : Wait for Database to initialize if managed DB] *** task path: /opt/ansible/roles/installer/tasks/database_configuration.yml:241

wyattzastrow commented 1 month ago

I'm having a similar problem on a single node k3s install.