# Awx operator does not start pods after a patch

**URL:** <https://forum.ansible.com/t/awx-operator-does-not-start-pods-after-a-patch/39887>\
**Category:** Get Help\
**Tags:** kubernetes, awx, ee\
**Created:** [January 28, 2025, 4:20pm UTC](https://forum.ansible.com/t/awx-operator-does-not-start-pods-after-a-patch/39887 "2025-01-28T16:20:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![gstefanoff](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gstefanoff/32/7333_2.png) [@gstefanoff](https://forum.ansible.com/u/gstefanoff)\
**Post date:** [January 28, 2025, 4:20pm UTC](https://forum.ansible.com/t/awx-operator-does-not-start-pods-after-a-patch/39887/1 "2025-01-28T16:20:44Z")

</div>

I ran `k delete -f cr.yaml` then `k apply -f cr.yaml` to force awx operator to see changes I made to ldap secret. This has worked several times already, but this time it didn’t.

pods are stuck in “Stopping container” when I checked the operator’s events.

No pods in the namespace just the controller manager.

```auto
LAST SEEN TYPE REASON OBJECT MESSAGE
9m52s Normal Killing Pod/ansible-task-7f464d9c85-dczbh Stopping container redis
9m52s Normal Killing Pod/ansible-task-7f464d9c85-dczbh Stopping container ansible-rsyslog
9m52s Normal Killing Pod/ansible-task-7f464d9c85-dczbh Stopping container ansible-ee
9m52s Normal Killing Pod/ansible-task-7f464d9c85-dczbh Stopping container ansible-task
9m52s Normal Killing Pod/ansible-web-84d8849bc6-vlgmz Stopping container redis
9m52s Normal Killing Pod/ansible-web-84d8849bc6-vlgmz Stopping container ansible-web
9m52s Normal Killing Pod/ansible-web-84d8849bc6-vlgmz Stopping container ansible-rsyslog
9m51s Normal Killing Pod/ansible-postgres-15-0 Stopping container postgres

```

Last time this happened, I had to destroy the namespace and remove the operator.

Is there better way to fix this issue?

Version:  
[app.kubernetes.io/operator-version=2.19.1](http://app.kubernetes.io/operator-version=2.19.1)

Logs from controller

```auto
{"level":"error","ts":"2025-01-28T16:12:09Z","msg":"Reconciler error","controller":"awx-controller","object":{"name":"ansible","namespace":"awx"},"namespace":"awx","name":"ansible","reconcileID":"ce5816c0-eca1-405f-b72d-6b060d236d2a","error":"event runner on failed","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.16.3/pkg/internal/controller/controller.go:329\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.16.3/pkg/internal/controller/controller.go:266\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/home/runner/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.16.3/pkg/internal/controller/controller.go:227"}

```

It looks like it might be failing to load ldap\_secret

```auto
{"level":"error","ts":"2025-01-28T16:23:12Z","logger":"logging_event_handler","msg":"","name":"ansible","namespace":"awx","gvk":"awx.ansible.com/v1beta1, Kind=AWX","event_type":"runner_on_failed","job":"5067429572178472837","EventData.Task":"Load LDAP CA Certificate Secret content","EventData.TaskArgs":"","EventData.FailedTaskPath":"/opt/ansible/roles/installer/tasks/load_ldap_cacert_secret.yml:10","error":"[playbook task failed]","s

```

What is the proper (working) way of adding ldap certificates? The methods listed in the documentation do not work, operator does not load the certificate to /etc/openldap/certs/

Thanks

---

<div class="post-metadata">

**Author:** ![gstefanoff](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gstefanoff/32/7333_2.png) [@gstefanoff](https://forum.ansible.com/u/gstefanoff)\
**Post date:** [January 28, 2025, 5:26pm UTC](https://forum.ansible.com/t/awx-operator-does-not-start-pods-after-a-patch/39887/2 "2025-01-28T17:26:00Z")

</div>

Issue was the operator was looking for name of a secret that did not exist.  
If one fails to update the CR with the new name of parameter, in my case a secret, this will happen.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\
**Post date:** [February 27, 2025, 5:26pm UTC](https://forum.ansible.com/t/awx-operator-does-not-start-pods-after-a-patch/39887/3 "2025-02-27T17:26:19Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.