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

[BUG] Node import failed with distributed server in Core Xml! #870

Open
jhonzy0928 opened this issue May 29, 2024 · 0 comments
Open

[BUG] Node import failed with distributed server in Core Xml! #870

jhonzy0928 opened this issue May 29, 2024 · 0 comments
Labels

Comments

@jhonzy0928
Copy link

Describe the bug
I was trying to deploy the distributed node, and when I had the distributed service deployed, I tried to save the XML file, but when I re-opened the Xml file a second time, the assigned server on the node disappeared and became a normal node. This causes me to need to reassign servers to nodes, which is annoying if the number of nodes grows.
To Reproduce
Steps to reproduce the behavior:

  1. Deploy distributed scenarios
  2. Assign a slave server to a node
  3. Run, and then save the file after running successfully
  4. After the file is imported again, the distributed node becomes a common node

Expected behavior
In the Xml file, the node has the server: field, and the server to which the file node is assigned should not change

Screenshots
f8d291401b273ea91b218097ea157a0
918e021d2be0d6cba95c5799a09acf2

Desktop (please complete the following information):

  • OS: [e.g. Ubuntu 22.04]
  • CORE Version [e.g. 9.0.3]
  • EMANE Version [e.g. 1.5.1]

Additional context
I would appreciate it if you could solve my problem。

@jhonzy0928 jhonzy0928 added the bug label May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant