Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-2626

Network interface selection criteria is not working for a duplicate IP addresses but one is down

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 3.0.0.Beta16
    • None
    • Management
    • None
    • Hide

      Suppose 2 NICs are added (by virt-manager) and recognised as "ens9" and "ens10" respectively. These need to be umanamged by NetworkManager. Then asign the same IP address and disable "ens10".

      # nmcli device set ens9 managed no
# ip addr add 192.168.1.1/24 dev ens9 
(Repeat the same for "ens10".)
# ip link set ens10 down
      Show
      Suppose 2 NICs are added (by virt-manager) and recognised as "ens9" and "ens10" respectively. These need to be umanamged by NetworkManager. Then asign the same IP address and disable "ens10". # nmcli device set ens9 managed no # ip addr add 192.168.1.1/24 dev ens9 (Repeat the same for "ens10" .) # ip link set ens10 down

      In the standalone.xml, there are <up/> criterion which is sufficient to identify a unique NIC under the environment described above.

          <interfaces>
        <interface name="management">
            <up/>
            <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>
        </interface>
        <interface name="public">
            <up/>
            <inet-address value="${jboss.bind.address:127.0.0.1}"/>
        </interface>
    </interfaces>

      But it says "ambiguous". WildFly 10.1.0.Final doesn't show this error.

      # $JBOSS_HOME/bin/standalone.sh -b 192.168.1.1 -bmanagement=192.168.1.1
...
04:38:52,839 WARN  [org.jboss.as.controller] (MSC service thread 1-3) WFLYCTL0023: Value '192.168.1.1' for interface selection criteria 'inet-address' is ambiguous, as more than one address or network interface available on the machine matches it. Because of this ambiguity,
 no address will be selected as a match. Matching addresses: [/192.168.1.1].  Matching network interfaces: [ens9, ens10].
04:38:52,840 WARN  [org.jboss.as.controller] (MSC service thread 1-4) WFLYCTL0023: Value '192.168.1.1' for interface selection criteria 'inet-address' is ambiguous, as more than one address or network interface available on the machine matches it. Because of this ambiguity,
 no address will be selected as a match. Matching addresses: [/192.168.1.1].  Matching network interfaces: [ens9, ens10].
04:38:52,840 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.network.public: org.jboss.msc.service.StartException in service jboss.network.public: WFLYSRV0082: failed to resolve interface public
        at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:91)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

04:38:52,841 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: WFLYSRV0082: failed to resolve interface management
        at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:91)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
        at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)
...

              bstansbe@redhat.com Brian Stansberry
              rhn-support-onagano Osamu Nagano
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: