Skip to content

troubleshooting.md

Latest commit

 

History

History
73 lines (52 loc) · 2.45 KB

troubleshooting.md

File metadata and controls

73 lines (52 loc) · 2.45 KB

Troubleshooting

ErrArbitrationFailed on Dial

The target did not respond to the initial MasterArbitrationUpdate within the arbitration timeout. Common causes:

  • The target is still warming up (BMv2 takes a few hundred ms to start the gRPC server).
  • Another controller owns the primary election with a higher election ID — you are connected but backup; inspect c.State() to confirm.
  • TLS mismatch: you dialed with WithInsecure() but the server requires TLS, or vice versa.

Bump the timeout with client.WithArbitrationTimeout(30 * time.Second) and re-check logs at INFO level — the supervisor logs every connection attempt.

ErrNotPrimary on Write / SetPipeline

The client lost primary status (stream drop + re-arbitration, or another controller took over with a higher election ID). Call c.BecomePrimary(ctx) to wait for primary to return, or bump the election ID.

SetForwardingPipelineConfig keeps failing

The SDK walks VERIFY_AND_COMMIT → RECONCILE_AND_COMMIT → COMMIT. If every step fails, the final error is returned. Typical root causes:

  • P4Info bytes do not match the compiled pipeline blob. Re-run p4c to produce a matching pair.
  • The target dislikes RECONCILE_AND_COMMIT on first boot — pass client.SetPipelineOptions{Action: client.PipelineCommit} once to seed the pipeline, then switch back to the default.

Leading zeros in match fields

The P4Runtime spec mandates no leading zero bytes in integer match fields. If you feed []byte{0x00, 0x01} directly into the wire message the target will reject it. Always run values through codec.EncodeBytes, codec.MAC, codec.IPv4, or codec.IPv6.

Packet-in decode drops metadata

The SDK only decodes metadata fields it can resolve through the active Pipeline. If a metadata field is missing, verify that the P4Info you loaded actually declares controller_packet_metadata with the expected name and field IDs.

High CPU in the stream goroutine

If you registered a slow PacketInHandler, it runs inline on the supervisor goroutine and blocks the next receive. Push work to a buffered channel or a worker pool.

BMv2 on Apple Silicon

Pin the image to an arm64 build:

docker pull p4lang/behavioral-model:latest-arm64
./scripts/run-bmv2.sh -i p4lang/behavioral-model:latest-arm64

Running integration tests

./scripts/run-bmv2.sh
make e2e

The integration suite uses the integration build tag; it is excluded from the default make test run.