Bug 1111575

Summary: (6.x) subnet-match is does not respect 'value' attribute
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Ivo Studensky <istudens>
Component: Domain ManagementAssignee: Ivo Studensky <istudens>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Kremensky <pkremens>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: cdewolf, dandread, kkhan
Target Milestone: DR1   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previous releases of JBoss EAP 6 carried a bug that prevented subnet-match from respecting the `value` attribute. In this release of the product, the issue has been resolved and the `value` attribute works as expected.
Story Points: ---
Clone Of:
: 1111578 (view as bug list) Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1111578    

Description Ivo Studensky 2014-06-20 12:10:18 UTC
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 2 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 3 Ivo Studensky 2014-06-26 08:34:33 UTC
PR sent:

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