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.

Sign up for GitHub

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

NETOBSERV-601: Added workaround documentation #211

Merged
merged 4 commits into from
Jan 3, 2023
Merged

NETOBSERV-601: Added workaround documentation #211

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
e975b6c
Added instructions to restart the openshift console
OlivierCazade Dec 12, 2022
423ac14
Added known issu reference.
OlivierCazade Dec 12, 2022
f861312
Update FAQ.md
OlivierCazade Dec 19, 2022
3eaa872
Fixing typo
OlivierCazade Dec 19, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 20 additions & 2 deletions FAQ.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -138,18 +138,36 @@ kubectl get pods -n netobserv -l app=netobserv-plugin
kubectl logs -n netobserv -l app=netobserv-plugin
```

It is also possible that the OpenShift Console is failing to restart. There is for instance a [known issue](https://issues.redhat.com/browse/OCPBUGS-810) with very small clusters, causing this problem.
```bash
kubectl get pods -n openshift-console
```

```
NAME READY STATUS RESTARTS AGE
console-65486f987c-bk6zn 1/1 Running 0 44m
console-67fd7b6f49-l5nmq 0/1 Pending 0 10m
console-67fd7b6f49-wmhp4 0/1 Pending 0 10m
downloads-5fc6cc467f-2fttx 1/1 Running 0 45m
downloads-5fc6cc467f-2gfpw 1/1 Running 0 45m
```

To force a restart, kill the running console pod using the following command:
`oc delete pods -n openshift-console -l app=console`
Note that this will make the console unavailable for some time

### I first deployed flowcollector, and then kafka. Flowlogs-pipeline is not consuming any flow from Kafka

This is a [known bug](https://github.com/segmentio/kafka-go/issues/1044) in one of flowlogs-pipeline dependencies.

Please recreate the flowlogs-pipeline pods by either killing them maunally or deleting and recreating the flow collector object.

### I don't see flows from either the `br-int` or `br-ex` interfaces
### I don't see flows from either the `br-int` or `br-ex` interfaces

[`br-ex` and `br-int` are virtual bridge devices](https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.0/html/networking_guide/bridge-mappings),
so they operate at OSI Layer 2 (e.g. Ethernet level). The eBPF agent works at Layers 3 and 4
(IP and TCP level), so it is expected that traffic passing through `br-int` and `br-ex` is captured
by the agent when it is processed by other interfaces (e.g. physical host or virtual pod interfaces).

This means that, if you restrict the agent interfaces (using the `interfaces` or `excludeInterfaces`
properties) to attach only to `br-int` and/or `br-ex`, you won't be able to see any flow.
properties) to attach only to `br-int` and/or `br-ex`, you won't be able to see any flow.