Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to associate Execution Node with Hop Node after adding the 29th instance. "Something went wrong..." #15698

Open
5 of 11 tasks
cselbach opened this issue Dec 11, 2024 · 0 comments

Comments

@cselbach
Copy link

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

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 (....

Bildschirmfoto 2024-12-10 um 18 23 32

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant