]
Brian Stansberry moved JBEAP-10141 to WFCORE-2626:
--------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-2626 (was: JBEAP-10141)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Domain Management
(was: Domain Management)
Affects Version/s: (was: 7.0.5.GA)
Network interface selection criteria is not working for a duplicate
IP addresses but one is down
------------------------------------------------------------------------------------------------
Key: WFCORE-2626
URL:
https://issues.jboss.org/browse/WFCORE-2626
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Environment: On Fedora 24 KVM instance, I added 2 extra NICs those are recognized
as ens9 and ens10. Both have 192.168.1.1 but one is down.
{code}
# ip address show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group
default qlen 1000
link/ether 52:54:00:ca:86:e2 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.117/24 brd 192.168.122.255 scope global dynamic ens3
valid_lft 3483sec preferred_lft 3483sec
inet6 fe80::782d:5d87:243d:917f/64 scope link
valid_lft forever preferred_lft forever
3: ens9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group
default qlen 1000
link/ether 52:54:00:ee:c6:16 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 scope global ens9
valid_lft forever preferred_lft forever
4: ens10: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel state DOWN group default
qlen 1000
link/ether 52:54:00:52:78:ca brd ff:ff:ff:ff:ff:ff
inet 192.168.1.1/24 scope global ens10
valid_lft forever preferred_lft forever
{code}
Note that those devices should be unmanaged by NetworkManager by "{{nmcli device set
ens9 managed no}}". And you can give an IP address by "{{ip addr add
192.168.1.1/24 dev ens9}}". Repeat the same on ens10.
Reporter: Osamu Nagano
Assignee: Brian Stansberry
In the standalone.xml, there are {{<up/>}} criterion which is sufficient to
identify a unique NIC under the environment described above.
{code}
<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>
{code}
But it says "ambiguous". WildFly 10.1.0.Final doesn't show this error.
{code}
# $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)
...
{code}