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 #3114

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

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

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

Comments

@Rajesh-Gurjar
Copy link

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 Tigera version?
The Tigera pod is running and working as expected, no logs are there related to this error.

@hjiawei
Copy link
Contributor

hjiawei commented Jan 16, 2024

Hi @Rajesh-Gurjar, during the calico/node container build, we have a step to create a libpcap.so.0.8 symbolic link inside the container to address the issue you are seeing. It can also be found from our calico/node image layer.

If you run the following command, it will report node version which suggested that shared libraries are correctly resolved and loaded.

$ docker run --rm --entrypoint=/usr/bin/calico-node calico/node:v3.27.0 -v
... (pulling the image)
v3.27.0

Can you find which calico/node image is deployed in your cluster? You can find the image info from calico-node deamoeset under the calico-system namespace. You can also replace calico/node:v3.27.0 from the above command and try to reproduce the error you are seeing.

@hjiawei
Copy link
Contributor

hjiawei commented Jan 16, 2024

It is for RHEL 8
...
In the working version libpcap.so.1.9.1 is installed.

I assume these are your host setup that runs the k8s cluster? I don't think calico/node pod requires dependency from the host. Dependencies are self-contained within the image.

@Rajesh-Gurjar
Copy link
Author

Hi @hjiawei I'll try this and get back.

@clayvan
Copy link

clayvan commented Feb 7, 2024

I'm trying to use Tigera v1.33.0 and can confirm the same.

If it's helpful information, I'm actually trying to use the Ironbank builds of tigera and calico
https://repo1.dso.mil/dsop/opensource/calico/node/-/blob/development/Dockerfile?ref_type=heads

@Rajesh-Gurjar
Copy link
Author

Hi @hjiawei It worked after creating the symlink. Thanks for help. This can be closed.

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

3 participants