XMLWordPrintable

    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • os-net-config-18.0.1-18.0.20250621114744.22b9a65
    • rhos-connectivity-nfv-automation
    • NFV Automation 010
    • 1

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

      Apply 2 sets of templates one after the other

       

       

      interfaces:
      - ipv4:
          dhcp: false
          enabled: false
        ipv6:
          autoconf: false
          dhcp: false
          enabled: false
        name: br-ex
        state: up
        type: ovs-interface
      - ethernet: {}
        ipv4:
          auto-dns: true
          auto-gateway: false
          auto-routes: true
          dhcp: true
          enabled: true
        ipv6:
          auto-gateway: false
          autoconf: false
          dhcp: false
          enabled: false
        name: eno8303
        state: up
        type: ethernet
      - ethernet:
          sr-iov:
            total-vfs: 0
        ipv4:
          address:
          - ip: 192.168.122.100
            prefix-length: 24
          auto-dns: false
          auto-gateway: false
          dhcp: false
          enabled: true
        ipv6:
          auto-dns: false
          auto-gateway: false
          autoconf: false
          dhcp: false
          enabled: false
        name: ens1f0
        state: up
        type: ethernet
      - ethernet:
          sr-iov:
            total-vfs: 0
        ipv4:
          address:
          - ip: 100.64.0.2
            prefix-length: 30
          dhcp: false
          enabled: true
        ipv6:
          autoconf: false
          dhcp: false
          enabled: false
        name: ens1f1
        state: up
        type: ethernet
      - ethernet:
          sr-iov:
            total-vfs: 0
        ipv4:
          address:
          - ip: 100.65.0.2
            prefix-length: 30
          dhcp: false
          enabled: true
        ipv6:
          autoconf: false
          dhcp: false
          enabled: false
        name: ens1f2
        state: up
        type: ethernet
      - bridge:
          options:
            fail-mode: standalone
            mcast-snooping-enable: false
            rstp: false
            stp: false
          port: []
        name: br-ex
        ovs-db:
          external_ids: {}
          other_config:
            mac-table-size: 50000
        state: up
        type: ovs-bridge
      dns-resolver:
        config:
          search:
          - ctlplane.example.com
          - internalapi.example.com
          - storage.example.com
          - tenant.example.com
          - bgpnet0.example.com
          - bgpnet1.example.com
          - bgpmainnet.example.com
          - bgpmainnetv6.example.com
          server:
          - 192.168.125.80 

       

       

      This is successful. Then apply the next one

       

      interfaces:
      - ethernet: {}
        ipv4:
          address:
          - ip: 99.99.0.7
            prefix-length: 32
          - ip: 172.17.0.101
            prefix-length: 32
          - ip: 172.18.0.101
            prefix-length: 32
          - ip: 172.19.0.101
            prefix-length: 32
          dhcp: false
          enabled: true
        ipv6:
          address:
          - ip: f00d:f00d:f00d:f00d:f00d:f00d:f00d:17
            prefix-length: 128
          autoconf: false
          dhcp: false
          enabled: true
        name: lo
        state: up
        type: ethernet 

       

       

      Configuring the `lo` device fails with the below error.

       

      2025-06-13 06:07:05.330 ERROR os_net_config.impl_nmstate.nmstate_apply Error seen while applying the nmstate templates Manager(UnknownDevice): No suitable device found for this connection (device eno12399 not available because profile is not compatible with device (mismatching interface name)). 

      What is the impact of this issue to you?

       

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

      [root@compute-0 cloud-admin]# nmcli -v
      nmcli tool, version 1.46.0-26.el9_4
      [root@compute-0 cloud-admin]# nmstatectl --version
      nmstatectl 2.2.45 

      How reproducible is this bug?:

      Always

      Expected results

      The `lo` device configuration shall be successful.

      Actual results

      The `lo` device configuration fails.

              ksundara@redhat.com Karthik Sundaravel
              ksundara@redhat.com Karthik Sundaravel
              rhos-dfg-nfv
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: