[jira] [Updated] (HDDS-1355) Only FQDN is accepted for OM rpc address in secure environment

2019-04-02 Thread Xiaoyu Yao (JIRA) 


 [ 
https://issues.apache.org/jira/browse/HDDS-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xiaoyu Yao updated HDDS-1355:
-
Fix Version/s: 0.4.0

> Only FQDN is accepted for OM rpc address in secure environment
> --
>
> Key: HDDS-1355
> URL: https://issues.apache.org/jira/browse/HDDS-1355
> Project: Hadoop Distributed Data Store
>  Issue Type: Bug
>Reporter: Elek, Marton
>Assignee: Ajay Kumar
>Priority: Major
>  Labels: pull-request-available
> Fix For: 0.4.0
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> While the scm address can be a host name (relative to the current search 
> domain) if the om address is just a hostname and not a FQDN a NPE is thrown:
> {code}
>   10   │   OZONE-SITE.XML_ozone.om.address: "om-0.om"
>   11   │   OZONE-SITE.XML_ozone.scm.client.address: "scm-0.scm"
>   12   │   OZONE-SITE.XML_ozone.scm.names: "scm-0.scm"
> {code} 
> {code}
> 2019-03-29 14:37:52 ERROR OzoneManager:865 - Failed to start the OzoneManager.
> java.lang.NullPointerException
> at 
> org.apache.hadoop.ozone.om.OzoneManager.getSCMSignedCert(OzoneManager.java:1372)
> at 
> org.apache.hadoop.ozone.om.OzoneManager.initializeSecurity(OzoneManager.java:1018)
> at org.apache.hadoop.ozone.om.OzoneManager.omInit(OzoneManager.java:971)
> at org.apache.hadoop.ozone.om.OzoneManager.createOm(OzoneManager.java:928)
> at org.apache.hadoop.ozone.om.OzoneManager.main(OzoneManager.java:859)
> {code}
> I don't know what is the right validation rule here, but I am pretty sure 
> that NPE should be avoided and a meaningful error should be thrown. (and the 
> behaviour should be the same for scm and om)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

[jira] [Updated] (HDDS-1355) Only FQDN is accepted for OM rpc address in secure environment

2019-04-02 Thread Xiaoyu Yao (JIRA) 


 [ 
https://issues.apache.org/jira/browse/HDDS-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xiaoyu Yao updated HDDS-1355:
-
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Only FQDN is accepted for OM rpc address in secure environment
> --
>
> Key: HDDS-1355
> URL: https://issues.apache.org/jira/browse/HDDS-1355
> Project: Hadoop Distributed Data Store
>  Issue Type: Bug
>Reporter: Elek, Marton
>Assignee: Ajay Kumar
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> While the scm address can be a host name (relative to the current search 
> domain) if the om address is just a hostname and not a FQDN a NPE is thrown:
> {code}
>   10   │   OZONE-SITE.XML_ozone.om.address: "om-0.om"
>   11   │   OZONE-SITE.XML_ozone.scm.client.address: "scm-0.scm"
>   12   │   OZONE-SITE.XML_ozone.scm.names: "scm-0.scm"
> {code} 
> {code}
> 2019-03-29 14:37:52 ERROR OzoneManager:865 - Failed to start the OzoneManager.
> java.lang.NullPointerException
> at 
> org.apache.hadoop.ozone.om.OzoneManager.getSCMSignedCert(OzoneManager.java:1372)
> at 
> org.apache.hadoop.ozone.om.OzoneManager.initializeSecurity(OzoneManager.java:1018)
> at org.apache.hadoop.ozone.om.OzoneManager.omInit(OzoneManager.java:971)
> at org.apache.hadoop.ozone.om.OzoneManager.createOm(OzoneManager.java:928)
> at org.apache.hadoop.ozone.om.OzoneManager.main(OzoneManager.java:859)
> {code}
> I don't know what is the right validation rule here, but I am pretty sure 
> that NPE should be avoided and a meaningful error should be thrown. (and the 
> behaviour should be the same for scm and om)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

[jira] [Updated] (HDDS-1355) Only FQDN is accepted for OM rpc address in secure environment

2019-04-01 Thread ASF GitHub Bot (JIRA) 


 [ 
https://issues.apache.org/jira/browse/HDDS-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated HDDS-1355:
-
Labels: pull-request-available  (was: )

> Only FQDN is accepted for OM rpc address in secure environment
> --
>
> Key: HDDS-1355
> URL: https://issues.apache.org/jira/browse/HDDS-1355
> Project: Hadoop Distributed Data Store
>  Issue Type: Bug
>Reporter: Elek, Marton
>Assignee: Ajay Kumar
>Priority: Major
>  Labels: pull-request-available
>
> While the scm address can be a host name (relative to the current search 
> domain) if the om address is just a hostname and not a FQDN a NPE is thrown:
> {code}
>   10   │   OZONE-SITE.XML_ozone.om.address: "om-0.om"
>   11   │   OZONE-SITE.XML_ozone.scm.client.address: "scm-0.scm"
>   12   │   OZONE-SITE.XML_ozone.scm.names: "scm-0.scm"
> {code} 
> {code}
> 2019-03-29 14:37:52 ERROR OzoneManager:865 - Failed to start the OzoneManager.
> java.lang.NullPointerException
> at 
> org.apache.hadoop.ozone.om.OzoneManager.getSCMSignedCert(OzoneManager.java:1372)
> at 
> org.apache.hadoop.ozone.om.OzoneManager.initializeSecurity(OzoneManager.java:1018)
> at org.apache.hadoop.ozone.om.OzoneManager.omInit(OzoneManager.java:971)
> at org.apache.hadoop.ozone.om.OzoneManager.createOm(OzoneManager.java:928)
> at org.apache.hadoop.ozone.om.OzoneManager.main(OzoneManager.java:859)
> {code}
> I don't know what is the right validation rule here, but I am pretty sure 
> that NPE should be avoided and a meaningful error should be thrown. (and the 
> behaviour should be the same for scm and om)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

[jira] [Updated] (HDDS-1355) Only FQDN is accepted for OM rpc address in secure environment

2019-04-01 Thread Ajay Kumar (JIRA) 


 [ 
https://issues.apache.org/jira/browse/HDDS-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ajay Kumar updated HDDS-1355:
-
Status: Patch Available  (was: Open)

> Only FQDN is accepted for OM rpc address in secure environment
> --
>
> Key: HDDS-1355
> URL: https://issues.apache.org/jira/browse/HDDS-1355
> Project: Hadoop Distributed Data Store
>  Issue Type: Bug
>Reporter: Elek, Marton
>Assignee: Ajay Kumar
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> While the scm address can be a host name (relative to the current search 
> domain) if the om address is just a hostname and not a FQDN a NPE is thrown:
> {code}
>   10   │   OZONE-SITE.XML_ozone.om.address: "om-0.om"
>   11   │   OZONE-SITE.XML_ozone.scm.client.address: "scm-0.scm"
>   12   │   OZONE-SITE.XML_ozone.scm.names: "scm-0.scm"
> {code} 
> {code}
> 2019-03-29 14:37:52 ERROR OzoneManager:865 - Failed to start the OzoneManager.
> java.lang.NullPointerException
> at 
> org.apache.hadoop.ozone.om.OzoneManager.getSCMSignedCert(OzoneManager.java:1372)
> at 
> org.apache.hadoop.ozone.om.OzoneManager.initializeSecurity(OzoneManager.java:1018)
> at org.apache.hadoop.ozone.om.OzoneManager.omInit(OzoneManager.java:971)
> at org.apache.hadoop.ozone.om.OzoneManager.createOm(OzoneManager.java:928)
> at org.apache.hadoop.ozone.om.OzoneManager.main(OzoneManager.java:859)
> {code}
> I don't know what is the right validation rule here, but I am pretty sure 
> that NPE should be avoided and a meaningful error should be thrown. (and the 
> behaviour should be the same for scm and om)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org