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
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
I am experiencing a consistent issue when attempting to associate a Hop-Node under peers for an Execution Node in AWX. The problem occurs when there are 28 Execution Nodes. After adding a 29th instance, it leads to an error in the UI when I attempt to associate a Hop-Node for this object. This seems to be a reproducible bug.
Any help or guidance on resolving this issue would be greatly appreciated. Thank you!
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
No response
Web browser
Chrome, Safari
Steps to reproduce
Set up AWX with 28 Execution Nodes and a Hop-Node (AWXMeshIngress deployed with crd in Kubernetes) .
Add a 29th Execution Node.
Attempt to associate the Hop-Node under peers for the new Execution Node.
Observe the error in the UI.
Expected results
The Hop-Node should be successfully associated under peers for the Execution Node without any errors.
Actual results
An error message appears in the UI, and the association fails. The error message displayed is:
Something went wrong...
There was an error loading this content. TypeError: Cannot read properties of undefined (reading 'hostname')
TypeError: Cannot read properties of undefined (reading 'hostname')
at p (....
Additional information
This issue appears on both Google Chrome and Safari browsers (other browsers not tested). The issue appears to be related to the number of Execution Nodes.
The text was updated successfully, but these errors were encountered:
Please confirm the following
[email protected]
instead.)Bug Summary
I am experiencing a consistent issue when attempting to associate a Hop-Node under peers for an Execution Node in AWX. The problem occurs when there are 28 Execution Nodes. After adding a 29th instance, it leads to an error in the UI when I attempt to associate a Hop-Node for this object. This seems to be a reproducible bug.
Any help or guidance on resolving this issue would be greatly appreciated. Thank you!
AWX version
24.6.1
Select the relevant components
Installation method
kubernetes
Modifications
no
Ansible version
No response
Operating system
No response
Web browser
Chrome, Safari
Steps to reproduce
Expected results
The Hop-Node should be successfully associated under peers for the Execution Node without any errors.
Actual results
An error message appears in the UI, and the association fails. The error message displayed is:
Something went wrong...
There was an error loading this content. TypeError: Cannot read properties of undefined (reading 'hostname')
TypeError: Cannot read properties of undefined (reading 'hostname')
at p (....
Additional information
This issue appears on both Google Chrome and Safari browsers (other browsers not tested). The issue appears to be related to the number of Execution Nodes.
The text was updated successfully, but these errors were encountered: