Routing Table not distributed to receptors

[Zappelphilipp]

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 [email protected] instead.)

Bug Summary

using the kubernetes operator with default settings

After adding execution nodes to the mesh, they do not appear in the routing tables and therefore cannot be used.

AWX version

24.6.1

Select the relevant components

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

Installation method

kubernetes

Modifications

no

Ansible version

No response

Operating system

Windows 10

Web browser

Firefox / Chrome

Steps to reproduce

1. add hop node as instance to mesh via GUI
2. install hop node with ansible bundle
3. confirm hop node is connected via GUI (it is)
4. add execution node as instance to mesh via GUI
5. install execution node with ansible bundle
6. connect execution node to hop node as peer

Expected results

see execution node show up as connected in gui as well as the routing table of all receptors

Actual results

The execution node never comes online and after checking the hop node as well as the internal control node (inside kubernetes), it seems like the routing table never adds the node:

receptorctl --socket /var/run/receptor/receptor.sock status
Warning: receptorctl and receptor are different versions, they may not be compatible
Node ID: 10.11.23.60
Version: v1.4.8
System CPU Count: 2
System Memory MiB: 1970

Connection                       Cost
awx-22-1-0-task-58f68cd49b-xdnnv 1

Known Node                       Known Connections
10.11.23.60                      awx-22-1-0-task-58f68cd49b-xdnnv: 1
awx-22-1-0-task-58f68cd49b-xdnnv 10.11.23.60: 1

Route                            Via
awx-22-1-0-task-58f68cd49b-xdnnv awx-22-1-0-task-58f68cd49b-xdnnv

Node                             Service   Type       Last Seen             Tags
10.11.23.60                      control   StreamTLS  2024-09-27 13:01:54   {'type': 'Control Service'}
awx-22-1-0-task-58f68cd49b-xdnnv control   Stream     2024-09-27 11:01:14   {'type': 'Control Service'}

Node                             Work Types
awx-22-1-0-task-58f68cd49b-xdnnv local, kubernetes-runtime-auth, kubernetes-incluster-auth

checking with awx-manage list_instances the execution node does show up so it is added and connected as peer configuration wise.

bonus question: Killing the pod containing the control-node does respawn the control node container with a new id, also showing up in the GUI as new control node. Is this configurable somehow so that the id is fixed (and not random like "awx-22-1-0-task-58f68cd49b-5jcf7"?

also is it possible to connect a hop node backwards into the control node and is this the mesh ingress feature? https://ansible.readthedocs.io/projects/awx-operator/en/latest/user-guide/advanced-configuration/mesh-ingress.html

Additional information

No response