You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've tracked down the bug to a bcc bug (in combination with llvm).
Upgrading the pixie BCC fork to include the changes through 0.30.0 results in a functional socket tracer. This also requires upgrading libbpf since we specify libbpf's version separately in our bazel configuration.
Summary: Upgrade bcc and libbpf to fix Google COS socket tracer issues
See GitHub issue comments below for more details. This pulls in the
following BCC fix
(iovisor/bcc@57ca51b).
Relevant Issues: Closes#1900, part of #1905
Type of change: /kind bug
Test Plan: Skaffold'ed this change to a Ubuntu and Google COS cluster
and verified socket tracer works again
- [x] Verified that all kernel build passes
- [x] Verified that all kernel build used a bcc repo reference that
matches latest commit
```
ddelnano@noble-dev:~/code/bcc/build (pixie8) $ git diff pixie/pixie8 ddelnano/pixie8
ddelnano@noble-dev:~/code/bcc/build (pixie8) $
```
Changelog Message: Fix issue with socket tracer on recent Google COS
instances
---------
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Running Pixie on a recent (v109) COS GKE cluster results in a failed socket tracer.
To Reproduce
px deploy
pem logs
Expected behavior
Pixie's socket tracer should work with latest COS instances.
App information (please complete the following information):
The text was updated successfully, but these errors were encountered: