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

Fix unmarshall of results for interface index 0 #434

Conversation

vikaschoudhary16
Copy link

In the "ips" struct, if the plugin passes interface index as 0 to
cni unmarshalling api, index index gets omitted in the result.

fixes #404

Signed-off-by: vikaschoudhary16 [email protected]

In the "ips" struct, if the plugin passes interface index as 0 to
cni unmarshalling api, index index gets omitted in the result.

fixes containernetworking#404

Signed-off-by: vikaschoudhary16 <[email protected]>
@dcbw
Copy link
Member

dcbw commented Apr 21, 2017

I think this might be a problem for IPAM plugins which use the same structure, but don't pass anything about interface indexes. Their JSON would now include 0 where before it was empty, and their results do not always correspond to any specific interface index.

@vikaschoudhary16
Copy link
Author

@dcbw , IPAM plugins are not supposed to pass anything about interface indexes as per the cni spec. May be i misunderstood your point. Would you mind please reword it again for me?

@squeed
Copy link
Member

squeed commented Apr 24, 2017

@dcbw I thought you were gonna replace that with an *int...

@dcbw
Copy link
Member

dcbw commented Jul 5, 2017

CLosing in favor of containernetworking/plugins#28

@dcbw dcbw closed this Jul 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CNI result ips[].interface is omitted when set to 0
3 participants