-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Comments
I noticed this line in our Dockerfile, which seems relevant: Lines 238 to 240 in 711528e
From this PR: 4bbda7d @sridhartigera any thoughts on this one? |
Ref tigera/operator#3114. |
It worked after creating the symlink. Thanks for help. |
@caseydavenport I am encounter same issue
|
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. |
Hi @hjiawei I'm on version 3.27.2 But still getting this on arm.
|
@blueberrysnapple This fix was late for v3.27.2 (was v3.27.1) so please wait for the coming v3.27.3 release. |
Also faced this issue - rolled back to 3.27.0. Is there an ETA for v3.27.3? |
any update for v3.27.3 please ? |
If all goes well v3.27.3 should be out this week 🤞 |
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
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.
The text was updated successfully, but these errors were encountered: