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.

Sign up for GitHub

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

Jump to bottom

If a node is holding EgressIP(s), the reported node IP might not be correct #27

Open
AmrGanz opened this issue Dec 9, 2020 · 2 comments
Open

If a node is holding EgressIP(s), the reported node IP might not be correct #27

AmrGanz opened this issue Dec 9, 2020 · 2 comments
Assignees
@kxr

Comments

@AmrGanz
Copy link

AmrGanz commented Dec 9, 2020

Hello Khizer,

I saw that if a node is servicing EgressIP(s), it will show u as Internal and External IPs in the YAML and JSON definition of the node.

This will "sometimes" get the wrong IP when issuing "# omg get nodes -o wide" command.
@kxr kxr self-assigned this Dec 10, 2020
@kxr
Copy link
Owner

kxr commented Dec 10, 2020

@AmrGanz Thank you for reporting this. I will have a look. If you can PM me the specific case where this is happening, that would be helpful :)

@AmrGanz
Copy link
Author

AmrGanz commented Dec 10, 2020

Sure thing. Doing it now .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kxr kxr

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kxr @AmrGanz