-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
rhel-9.5
-
nmstate-2.2.35-1.el9
-
No
-
Low
-
2
-
rhel-sst-network-management
-
ssg_networking
-
2
-
False
-
-
No
-
NMT - RHEL-9.5 DTM 24, Future releases
-
-
Pass
-
None
-
Unspecified Release Note Type - Unknown
-
None
What were you trying to do that didn't work?
In general, when using identifier=mac-address, interfaces.name will be used as NM profile/connection name, but this doesn't work when using nmpolicy.
Please provide the package NVR for which bug is seen:
nmstate-2.2.35-1.el9.x86_64
How reproducible:
100%
Steps to reproduce
cat << EOF > nmpolicy.yaml --- capture: gw: routes.running.destination=="0.0.0.0/0" gw-iface: interfaces.name==capture.gw.routes.running.0.next-hop-interface desiredState: interfaces: - name: test0-eth0 identifier: mac-address mac-address: "{{ capture.gw-iface.interfaces.0.mac-address }}" EOF nmstatectl apply nmpolicy.yaml --no-commit --timeout 10
Expected results
Actual results
[root@vm-10-0-185-109 ~]# nmstatectl set nmpolicy.yaml --no-commit --timeout 10 [2024-09-04T06:53:12Z INFO nmstatectl] Nmstate version: 2.2.35 Using 'set' is deprecated, use 'apply' instead. [2024-09-04T06:53:12Z ERROR nmstate::ifaces::inter_ifaces] InvalidArgument: Failed to find unknown type interface test0-eth0 in current state NmstateError: InvalidArgument: Failed to find unknown type interface test0-eth0 in current state [root@vm-10-0-185-109 ~]# [root@vm-10-0-185-109 ~]# cat nmpolicy.yaml --- capture: gw: routes.running.destination=="0.0.0.0/0" gw-iface: interfaces.name==capture.gw.routes.running.0.next-hop-interface desiredState: interfaces: - name: test0-eth0 identifier: mac-address mac-address: "{{ capture.gw-iface.interfaces.0.mac-address }}"
- is triggered by
-
RHEL-54292 Nmpolicy cannot change interface identifier to mac-address
- Closed