Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-10117

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

    XMLWordPrintable

Details

    • 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

    Description

      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)
...

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-10425 (7.0.z) WFCORE-2626 - Network interface selection criteria is not working for a duplicate IP addresses but one is down

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-2626 Network interface selection criteria is not working for a duplicate IP addresses but one is down

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-10119 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta16

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: