-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Monitor test relies on dumping host endpoint debug messages #12037
Copy link
Copy link
Closed
Labels
area/datapathImpacts bpf/ or low-level forwarding details, including map management and monitor messages.Impacts bpf/ or low-level forwarding details, including map management and monitor messages.area/host-firewallImpacts the host firewall or the host endpoint.Impacts the host firewall or the host endpoint.area/monitorImpacts monitoring, access logging, flow logging, visibility of datapath traffic.Impacts monitoring, access logging, flow logging, visibility of datapath traffic.
Metadata
Metadata
Assignees
Labels
area/datapathImpacts bpf/ or low-level forwarding details, including map management and monitor messages.Impacts bpf/ or low-level forwarding details, including map management and monitor messages.area/host-firewallImpacts the host firewall or the host endpoint.Impacts the host firewall or the host endpoint.area/monitorImpacts monitoring, access logging, flow logging, visibility of datapath traffic.Impacts monitoring, access logging, flow logging, visibility of datapath traffic.
It's not possible to reconfigure host endpoint datapath options because it has reserved labels and we disable it in the API:
This by itself is fine, but in PR #11977 we disable datapath debug mode by default, which means we can't turn it back on.
Combined with the RuntimeMonitor tests which iterate through all endpoints to make sure that debug mode outputs events for all endpoints, this causes a test failure.