Skip to content

Conversation

@rejain456
Copy link
Contributor

…in l1vh node

Reason for Change:

Currently when npm lite is enabled and running on an l1vh node, in the npm daemon set logs we see a log stating "ignoring pod update since there is no corresponding endpoints". The endpoints of the pods do exist in the HNS network itself; however, the logs are not able to find them.

Issue Fixed:

The state of the endpoints in HNS network in L1VH node is 2 which corresponds to state "hcnEndpointStateAttached". In the original windows NPM setup, the state of the endpoints in non-L1VH nodes is 3 which corresponds to state "hcnEndpointStateAttachedSharing". This pr adds a statement which checks if npm lite is enabled and running on L1VH node and if so, the endpoints are filter based on "hcnEndpointStateAttached" rather than "hcnEndpointStateAttachedSharing".

Requirements:

Notes:

@github-actions
Copy link

This pull request is stale because it has been open for 2 weeks with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale due to inactivity. label Oct 26, 2024
@github-actions
Copy link

github-actions bot commented Nov 2, 2024

Pull request closed due to inactivity.

@github-actions github-actions bot closed this Nov 2, 2024
@github-actions github-actions bot deleted the jainriya/l1VhEndpointFixNpmLite branch November 2, 2024 00:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stale Stale due to inactivity.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants