-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
Moderate
-
rhel-net-mgmt
-
5
-
False
-
False
-
-
Yes
-
None
-
Definition of Done:
Please mark each item below with ( / ) if completed or ( x ) if incomplete:
The acceptance criteria defined below are met.
Given NetworkManager exposes a geneve connection type with fields base-iface, id (VNI), remote/remote6, mtu,
When a connection is created (nmcli or D-Bus) and activated,
Then a kernel Geneve netdev exists (ip link), is up, has the configured MTU and IP (if set), and ip -d link show reflects Geneve attributes with kernel defaults applied. Also, configuration is persisted in keyfile and restored on NM restart.–
Given invalid inputs (id out of range, malformed remote/remote6, or missing base-iface),
When attempting to activate the connection,
Then activation fails with a clear error and no partial/ghost devices remain and when a valid connection is configured and the host reboots,
Then the Geneve netdev is recreated and UP with the same settings before dependent services start. Integration test case are available upstream
Code is reviewed and merged upstream.
Preliminary testing is done
Upstream documentation is written in the upstream MR
( ) RHEL documentation is written.
Definition of Done: Please mark each item below with ( / ) if completed or ( x ) if incomplete: The acceptance criteria defined below are met. Given NetworkManager exposes a geneve connection type with fields base-iface, id (VNI), remote/remote6, mtu, When a connection is created (nmcli or D-Bus) and activated, Then a kernel Geneve netdev exists (ip link), is up, has the configured MTU and IP (if set), and ip -d link show reflects Geneve attributes with kernel defaults applied. Also, configuration is persisted in keyfile and restored on NM restart. – Given invalid inputs (id out of range, malformed remote/remote6, or missing base-iface), When attempting to activate the connection, Then activation fails with a clear error and no partial/ghost devices remain and when a valid connection is configured and the host reboots, Then the Geneve netdev is recreated and UP with the same settings before dependent services start. Integration test case are available upstream Code is reviewed and merged upstream. Preliminary testing is done Upstream documentation is written in the upstream MR ( ) RHEL documentation is written. -
Requested
-
None
-
Unspecified Release Note Type - Unknown
-
Unspecified
-
Unspecified
-
Unspecified
-
None
Goal
As a system administrator, I want to create, modify, and persist Linux kernel Geneve tunnels directly via NetworkManager (nmcli/D‑Bus/keyfile), so that I can manage overlay connectivity declaratively and consistently alongside other interfaces, and enable nmstate to orchestrate Geneve at scale.
Acceptance criteria
A list of verification conditions, successful functional tests, or expected outcomes in order to declare this story/task successfully completed.
- Verify NetworkManager exposes a `geneve` connection type with fields: `base-iface`, `id` (VNI), `remote`/`remote6`, `mtu`; attributes are persisted and restored on restart.
- Verify kernel Geneve attributes per ip‑link “geneve” are supported: https://man7.org/linux/man-pages/man8/ip-link.8.html
- Verify create/activate: `ip -d link show` reflects configured/default Geneve attributes; device is UP and IP/MTU are applied when set.
- Verify validation: invalid `id` range, malformed `remote`/`remote6`, or missing `base-iface` fails activation with clear error and no orphan devices.
- Verify persistence across reboot: valid configuration recreates the Geneve netdev and brings it up before dependent services start.