AWX UI goes unresponsive post reboot

[muskanmittal015]

Please confirm the following

• I agree to follow this project's code of conduct.
• I have checked the current issues for duplicates.
• I understand that AWX is open source software provided for free and that I might not receive a timely response.
• I am NOT reporting a (potential) security vulnerability. (These should be emailed to security@ansible.com instead.)

Bug Summary

We have provisioned one controller node and two execution nodes, one node status keeps switching between ready and unavailable and gives an error message "Another cluster node has determined this instance to be unresponsive " and after this issue when i reboots my controller node, AWX UI is not accessible and provides message your connection is not private.

AWX version

23.6.0

Select the relevant components

• UI
• UI (tech preview)
• API
• Docs
• Collection
• CLI
• Other

Installation method

kubernetes

Modifications

no

Ansible version

2.14.9

Operating system

Red Hat Enterprise Linux release 8.9 (Ootpa)

Web browser

Chrome, Edge

Steps to reproduce

We have provisioned one controller node and two execution nodes, one node status keeps switching between ready and unavailable and gives an error message "Another cluster node has determined this instance to be unresponsive " and after this issue when i reboots my controller node, AWX UI is not accessible and provides message your connection is not private.

Expected results

it should be working

Actual results

AWX UI is not accessible and provides message your connection is not private.

Additional information

No response

[fosterseth]

another similar issue reported here ansible/receptor#934

[fosterseth]

can you provide more details about your setup (how many task pods / web pods), how many execution nodes, are there any hop nodes involved?

how are you "restarting controller node"? just deleting task pods?

[muskanmittal015]

There is one task pod, one web pod and we have two execution nodes created. No hop nodes added on the controller.

Yes by deleting the pods and running the command make deploy.