[ 
https://issues.apache.org/jira/browse/HADOOP-16544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16939140#comment-16939140
 ] 

Masatake Iwasaki commented on HADOOP-16544:
-------------------------------------------

TestJournalNodeRespectsBindHostKeys failed multiple times but the cause looks 
like build environment issue. The test succeeded on my local. JournalNode does 
not use netty.
{noformat}
[ERROR] Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.386 s 
<<< FAILURE! - in 
org.apache.hadoop.hdfs.qjournal.server.TestJournalNodeRespectsBindHostKeys
[ERROR] 
testHttpsBindHostKey(org.apache.hadoop.hdfs.qjournal.server.TestJournalNodeRespectsBindHostKeys)
  Time elapsed: 2.62 s  <<< ERROR!
java.io.FileNotFoundException: /home/jenkins/.keystore (No such file or 
directory)
        at java.io.FileInputStream.open0(Native Method)
        at java.io.FileInputStream.open(FileInputStream.java:195)
        at java.io.FileInputStream.<init>(FileInputStream.java:138)
        at 
org.mortbay.resource.FileResource.getInputStream(FileResource.java:275)
        at 
org.mortbay.jetty.security.SslSelectChannelConnector.createSSLContext(SslSelectChannelConnector.java:624)
        ...
{noformat}

> update io.netty in branch-2
> ---------------------------
>
>                 Key: HADOOP-16544
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16544
>             Project: Hadoop Common
>          Issue Type: Task
>            Reporter: Wei-Chiu Chuang
>            Assignee: Masatake Iwasaki
>            Priority: Major
>              Labels: release-blocker
>         Attachments: HADOOP-16544-branch-2.001.patch, 
> HADOOP-16544-branch-2.002.patch, HADOOP-16544-branch-2.003.patch, 
> HADOOP-16544-branch-2.004.patch
>
>
> branch-2 pulls in io.netty 3.6.2.Final which is more than 5 years old.
> The latest is 3.10.6Final. I know updating netty is sensitive but it deserves 
> some attention.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to