search

kubernetes-sigs / sig-windows-dev-tools

This is a batteries included local development environment for Kubernetes on Windows.
Apache License 2.0
80 stars 46 forks source link

Calico Felix - L3 routing issue #269

Closed aroradaman closed 8 months ago

aroradaman commented 1 year ago

Calico-felix HPC is currently unable to create route for endpoints

Logs from the calico-felix container (windows node)

2023-04-08 15:03:14.118 [INFO][4092] felix/win_dataplane.go 307: Applying dataplane updates
2023-04-08 15:03:14.118 [INFO][4092] felix/endpoint_mgr.go 162: Refreshing the endpoint cache
2023-04-08 15:03:14.119 [WARNING][4092] felix/l3_route_resolver.go 662: Unable to create route for IP; the node it belongs to was not recorded in IPAM IP=100.244.206.64
2023-04-08 15:03:14.120 [WARNING][4092] felix/l3_route_resolver.go 662: Unable to create route for IP; the node it belongs to was not recorded in IPAM IP=100.244.206.65
2023-04-08 15:03:14.120 [WARNING][4092] felix/l3_route_resolver.go 662: Unable to create route for IP; the node it belongs to was not recorded in IPAM IP=100.244.206.66
2023-04-08 15:03:14.120 [WARNING][4092] felix/l3_route_resolver.go 662: Unable to create route for IP; the node it belongs to was not recorded in IPAM IP=100.244.206.127
2023-04-08 15:03:14.131 [WARNING][4092] felix/endpoint_mgr.go 200: Failed to get attached containers id="96667AD0-93CC-409D-854D-98BD83730594" name="aba9dfc476b7423c1c15ffabb9f165ad0430116c2746e88a85dff998fca3183e_Calico"

https://calicousers.slack.com/archives/CF9M1U9RV/p1681057621255359

k8s-triage-robot commented 10 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 9 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot commented 8 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 8 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/sig-windows-dev-tools/issues/269#issuecomment-2008475348): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.