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
Fix Target throws an NRE when querying port name on container with IP and no ports #230
Fix Target throws an NRE when querying port name on container with IP and no ports #230
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to harden the test case a bit
new V1Pod( | ||
spec: new V1PodSpec(new List<V1Container> | ||
{ | ||
new V1Container("akka-cluster-tooling-example", ports:new List<V1ContainerPort> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a second container to this list that doesn't have any ports exposed and that should do it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
new V1Pod( | ||
spec: new V1PodSpec(new List<V1Container> | ||
{ | ||
new V1Container("akka-cluster-tooling-example") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean this one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A pod can have multiple containers - that's the edge case that triggered the error in this case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
…ub.com:Arkatufus/Akka.Management into #223_DISCOVERY_KubernetesApi_NRE_during_lookup
@Arkatufus looks like one of the tests in the suite is racy - binding on the same port concurrently with another test. |
I'll give it another look |
Closes #223