What were you trying to do that didn't work?

I am unable to create a Linux bond by referencing a pre-existing permanent Linux bridge as its controller, unless the bridge is explicitly defined within the YAML configuration file. In addition, the error message provided is not sufficiently clear.

It is similar to RHEL-31981 but not the same.

What is the impact of this issue to you?

Please provide the package NVR for which the bug is seen:

nmstate-2.2.45-1.el9.x86_64
NetworkManager-1.53.90-1.el9.x86_64

How reproducible is this bug?:

100%

Steps to reproduce

1. Ensure the Linux bridge (BR-DHCP2) is not defined in the YAML when creating bond.
2. The bond should include `port`
3. The port interfaces (dummys) didn't exist, should be defined within the same YAML. It doesn't matter whether the port interfaces (dummys) already exist or to be created in the YAML

echo "
interfaces:
- name: BR-DHCP2
  type: linux-bridge
  state: up
" | nmstatectl apply

echo "
interfaces:
- name: bond0_p
  type: bond
  controller: BR-DHCP2
  state: up
  mtu: 9000
  link-aggregation:
    mode: 802.3ad
    port:
      - dummy0
      - dummy1
- name: dummy0
  type: dummy
  state: up
- name: dummy1
  type: dummy
  state: up
" | nmstatectl apply  # <----- failed

Expected results

success

Actual results

25-06-18T03:06:58Z ERROR nmstate::ifaces::inter_ifaces] Failed to set up priority: please order the interfaces in desire state to place controller before its ports
NmstateError: InvalidArgument: Failed to set up priority: nmstate only support nested interface up to 4 levels. To support more nest level, please order the interfaces in desire state to place controller before its ports

The error message is not clear yet:

1. There are only 3 levels: BR-DHCP2 - - - bond0_p - - - dummys
2. despite the level counts, placing BR-DHCP2 at the end of the YAML will work, even after its port (bond0_p)