Skip to content

ip-masq-agent broken for IPv4-only #26262

@qmonnet

Description

@qmonnet

What happened?

@gandro reports that, after #23219, he tested the ip-masq-agent in an IPv4-only cluster and observes the following error:

Controller Status:      21/22 healthy
  Name                            Last success   Last error   Count   Message
  bpf-map-sync-cilium_ipmasq_v6   never          9s ago       12      loading pinned map /sys/fs/bpf/tc/globals/cilium_ipmasq_v6: no such file or directory   

Adding that the ip-masq-agent seems broken, with the IPv4 map not containing any CIDRs anymore.

To be investigated as soon as possible - Worst case, we'll need to revert IPv6 ip-masq-agent before we cut 1.14.

Cilium Version

main branch, on top of #23219

Metadata

Metadata

Assignees

Labels

area/datapathImpacts bpf/ or low-level forwarding details, including map management and monitor messages.kind/bugThis is a bug in the Cilium logic.needs/e2e-testThis issue is not covered by existing CI tests, but should be.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions