Skip to content

Cilium with IPSec tunneling fails to start on 3033.2.2 #626

@shosti

Description

@shosti

Description

Since updating to 3033.2.2, all of my Cilium pods are in a CrashLoopBackoff state with the following error message:

level=fatal msg="IPSec with tunneling requires support for xfrm state output masks (Linux 4.19 or later)." error="invalid argument" subsys=daemon

After rolling back to 3033.2.1, cilium starts up again.

Impact

Cilium fails -> all other pods can't get network -> general mayhem 😈

Environment and steps to reproduce

  1. Set-up:
  1. Task: Automatic upgrade
  2. Action(s): Update from 3033.2.1 to 3033.2.2, check kubectl logs for a cilium pod
  3. Error:
level=fatal msg="IPSec with tunneling requires support for xfrm state output masks (Linux 4.19 or later)." error="invalid argument" subsys=daemon

Expected behavior

Cilium pods start up correctly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions