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

Namespace field is nil in the response for creation of HNS endpoint #1746

Open
rawahars opened this issue Apr 25, 2023 · 0 comments
Open

Namespace field is nil in the response for creation of HNS endpoint #1746

rawahars opened this issue Apr 25, 2023 · 0 comments

Comments

@rawahars
Copy link

Summary

We are using hcsshim to create HNS networks and endpoints. As per the struct HNSEndpoint, we see that there is a placeholder for Namespace and therefore, we were expecting this field to be populated with the relevant details of the endpoint namespace.

However, in the response, we see that this field is nil.

Implementation

hnsEndpoint = &hcsshim.HNSEndpoint{
		Name:               endpointName,
		VirtualNetworkName: nw.Name,
	}

	// Create the HNS endpoint.
	hnsResponse, err := hnsEndpoint.Create()
	if err != nil {
		log.Errorf("Failed to create HNS endpoint: %v.", err)
		return err
	}

Actual behaviour

The above request leads to the HNSResponse as below-

HNS endpoint response: &{
    Id:6E7241C5-B70A-4ECB-AC7E-244B14C82247 
    Name:nat-ep-c1a68e1e-733e-4789-a05e-647d42f73d23 
    VirtualNetwork:04263CD4-8CEA-4D95-BA0E-DF7B60AC4D44 
    VirtualNetworkName:nat 
    Policies:[] 
    MacAddress:00-15-5D-61-13-A1 
    IPAddress:172.17.238.81 
    DNSSuffix:us-west-2.compute.internal 
    DNSServerList:10.0.0.2 
    GatewayAddress:172.17.224.1 
    EnableInternalDNS:false 
    DisableICC:false 
    PrefixLength:20 
    IsRemoteEndpoint:false 
    Namespace:<nil>
}.

Namespace field is nil in the response.

Expected behaviour

We are expecting that the Namespace fields are populated with the relevant details from the HNS Endpoint namespace.

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

No branches or pull requests

1 participant