[
https://issues.apache.org/jira/browse/QPID-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208901#comment-13208901
]
Robbie Gemmell commented on QPID-3827:
--------------------------------------
Might be worth asking if its considered a config problem on the box, but coding
round it doesn't seems like it would be a bad idea for test robustness.
> FirewallConfigTests fail on FreeBSD Jenkins CI due to peer IP reported as
> non-loopback
> --------------------------------------------------------------------------------------
>
> Key: QPID-3827
> URL: https://issues.apache.org/jira/browse/QPID-3827
> Project: Qpid
> Issue Type: Bug
> Components: Java Tests
> Affects Versions: 0.15
> Reporter: Keith Wall
> Priority: Trivial
>
> The firewall tests fail because the tests assume that the client will be
> connecting to the loopback address. When the tests run on the Apache FreeBSD
> box, the peer's actual IP is reported to the Broker (140.211.166.131). This
> means the network firewall rules configured by FirewallConfigTest don't fire
> correctly. When we run the tests on other hosts, the Broker sees the loopback
> address.
> I'm not sure if the problem is the test making a bad assumption, or a config
> problem on the FreeBSD box.
> We *could* code around this in FirewallConfigTest by using
> {code}
> InetAddress.getByName("localhost").getHostAddress();
> {code}
> rather than assuming 127.0.0.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
