projectcalico / projectcalico/vpp-dataplane

WatchDog timed out waiting for config from felix. Exiting...

Open
#701 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
172
Forks
47
Avg merge
4d 23h
Merged PRs (30d)
3

Description

Environment

  • OS: CentOS7 with Linux 3.10.0-1160.119.1.el7.x86_64 kernel
  • Calico/VPP version: 3.26.0
  • Kubernetes version: 1.26.2
  • Deployment type: VM
  • Network configuration: Calico3.26.4

Issue description
After deploying Calico successfully, I attempted to run Calico-VPP. However, the VPP container frequently restarts on its own. Below are some infomations:
kubectl get po -A
image

kubectl describe po -n calico-vpp-dataplane calico-vpp-node-9vvdv
image

kubectl logs -n calico-vpp-dataplane calico-vpp-node-9vvdv -c agent
image

It seems that the file for felixconfig provided by Calico Node is missing, but I am unsure how to obtain this file.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the attached kubectl describe output and agent logs for calico-vpp-node-9vvdv, then compare the reported deployment versions and environment. No source file or test is named; done means identifying why the felix configuration is unavailable and why the VPP container restarts, with evidence from a reproducible deployment or logs.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes, linux
Domain
devops, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.