Bug 1111578

Summary: [SET] (6.3.1) subnet-match is completely broken
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Ivo Studensky <istudens>
Component: Domain ManagementAssignee: Ivo Studensky <istudens>
Status: CLOSED WONTFIX QA Contact: Petr Kremensky <pkremens>
Severity: unspecified Docs Contact: Russell Dickenson <rdickens>
Priority: unspecified    
Version: 6.3.0CC: cdewolf, emuckenh, myarboro, smumford
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1111575 Environment:
Last Closed: 2014-06-30 13:46:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On: 1111575    
Bug Blocks:    

Description Ivo Studensky 2014-06-20 12:13:40 UTC
+++ This bug was initially created as a clone of Bug #1111575 +++
A clone for 6.3.1.

Description of problem:

subnet-match does not respect the value attribute. Instead, it seems to just pick the first interface it finds. No matter what I specify as a value, even if it's a value that's complete nonsense and doesn't match any IP address on my system, e.g.

<interface name="public">
    <subnet-match value=""/>

the ports end up bound to the only interface that is currently connected

14:45:16,740 INFO  [stdout] (ServerService Thread Pool -- 40) -------------------------------------------------------------------
14:45:16,740 INFO  [stdout] (ServerService Thread Pool -- 40) GMS: address=normandy/GamingPortal, cluster=GamingPortal, physical address=
14:45:16,741 INFO  [stdout] (ServerService Thread Pool -- 40) -------------------------------------------------------------------

Comment 1 JBoss JIRA Server 2014-06-26 08:30:55 UTC
Ivo Studensky <istudens@redhat.com> updated the status of jira WFLY-3478 to Reopened

Comment 2 JBoss JIRA Server 2014-06-27 04:58:18 UTC
Ivo Studensky <istudens@redhat.com> updated the status of jira WFLY-3478 to Resolved