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

Calico v3.27.0 not working with Tigera v1.32.3 #8407

Closed
Rajesh-Gurjar opened this issue Jan 12, 2024 · 10 comments
Closed

Calico v3.27.0 not working with Tigera v1.32.3 #8407

Rajesh-Gurjar opened this issue Jan 12, 2024 · 10 comments

Comments

@Rajesh-Gurjar
Copy link

Rajesh-Gurjar commented Jan 12, 2024

Hi,

I'm deploying Tigera v1.32.3 which uses calico v3.27.0 and the pod is unable to start. It is for RHEL 8. k8s version is 1.27.

Expected Behavior

It should work as expected. Tigera v1.30.9 & v1.30.8 is working fine with v3.26.4 & v3.26.3 respectively.

Current Behavior

$ k logs calico-node-9cv7m
Defaulted container "calico-node" out of: calico-node, flexvol-driver (init)
calico-node: error while loading shared libraries: libpcap.so.0.8: cannot open shared object file: No such file or directory
Calico node failed to start

In the working version libpcap.so.1.9.1 is installed. Can you please help why an older lib is requested by newer calico version?
The Tigera pod is running and working as expected, no logs are there related to this error.

@caseydavenport
Copy link
Member

I noticed this line in our Dockerfile, which seems relevant:

# Node is build on a debian image with pcap 1.8, but there is no 1.8 available so we copy 1.9 over. Ideally we should
# should build node on a centos image so we can have correct pcap version alignment.
RUN ln -s $(ls /usr/lib64/libpcap.so.1.9.* | tail -n 1) /usr/lib64/libpcap.so.0.8

From this PR: 4bbda7d

@sridhartigera any thoughts on this one?

@hjiawei
Copy link
Contributor

hjiawei commented Jan 18, 2024

Ref tigera/operator#3114.

@Rajesh-Gurjar
Copy link
Author

It worked after creating the symlink. Thanks for help.

@lou-lan
Copy link
Contributor

lou-lan commented Feb 19, 2024

@caseydavenport I am encounter same issue

$ kubectl logs calico-node-jkmjp -n calico-system
Defaulted container "calico-node" out of: calico-node, flexvol-driver (init), install-cni (init)
calico-node: error while loading shared libraries: libpcap.so.0.8: cannot open shared object file: No such file or directory
Calico node failed to start
dpkg -l | grep libpcap
ii  libpcap0.8:arm64                      1.10.1-4build1                          arm64        system interface for user-level packet capture
image: quay.io/tigera/operator:v1.32.5
docker.io/calico/node:v3.27.2

@hjiawei
Copy link
Contributor

hjiawei commented Feb 20, 2024

Thanks for reporting this issue @lou-lan. I believe these lines in PR #8533 should fix the arm64 calico/node issue. amd64 and the main branch calico/node should not be affected.

@blueberrysnapple
Copy link

Hi @hjiawei I'm on version 3.27.2

But still getting this on arm.

kubectl logs calico-node-nbtln -n calico-system
Defaulted container "calico-node" out of: calico-node, flexvol-driver (init), install-cni (init)
calico-node: error while loading shared libraries: libpcap.so.0.8: cannot open shared object file: No such file or directory
Calico node failed to start
dpkg -l | grep libpcap
ii  libpcap0.8:arm64                         1.10.1-4build1                          arm64        system interface for user-level packet capture
find /usr/ -iname "*libpcap*"
/usr/lib/aarch64-linux-gnu/libpcap.so.0.8
/usr/lib/aarch64-linux-gnu/libpcap.so.1.10.1

@hjiawei
Copy link
Contributor

hjiawei commented Feb 21, 2024

@blueberrysnapple This fix was late for v3.27.2 (was v3.27.1) so please wait for the coming v3.27.3 release.

@hegerdes
Copy link

hegerdes commented Feb 25, 2024

Also faced this issue - rolled back to 3.27.0.

Is there an ETA for v3.27.3?

@marvinlnnx
Copy link

any update for v3.27.3 please ?

@caseydavenport
Copy link
Member

If all goes well v3.27.3 should be out this week 🤞

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants