You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
KUBE Information
kubectl version
Client Version: v1.29.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.27.12+vmware.1
Error Log Snippet
TASK [Get the postgres pod information] ****************************************
task path: /opt/ansible/roles/postgres/tasks/create_managed_postgres.yml:21
{"level":"info","ts":1719495681.4041488,"logger":"logging_event_handler","msg":"[playbook task start]","name":"eda","namespace":"eda","gvk":"eda.ansible.com/v1alpha1, Kind=EDA","event_type":"playbook_on_task_start","job":"3076361852053160124","EventData.Name":"Get the postgres pod information"}
{"level":"info","ts":1719495683.3174007,"logger":"proxy","msg":"cache miss: /v1, Kind=PodList err-Index with name field:status.phase does not exist"}
TASK [postgres : Wait for Database to initialize if managed DB] ****************
task path: /opt/ansible/roles/postgres/tasks/create_managed_postgres.yml:31
{"level":"info","ts":1719495683.5076895,"logger":"logging_event_handler","msg":"[playbook task start]","name":"eda","namespace":"eda","gvk":"eda.ansible.com/v1alpha1, Kind=EDA","event_type":"playbook_on_task_start","job":"3076361852053160124","EventData.Name":"postgres : Wait for Database to initialize if managed DB"}
{"level":"info","ts":1719495685.1001055,"logger":"proxy","msg":"cache miss: /v1, Kind=PodList err-Index with name field:status.phase does not exist"}
Looks like we have what its looking for
kubectl get pods -n eda --field-selector status.phase=Running
NAME READY STATUS RESTARTS AGE
eda-operator-controller-manager-55d6fbf6dc-r6zkn 2/2 Running 0 10m
eda-postgres-0 1/1 Running 0 11h
eda-redis-5bc54f4b6d-rt5sd 1/1 Running 0 11h
I did notice in the play, the task is labeled
"Wait for Database to initialize if managed DB"
We are using an unmanaged DB, so I would expect that to skip
The text was updated successfully, but these errors were encountered:
Error that field:status.phase does not exist
KUBE Information
kubectl version
Client Version: v1.29.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.27.12+vmware.1
Error Log Snippet
TASK [Get the postgres pod information] ****************************************
task path: /opt/ansible/roles/postgres/tasks/create_managed_postgres.yml:21
{"level":"info","ts":1719495681.4041488,"logger":"logging_event_handler","msg":"[playbook task start]","name":"eda","namespace":"eda","gvk":"eda.ansible.com/v1alpha1, Kind=EDA","event_type":"playbook_on_task_start","job":"3076361852053160124","EventData.Name":"Get the postgres pod information"}
{"level":"info","ts":1719495683.3174007,"logger":"proxy","msg":"cache miss: /v1, Kind=PodList err-Index with name field:status.phase does not exist"}
--------------------------- Ansible Task StdOut -------------------------------
TASK [postgres : Wait for Database to initialize if managed DB] ****************
task path: /opt/ansible/roles/postgres/tasks/create_managed_postgres.yml:31
{"level":"info","ts":1719495683.5076895,"logger":"logging_event_handler","msg":"[playbook task start]","name":"eda","namespace":"eda","gvk":"eda.ansible.com/v1alpha1, Kind=EDA","event_type":"playbook_on_task_start","job":"3076361852053160124","EventData.Name":"postgres : Wait for Database to initialize if managed DB"}
{"level":"info","ts":1719495685.1001055,"logger":"proxy","msg":"cache miss: /v1, Kind=PodList err-Index with name field:status.phase does not exist"}
Looks like we have what its looking for
kubectl get pods -n eda --field-selector status.phase=Running
NAME READY STATUS RESTARTS AGE
eda-operator-controller-manager-55d6fbf6dc-r6zkn 2/2 Running 0 10m
eda-postgres-0 1/1 Running 0 11h
eda-redis-5bc54f4b6d-rt5sd 1/1 Running 0 11h
I did notice in the play, the task is labeled
"Wait for Database to initialize if managed DB"
We are using an unmanaged DB, so I would expect that to skip
The text was updated successfully, but these errors were encountered: