Andrew Purtell created HBASE-13676:
--------------------------------------
Summary:
TestRegionServerHostname#testInvalidRegionServerHostnameAbortsServer is failing
Key: HBASE-13676
URL: https://issues.apache.org/jira/browse/HBASE-13676
Project: HBase
Issue Type: Bug
Affects Versions: 2.0.0, 1.1.0
Reporter: Andrew Purtell
{noformat}
Running org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 14.543 sec <<<
FAILURE! - in org.apache.hadoop.hbase.regionserver.TestRegionServerHostname
testInvalidRegionServerHostnameAbortsServer(org.apache.hadoop.hbase.regionserver.TestRegionServerHostname)
Time elapsed: 6.845 sec <<< FAILURE!
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at
org.apache.hadoop.hbase.regionserver.TestRegionServerHostname.testInvalidRegionServerHostnameAbortsServer(TestRegionServerHostname.java:57)
Results :
Failed tests:
TestRegionServerHostname.testInvalidRegionServerHostnameAbortsServer:57 null
{noformat}
This is because the exception message is not what the test expects. We want a
string containing "Failed resolve of " + invalidHostname, what I have is
"java.net.BindException: Problem binding to hostAddr.invalid/198.105.244.228:0
: Cannot assign requested address"
This is because my ISP is "helpfully" providing A records for invalid DNS
records.
{noformat}
apurtell@aspire ~ $ dig hostAddr.invalid
; <<>> DiG 9.9.5-3ubuntu0.2-Ubuntu <<>> hostAddr.invalid
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49027
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;hostAddr.invalid. IN A
;; ANSWER SECTION:
hostAddr.invalid. 10 IN A 198.105.244.228
hostAddr.invalid. 10 IN A 198.105.254.228
;; Query time: 27 msec
;; SERVER: 127.0.1.1#53(127.0.1.1)
;; WHEN: Tue May 12 13:34:21 PDT 2015
;; MSG SIZE rcvd: 66
{noformat}
The test should be made more general to capture this kind of failure too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
