[jira] [Comment Edited] (KUDU-3087) Python tests failed on arm64
[
https://issues.apache.org/jira/browse/KUDU-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17066439#comment-17066439
]
huangtianhua edited comment on KUDU-3087 at 3/25/20, 6:49 AM:
--
[~aserbin], I try to add "openssl_security_level_override=2" if size is 2048,
seems the tests passed on my aarch64 instance:
{ "numMasters" : cls.NUM_MASTER_SERVERS,
"numTservers" : cls.NUM_TABLET_SERVERS,
"extraMasterFlags" : [
"--default_num_replicas=1",
"--ipki_ca_key_size=2048",
"--ipki_server_key_size=2048",
"--openssl_security_level_override=2" ],
"extraTserverFlags" : [ "--ipki_server_key_size=2048" ,
"--openssl_security_level_override=2"]}})
was (Author: huangtianhua):
[~aserbin], I try to add "openssl_security_level_override=2" if size is 2048,
seems the tests passed on my aarch64 instance:
{ "numMasters" : cls.NUM_MASTER_SERVERS,
"numTservers" : cls.NUM_TABLET_SERVERS,
"extraMasterFlags" : [
"--default_num_replicas=1",
"--ipki_ca_key_size=2048",
"--ipki_server_key_size=2048",
"openssl_security_level_override=2" ],
"extraTserverFlags" : [ "--ipki_server_key_size=2048" ,
"openssl_security_level_override=2"]}})
> Python tests failed on arm64
>
>
> Key: KUDU-3087
> URL: https://issues.apache.org/jira/browse/KUDU-3087
> Project: Kudu
> Issue Type: Sub-task
>Reporter: huangtianhua
>Assignee: Alexey Serbin
>Priority: Major
> Attachments: python_test.rar
>
>
> I took python tests for kudu on arm64 platform based on
> https://gerrit.cloudera.org/#/c/14964/ the tests failed, error info as
> below:
> W0323 02:54:39.938022 9110 negotiation.cc:313] Failed RPC negotiation. Trace:
> 0323 02:54:39.936597 (+ 0us) reactor.cc:604] Submitting negotiation task
> for client connection to 127.8.25.194:34669
> 0323 02:54:39.936737 (+ 140us) negotiation.cc:98] Waiting for socket to
> connect
> 0323 02:54:39.936746 (+ 9us) client_negotiation.cc:169] Beginning
> negotiation
> 0323 02:54:39.936810 (+64us) client_negotiation.cc:246] Sending NEGOTIATE
> NegotiatePB request
> 0323 02:54:39.937073 (+ 263us) client_negotiation.cc:263] Received
> NEGOTIATE NegotiatePB response
> 0323 02:54:39.937074 (+ 1us) client_negotiation.cc:357] Received
> NEGOTIATE response from server
> 0323 02:54:39.937079 (+ 5us) client_negotiation.cc:184] Negotiated
> authn=TOKEN
> 0323 02:54:39.937168 (+89us) client_negotiation.cc:473] Sending
> TLS_HANDSHAKE message to server
> 0323 02:54:39.937171 (+ 3us) client_negotiation.cc:246] Sending
> TLS_HANDSHAKE NegotiatePB request
> 0323 02:54:39.937724 (+ 553us) client_negotiation.cc:263] Received
> TLS_HANDSHAKE NegotiatePB response
> 0323 02:54:39.937726 (+ 2us) client_negotiation.cc:486] Received
> TLS_HANDSHAKE response from server
> 0323 02:54:39.937906 (+ 180us) negotiation.cc:304] Negotiation complete:
> Runtime error: Client connection negotiation failed: client connection to
> 127.8.25.194:34669: TLS Handshake error: error:1416F086:SSL
> routines:tls_process_server_certificate:certificate verify
> failed:../ssl/statem/statem_clnt.c:1924
> Metrics:
> {"client-negotiator.queue_time_us":90,"thread_start_us":41,"threads_started":1}
> The python tests were successful before the commit
> https://github.com/apache/kudu/commit/3343144fefaad5a30e95e21297c64c78e308fa1f
> and I tried to remove this commit based on master and then the python tests
> are success, seems the problem introduced by
> https://github.com/apache/kudu/commit/3343144fefaad5a30e95e21297c64c78e308fa1f,
> but I am sorry I can't fix this, could someone help me？Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KUDU-3087) Python tests failed on arm64
[
https://issues.apache.org/jira/browse/KUDU-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17066439#comment-17066439
]
huangtianhua commented on KUDU-3087:
[~aserbin], I try to add "openssl_security_level_override=2" if size is 2048,
seems the tests passed on my aarch64 instance:
{ "numMasters" : cls.NUM_MASTER_SERVERS,
"numTservers" : cls.NUM_TABLET_SERVERS,
"extraMasterFlags" : [
"--default_num_replicas=1",
"--ipki_ca_key_size=2048",
"--ipki_server_key_size=2048",
"openssl_security_level_override=2" ],
"extraTserverFlags" : [ "--ipki_server_key_size=2048" ,
"openssl_security_level_override=2"]}})
> Python tests failed on arm64
>
>
> Key: KUDU-3087
> URL: https://issues.apache.org/jira/browse/KUDU-3087
> Project: Kudu
> Issue Type: Sub-task
>Reporter: huangtianhua
>Assignee: Alexey Serbin
>Priority: Major
> Attachments: python_test.rar
>
>
> I took python tests for kudu on arm64 platform based on
> https://gerrit.cloudera.org/#/c/14964/ the tests failed, error info as
> below:
> W0323 02:54:39.938022 9110 negotiation.cc:313] Failed RPC negotiation. Trace:
> 0323 02:54:39.936597 (+ 0us) reactor.cc:604] Submitting negotiation task
> for client connection to 127.8.25.194:34669
> 0323 02:54:39.936737 (+ 140us) negotiation.cc:98] Waiting for socket to
> connect
> 0323 02:54:39.936746 (+ 9us) client_negotiation.cc:169] Beginning
> negotiation
> 0323 02:54:39.936810 (+64us) client_negotiation.cc:246] Sending NEGOTIATE
> NegotiatePB request
> 0323 02:54:39.937073 (+ 263us) client_negotiation.cc:263] Received
> NEGOTIATE NegotiatePB response
> 0323 02:54:39.937074 (+ 1us) client_negotiation.cc:357] Received
> NEGOTIATE response from server
> 0323 02:54:39.937079 (+ 5us) client_negotiation.cc:184] Negotiated
> authn=TOKEN
> 0323 02:54:39.937168 (+89us) client_negotiation.cc:473] Sending
> TLS_HANDSHAKE message to server
> 0323 02:54:39.937171 (+ 3us) client_negotiation.cc:246] Sending
> TLS_HANDSHAKE NegotiatePB request
> 0323 02:54:39.937724 (+ 553us) client_negotiation.cc:263] Received
> TLS_HANDSHAKE NegotiatePB response
> 0323 02:54:39.937726 (+ 2us) client_negotiation.cc:486] Received
> TLS_HANDSHAKE response from server
> 0323 02:54:39.937906 (+ 180us) negotiation.cc:304] Negotiation complete:
> Runtime error: Client connection negotiation failed: client connection to
> 127.8.25.194:34669: TLS Handshake error: error:1416F086:SSL
> routines:tls_process_server_certificate:certificate verify
> failed:../ssl/statem/statem_clnt.c:1924
> Metrics:
> {"client-negotiator.queue_time_us":90,"thread_start_us":41,"threads_started":1}
> The python tests were successful before the commit
> https://github.com/apache/kudu/commit/3343144fefaad5a30e95e21297c64c78e308fa1f
> and I tried to remove this commit based on master and then the python tests
> are success, seems the problem introduced by
> https://github.com/apache/kudu/commit/3343144fefaad5a30e95e21297c64c78e308fa1f,
> but I am sorry I can't fix this, could someone help me？Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KUDU-3087) Python tests failed on arm64
[
https://issues.apache.org/jira/browse/KUDU-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17066432#comment-17066432
]
huangtianhua commented on KUDU-3087:
[~aserbin], I took test on my aarch64 instance, the python tests failed, there
is a piece of test log.
But if I modify to 1024, the tests passed:
{ "numMasters" : cls.NUM_MASTER_SERVERS,
"numTservers" : cls.NUM_TABLET_SERVERS,
"extraMasterFlags" : [
"--default_num_replicas=1",
"--ipki_ca_key_size=1024",
"--ipki_server_key_size=1024" ],
"extraTserverFlags" : [ "--ipki_server_key_size=1024" ]}})
> Python tests failed on arm64
>
>
> Key: KUDU-3087
> URL: https://issues.apache.org/jira/browse/KUDU-3087
> Project: Kudu
> Issue Type: Sub-task
>Reporter: huangtianhua
>Assignee: Alexey Serbin
>Priority: Major
> Attachments: python_test.rar
>
>
> I took python tests for kudu on arm64 platform based on
> https://gerrit.cloudera.org/#/c/14964/ the tests failed, error info as
> below:
> W0323 02:54:39.938022 9110 negotiation.cc:313] Failed RPC negotiation. Trace:
> 0323 02:54:39.936597 (+ 0us) reactor.cc:604] Submitting negotiation task
> for client connection to 127.8.25.194:34669
> 0323 02:54:39.936737 (+ 140us) negotiation.cc:98] Waiting for socket to
> connect
> 0323 02:54:39.936746 (+ 9us) client_negotiation.cc:169] Beginning
> negotiation
> 0323 02:54:39.936810 (+64us) client_negotiation.cc:246] Sending NEGOTIATE
> NegotiatePB request
> 0323 02:54:39.937073 (+ 263us) client_negotiation.cc:263] Received
> NEGOTIATE NegotiatePB response
> 0323 02:54:39.937074 (+ 1us) client_negotiation.cc:357] Received
> NEGOTIATE response from server
> 0323 02:54:39.937079 (+ 5us) client_negotiation.cc:184] Negotiated
> authn=TOKEN
> 0323 02:54:39.937168 (+89us) client_negotiation.cc:473] Sending
> TLS_HANDSHAKE message to server
> 0323 02:54:39.937171 (+ 3us) client_negotiation.cc:246] Sending
> TLS_HANDSHAKE NegotiatePB request
> 0323 02:54:39.937724 (+ 553us) client_negotiation.cc:263] Received
> TLS_HANDSHAKE NegotiatePB response
> 0323 02:54:39.937726 (+ 2us) client_negotiation.cc:486] Received
> TLS_HANDSHAKE response from server
> 0323 02:54:39.937906 (+ 180us) negotiation.cc:304] Negotiation complete:
> Runtime error: Client connection negotiation failed: client connection to
> 127.8.25.194:34669: TLS Handshake error: error:1416F086:SSL
> routines:tls_process_server_certificate:certificate verify
> failed:../ssl/statem/statem_clnt.c:1924
> Metrics:
> {"client-negotiator.queue_time_us":90,"thread_start_us":41,"threads_started":1}
> The python tests were successful before the commit
> https://github.com/apache/kudu/commit/3343144fefaad5a30e95e21297c64c78e308fa1f
> and I tried to remove this commit based on master and then the python tests
> are success, seems the problem introduced by
> https://github.com/apache/kudu/commit/3343144fefaad5a30e95e21297c64c78e308fa1f,
> but I am sorry I can't fix this, could someone help me？Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (KUDU-3087) Python tests failed on arm64
[
https://issues.apache.org/jira/browse/KUDU-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17066432#comment-17066432
]
huangtianhua edited comment on KUDU-3087 at 3/25/20, 6:34 AM:
--
[~aserbin], I took test on my aarch64 instance, the python tests failed, there
is a piece of test log: http://paste.openstack.org/show/791108/
But if I modify to 1024, the tests passed:
{ "numMasters" : cls.NUM_MASTER_SERVERS,
"numTservers" : cls.NUM_TABLET_SERVERS,
"extraMasterFlags" : [
"--default_num_replicas=1",
"--ipki_ca_key_size=1024",
"--ipki_server_key_size=1024" ],
"extraTserverFlags" : [ "--ipki_server_key_size=1024" ]}})
was (Author: huangtianhua):
[~aserbin], I took test on my aarch64 instance, the python tests failed, there
is a piece of test log.
But if I modify to 1024, the tests passed:
{ "numMasters" : cls.NUM_MASTER_SERVERS,
"numTservers" : cls.NUM_TABLET_SERVERS,
"extraMasterFlags" : [
"--default_num_replicas=1",
"--ipki_ca_key_size=1024",
"--ipki_server_key_size=1024" ],
"extraTserverFlags" : [ "--ipki_server_key_size=1024" ]}})
> Python tests failed on arm64
>
>
> Key: KUDU-3087
> URL: https://issues.apache.org/jira/browse/KUDU-3087
> Project: Kudu
> Issue Type: Sub-task
>Reporter: huangtianhua
>Assignee: Alexey Serbin
>Priority: Major
> Attachments: python_test.rar
>
>
> I took python tests for kudu on arm64 platform based on
> https://gerrit.cloudera.org/#/c/14964/ the tests failed, error info as
> below:
> W0323 02:54:39.938022 9110 negotiation.cc:313] Failed RPC negotiation. Trace:
> 0323 02:54:39.936597 (+ 0us) reactor.cc:604] Submitting negotiation task
> for client connection to 127.8.25.194:34669
> 0323 02:54:39.936737 (+ 140us) negotiation.cc:98] Waiting for socket to
> connect
> 0323 02:54:39.936746 (+ 9us) client_negotiation.cc:169] Beginning
> negotiation
> 0323 02:54:39.936810 (+64us) client_negotiation.cc:246] Sending NEGOTIATE
> NegotiatePB request
> 0323 02:54:39.937073 (+ 263us) client_negotiation.cc:263] Received
> NEGOTIATE NegotiatePB response
> 0323 02:54:39.937074 (+ 1us) client_negotiation.cc:357] Received
> NEGOTIATE response from server
> 0323 02:54:39.937079 (+ 5us) client_negotiation.cc:184] Negotiated
> authn=TOKEN
> 0323 02:54:39.937168 (+89us) client_negotiation.cc:473] Sending
> TLS_HANDSHAKE message to server
> 0323 02:54:39.937171 (+ 3us) client_negotiation.cc:246] Sending
> TLS_HANDSHAKE NegotiatePB request
> 0323 02:54:39.937724 (+ 553us) client_negotiation.cc:263] Received
> TLS_HANDSHAKE NegotiatePB response
> 0323 02:54:39.937726 (+ 2us) client_negotiation.cc:486] Received
> TLS_HANDSHAKE response from server
> 0323 02:54:39.937906 (+ 180us) negotiation.cc:304] Negotiation complete:
> Runtime error: Client connection negotiation failed: client connection to
> 127.8.25.194:34669: TLS Handshake error: error:1416F086:SSL
> routines:tls_process_server_certificate:certificate verify
> failed:../ssl/statem/statem_clnt.c:1924
> Metrics:
> {"client-negotiator.queue_time_us":90,"thread_start_us":41,"threads_started":1}
> The python tests were successful before the commit
> https://github.com/apache/kudu/commit/3343144fefaad5a30e95e21297c64c78e308fa1f
> and I tried to remove this commit based on master and then the python tests
> are success, seems the problem introduced by
> https://github.com/apache/kudu/commit/3343144fefaad5a30e95e21297c64c78e308fa1f,
> but I am sorry I can't fix this, could someone help me？Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KUDU-3087) Python tests failed on arm64
[
https://issues.apache.org/jira/browse/KUDU-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17066367#comment-17066367
]
huangtianhua commented on KUDU-3087:
[~aserbin]， Good job:) Thanks, I will test it on aarch64 platform.
> Python tests failed on arm64
>
>
> Key: KUDU-3087
> URL: https://issues.apache.org/jira/browse/KUDU-3087
> Project: Kudu
> Issue Type: Sub-task
>Reporter: huangtianhua
>Assignee: Alexey Serbin
>Priority: Major
> Attachments: python_test.rar
>
>
> I took python tests for kudu on arm64 platform based on
> https://gerrit.cloudera.org/#/c/14964/ the tests failed, error info as
> below:
> W0323 02:54:39.938022 9110 negotiation.cc:313] Failed RPC negotiation. Trace:
> 0323 02:54:39.936597 (+ 0us) reactor.cc:604] Submitting negotiation task
> for client connection to 127.8.25.194:34669
> 0323 02:54:39.936737 (+ 140us) negotiation.cc:98] Waiting for socket to
> connect
> 0323 02:54:39.936746 (+ 9us) client_negotiation.cc:169] Beginning
> negotiation
> 0323 02:54:39.936810 (+64us) client_negotiation.cc:246] Sending NEGOTIATE
> NegotiatePB request
> 0323 02:54:39.937073 (+ 263us) client_negotiation.cc:263] Received
> NEGOTIATE NegotiatePB response
> 0323 02:54:39.937074 (+ 1us) client_negotiation.cc:357] Received
> NEGOTIATE response from server
> 0323 02:54:39.937079 (+ 5us) client_negotiation.cc:184] Negotiated
> authn=TOKEN
> 0323 02:54:39.937168 (+89us) client_negotiation.cc:473] Sending
> TLS_HANDSHAKE message to server
> 0323 02:54:39.937171 (+ 3us) client_negotiation.cc:246] Sending
> TLS_HANDSHAKE NegotiatePB request
> 0323 02:54:39.937724 (+ 553us) client_negotiation.cc:263] Received
> TLS_HANDSHAKE NegotiatePB response
> 0323 02:54:39.937726 (+ 2us) client_negotiation.cc:486] Received
> TLS_HANDSHAKE response from server
> 0323 02:54:39.937906 (+ 180us) negotiation.cc:304] Negotiation complete:
> Runtime error: Client connection negotiation failed: client connection to
> 127.8.25.194:34669: TLS Handshake error: error:1416F086:SSL
> routines:tls_process_server_certificate:certificate verify
> failed:../ssl/statem/statem_clnt.c:1924
> Metrics:
> {"client-negotiator.queue_time_us":90,"thread_start_us":41,"threads_started":1}
> The python tests were successful before the commit
> https://github.com/apache/kudu/commit/3343144fefaad5a30e95e21297c64c78e308fa1f
> and I tried to remove this commit based on master and then the python tests
> are success, seems the problem introduced by
> https://github.com/apache/kudu/commit/3343144fefaad5a30e95e21297c64c78e308fa1f,
> but I am sorry I can't fix this, could someone help me？Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (KUDU-3087) Python tests failed on arm64
[
https://issues.apache.org/jira/browse/KUDU-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin updated KUDU-3087:
Status: In Review (was: In Progress)
> Python tests failed on arm64
>
>
> Key: KUDU-3087
> URL: https://issues.apache.org/jira/browse/KUDU-3087
> Project: Kudu
> Issue Type: Sub-task
>Reporter: huangtianhua
>Assignee: Alexey Serbin
>Priority: Major
> Attachments: python_test.rar
>
>
> I took python tests for kudu on arm64 platform based on
> https://gerrit.cloudera.org/#/c/14964/ the tests failed, error info as
> below:
> W0323 02:54:39.938022 9110 negotiation.cc:313] Failed RPC negotiation. Trace:
> 0323 02:54:39.936597 (+ 0us) reactor.cc:604] Submitting negotiation task
> for client connection to 127.8.25.194:34669
> 0323 02:54:39.936737 (+ 140us) negotiation.cc:98] Waiting for socket to
> connect
> 0323 02:54:39.936746 (+ 9us) client_negotiation.cc:169] Beginning
> negotiation
> 0323 02:54:39.936810 (+64us) client_negotiation.cc:246] Sending NEGOTIATE
> NegotiatePB request
> 0323 02:54:39.937073 (+ 263us) client_negotiation.cc:263] Received
> NEGOTIATE NegotiatePB response
> 0323 02:54:39.937074 (+ 1us) client_negotiation.cc:357] Received
> NEGOTIATE response from server
> 0323 02:54:39.937079 (+ 5us) client_negotiation.cc:184] Negotiated
> authn=TOKEN
> 0323 02:54:39.937168 (+89us) client_negotiation.cc:473] Sending
> TLS_HANDSHAKE message to server
> 0323 02:54:39.937171 (+ 3us) client_negotiation.cc:246] Sending
> TLS_HANDSHAKE NegotiatePB request
> 0323 02:54:39.937724 (+ 553us) client_negotiation.cc:263] Received
> TLS_HANDSHAKE NegotiatePB response
> 0323 02:54:39.937726 (+ 2us) client_negotiation.cc:486] Received
> TLS_HANDSHAKE response from server
> 0323 02:54:39.937906 (+ 180us) negotiation.cc:304] Negotiation complete:
> Runtime error: Client connection negotiation failed: client connection to
> 127.8.25.194:34669: TLS Handshake error: error:1416F086:SSL
> routines:tls_process_server_certificate:certificate verify
> failed:../ssl/statem/statem_clnt.c:1924
> Metrics:
> {"client-negotiator.queue_time_us":90,"thread_start_us":41,"threads_started":1}
> The python tests were successful before the commit
> https://github.com/apache/kudu/commit/3343144fefaad5a30e95e21297c64c78e308fa1f
> and I tried to remove this commit based on master and then the python tests
> are success, seems the problem introduced by
> https://github.com/apache/kudu/commit/3343144fefaad5a30e95e21297c64c78e308fa1f,
> but I am sorry I can't fix this, could someone help me？Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (KUDU-3087) Python tests failed on arm64
[
https://issues.apache.org/jira/browse/KUDU-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Serbin updated KUDU-3087:
Code Review: http://gerrit.cloudera.org:8080/15554
> Python tests failed on arm64
>
>
> Key: KUDU-3087
> URL: https://issues.apache.org/jira/browse/KUDU-3087
> Project: Kudu
> Issue Type: Sub-task
>Reporter: huangtianhua
>Assignee: Alexey Serbin
>Priority: Major
> Attachments: python_test.rar
>
>
> I took python tests for kudu on arm64 platform based on
> https://gerrit.cloudera.org/#/c/14964/ the tests failed, error info as
> below:
> W0323 02:54:39.938022 9110 negotiation.cc:313] Failed RPC negotiation. Trace:
> 0323 02:54:39.936597 (+ 0us) reactor.cc:604] Submitting negotiation task
> for client connection to 127.8.25.194:34669
> 0323 02:54:39.936737 (+ 140us) negotiation.cc:98] Waiting for socket to
> connect
> 0323 02:54:39.936746 (+ 9us) client_negotiation.cc:169] Beginning
> negotiation
> 0323 02:54:39.936810 (+64us) client_negotiation.cc:246] Sending NEGOTIATE
> NegotiatePB request
> 0323 02:54:39.937073 (+ 263us) client_negotiation.cc:263] Received
> NEGOTIATE NegotiatePB response
> 0323 02:54:39.937074 (+ 1us) client_negotiation.cc:357] Received
> NEGOTIATE response from server
> 0323 02:54:39.937079 (+ 5us) client_negotiation.cc:184] Negotiated
> authn=TOKEN
> 0323 02:54:39.937168 (+89us) client_negotiation.cc:473] Sending
> TLS_HANDSHAKE message to server
> 0323 02:54:39.937171 (+ 3us) client_negotiation.cc:246] Sending
> TLS_HANDSHAKE NegotiatePB request
> 0323 02:54:39.937724 (+ 553us) client_negotiation.cc:263] Received
> TLS_HANDSHAKE NegotiatePB response
> 0323 02:54:39.937726 (+ 2us) client_negotiation.cc:486] Received
> TLS_HANDSHAKE response from server
> 0323 02:54:39.937906 (+ 180us) negotiation.cc:304] Negotiation complete:
> Runtime error: Client connection negotiation failed: client connection to
> 127.8.25.194:34669: TLS Handshake error: error:1416F086:SSL
> routines:tls_process_server_certificate:certificate verify
> failed:../ssl/statem/statem_clnt.c:1924
> Metrics:
> {"client-negotiator.queue_time_us":90,"thread_start_us":41,"threads_started":1}
> The python tests were successful before the commit
> https://github.com/apache/kudu/commit/3343144fefaad5a30e95e21297c64c78e308fa1f
> and I tried to remove this commit based on master and then the python tests
> are success, seems the problem introduced by
> https://github.com/apache/kudu/commit/3343144fefaad5a30e95e21297c64c78e308fa1f,
> but I am sorry I can't fix this, could someone help me？Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KUDU-3087) Python tests failed on arm64
[
https://issues.apache.org/jira/browse/KUDU-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17066360#comment-17066360
]
Alexey Serbin commented on KUDU-3087:
-
Thank you for pinging me w.r.t. to the progress on this issue, [~huangtianhua]!
I posted a patch for review: http://gerrit.cloudera.org:8080/15554
> Python tests failed on arm64
>
>
> Key: KUDU-3087
> URL: https://issues.apache.org/jira/browse/KUDU-3087
> Project: Kudu
> Issue Type: Sub-task
>Reporter: huangtianhua
>Assignee: Alexey Serbin
>Priority: Major
> Attachments: python_test.rar
>
>
> I took python tests for kudu on arm64 platform based on
> https://gerrit.cloudera.org/#/c/14964/ the tests failed, error info as
> below:
> W0323 02:54:39.938022 9110 negotiation.cc:313] Failed RPC negotiation. Trace:
> 0323 02:54:39.936597 (+ 0us) reactor.cc:604] Submitting negotiation task
> for client connection to 127.8.25.194:34669
> 0323 02:54:39.936737 (+ 140us) negotiation.cc:98] Waiting for socket to
> connect
> 0323 02:54:39.936746 (+ 9us) client_negotiation.cc:169] Beginning
> negotiation
> 0323 02:54:39.936810 (+64us) client_negotiation.cc:246] Sending NEGOTIATE
> NegotiatePB request
> 0323 02:54:39.937073 (+ 263us) client_negotiation.cc:263] Received
> NEGOTIATE NegotiatePB response
> 0323 02:54:39.937074 (+ 1us) client_negotiation.cc:357] Received
> NEGOTIATE response from server
> 0323 02:54:39.937079 (+ 5us) client_negotiation.cc:184] Negotiated
> authn=TOKEN
> 0323 02:54:39.937168 (+89us) client_negotiation.cc:473] Sending
> TLS_HANDSHAKE message to server
> 0323 02:54:39.937171 (+ 3us) client_negotiation.cc:246] Sending
> TLS_HANDSHAKE NegotiatePB request
> 0323 02:54:39.937724 (+ 553us) client_negotiation.cc:263] Received
> TLS_HANDSHAKE NegotiatePB response
> 0323 02:54:39.937726 (+ 2us) client_negotiation.cc:486] Received
> TLS_HANDSHAKE response from server
> 0323 02:54:39.937906 (+ 180us) negotiation.cc:304] Negotiation complete:
> Runtime error: Client connection negotiation failed: client connection to
> 127.8.25.194:34669: TLS Handshake error: error:1416F086:SSL
> routines:tls_process_server_certificate:certificate verify
> failed:../ssl/statem/statem_clnt.c:1924
> Metrics:
> {"client-negotiator.queue_time_us":90,"thread_start_us":41,"threads_started":1}
> The python tests were successful before the commit
> https://github.com/apache/kudu/commit/3343144fefaad5a30e95e21297c64c78e308fa1f
> and I tried to remove this commit based on master and then the python tests
> are success, seems the problem introduced by
> https://github.com/apache/kudu/commit/3343144fefaad5a30e95e21297c64c78e308fa1f,
> but I am sorry I can't fix this, could someone help me？Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (KUDU-3087) Python tests failed on arm64
[
https://issues.apache.org/jira/browse/KUDU-3087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17066343#comment-17066343
]
huangtianhua commented on KUDU-3087:
[~aserbin], Sorry to disturb you. Is there any progress for this issue? Or
anything I can do for it? Thanks.
> Python tests failed on arm64
>
>
> Key: KUDU-3087
> URL: https://issues.apache.org/jira/browse/KUDU-3087
> Project: Kudu
> Issue Type: Sub-task
>Reporter: huangtianhua
>Assignee: Alexey Serbin
>Priority: Major
> Attachments: python_test.rar
>
>
> I took python tests for kudu on arm64 platform based on
> https://gerrit.cloudera.org/#/c/14964/ the tests failed, error info as
> below:
> W0323 02:54:39.938022 9110 negotiation.cc:313] Failed RPC negotiation. Trace:
> 0323 02:54:39.936597 (+ 0us) reactor.cc:604] Submitting negotiation task
> for client connection to 127.8.25.194:34669
> 0323 02:54:39.936737 (+ 140us) negotiation.cc:98] Waiting for socket to
> connect
> 0323 02:54:39.936746 (+ 9us) client_negotiation.cc:169] Beginning
> negotiation
> 0323 02:54:39.936810 (+64us) client_negotiation.cc:246] Sending NEGOTIATE
> NegotiatePB request
> 0323 02:54:39.937073 (+ 263us) client_negotiation.cc:263] Received
> NEGOTIATE NegotiatePB response
> 0323 02:54:39.937074 (+ 1us) client_negotiation.cc:357] Received
> NEGOTIATE response from server
> 0323 02:54:39.937079 (+ 5us) client_negotiation.cc:184] Negotiated
> authn=TOKEN
> 0323 02:54:39.937168 (+89us) client_negotiation.cc:473] Sending
> TLS_HANDSHAKE message to server
> 0323 02:54:39.937171 (+ 3us) client_negotiation.cc:246] Sending
> TLS_HANDSHAKE NegotiatePB request
> 0323 02:54:39.937724 (+ 553us) client_negotiation.cc:263] Received
> TLS_HANDSHAKE NegotiatePB response
> 0323 02:54:39.937726 (+ 2us) client_negotiation.cc:486] Received
> TLS_HANDSHAKE response from server
> 0323 02:54:39.937906 (+ 180us) negotiation.cc:304] Negotiation complete:
> Runtime error: Client connection negotiation failed: client connection to
> 127.8.25.194:34669: TLS Handshake error: error:1416F086:SSL
> routines:tls_process_server_certificate:certificate verify
> failed:../ssl/statem/statem_clnt.c:1924
> Metrics:
> {"client-negotiator.queue_time_us":90,"thread_start_us":41,"threads_started":1}
> The python tests were successful before the commit
> https://github.com/apache/kudu/commit/3343144fefaad5a30e95e21297c64c78e308fa1f
> and I tried to remove this commit based on master and then the python tests
> are success, seems the problem introduced by
> https://github.com/apache/kudu/commit/3343144fefaad5a30e95e21297c64c78e308fa1f,
> but I am sorry I can't fix this, could someone help me？Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (KUDU-3072) minidump-test failed on aarch64 server
[
https://issues.apache.org/jira/browse/KUDU-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adar Dembo resolved KUDU-3072.
--
Fix Version/s: 1.12.0
Assignee: huangtianhua
Resolution: Fixed
> minidump-test failed on aarch64 server
> --
>
> Key: KUDU-3072
> URL: https://issues.apache.org/jira/browse/KUDU-3072
> Project: Kudu
> Issue Type: Sub-task
>Reporter: huangtianhua
>Assignee: huangtianhua
>Priority: Major
> Fix For: 1.12.0
>
>
> I test kudu on aarch64 server based on https://gerrit.cloudera.org/#/c/14964/
> , the test minidump-test failed, error details info see
> http://paste.openstack.org/show/790470/ :
> [==] Running 8 tests from 2 test cases.
> [--] Global test environment set-up.
> [--] 2 tests from MinidumpDeathTest
> [ RUN ] MinidumpDeathTest.TestRegisterAndDelete
> WARNING: Logging before InitGoogleLogging() is written to STDERR
> I0309 02:17:29.248252 26035 minidump.cc:241] Setting minidump size limit to
> 20M
> [WARNING]
> /home/jenkins/workspace/kudu/thirdparty/src/googletest-release-1.8.0/googletest/src/gtest-death-test.cc:836::
> Death tests use fork(), which is unsafe particularly in a threaded context.
> For this test, Google Test detected 3 threads.
> Wrote minidump to
> /tmp/kudutest-0/minidump-test.MinidumpDeathTest.TestRegisterAndDelete.1583720249245925-26035/minidumps/minidump-test/884bfadb-15be-463e-ab19968c-be52ffe0.dmp
> /home/jenkins/workspace/kudu/src/kudu/util/minidump-test.cc:71: Failure
> Death test: { abort(); }
> Result: died but not with expected error.
> Expected: kudu::MinidumpDeathTest_TestRegisterAndDelete_Test::TestBody()
> Actual msg:
> [ DEATH ] Wrote minidump to
> /tmp/kudutest-0/minidump-test.MinidumpDeathTest.TestRegisterAndDelete.1583720249245925-26035/minidumps/minidump-test/884bfadb-15be-463e-ab19968c-be52ffe0.dmp
> [ DEATH ] *** Aborted at 1583720249 (unix time) try "date -d @1583720249"
> if you are using GNU date ***
> [ DEATH ] PC: @0x0 (unknown)
> [ DEATH ] *** SIGABRT (@0x65b6) received by PID 26038 (TID 0x845d9010)
> from PID 26038; stack trace: ***
> [ DEATH ] @ 0x85875688 ([vdso]+0x687)
> [ DEATH ] @ 0x84cba4d8 raise
> [ DEATH ] @ 0x84cba464 raise
> [ DEATH ]
> I0309 02:17:29.562698 26035 test_util.cc:147]
> ---
> I0309 02:17:29.562726 26035 test_util.cc:148] Had fatal failures, leaving
> test files at
> /tmp/kudutest-0/minidump-test.MinidumpDeathTest.TestRegisterAndDelete.1583720249245925-26035
> [ FAILED ] MinidumpDeathTest.TestRegisterAndDelete (316 ms)
> [ RUN ] MinidumpDeathTest.TestCheckStackTraceAndMinidump
> I0309 02:17:29.563597 26035 minidump.cc:241] Setting minidump size limit to
> 20M
> [WARNING]
> /home/jenkins/workspace/kudu/thirdparty/src/googletest-release-1.8.0/googletest/src/gtest-death-test.cc:836::
> Death tests use fork(), which is unsafe particularly in a threaded context.
> For this test, Google Test detected 3 threads.
> Wrote minidump to
> /tmp/kudutest-0/minidump-test.MinidumpDeathTest.TestCheckStackTraceAndMinidump.1583720249245925-26035/minidumps/minidump-test/578fe2af-ffae-47a9-54c969bb-d909b4b5.dmp
> /home/jenkins/workspace/kudu/src/kudu/util/minidump-test.cc:97: Failure
> Death test: { while (google::_Check_string* _result = google::Check_EQImpl(
> google::GetReferenceableValue(1), google::GetReferenceableValue(0), "1" " "
> "==" " " "0"))
> google::LogMessageFatal("/home/jenkins/workspace/kudu/src/kudu/util/minidump-test.cc",
> 97, google::CheckOpString(_result)).stream(); }
> Result: died but not with expected error.
> Expected:
> kudu::MinidumpDeathTest_TestCheckStackTraceAndMinidump_Test::TestBody()
> Actual msg:
> [ DEATH ] F0309 02:17:29.564812 26042 minidump-test.cc:97] Check failed: 1
> == 0 (1 vs. 0)
> [ DEATH ] *** Check failure stack trace: ***
> [ DEATH ] Wrote minidump to
> /tmp/kudutest-0/minidump-test.MinidumpDeathTest.TestCheckStackTraceAndMinidump.1583720249245925-26035/minidumps/minidump-test/578fe2af-ffae-47a9-54c969bb-d909b4b5.dmp
> [ DEATH ] *** Aborted at 1583720249 (unix time) try "date -d @1583720249"
> if you are using GNU date ***
> [ DEATH ] PC: @0x0 (unknown)
> [ DEATH ] *** SIGABRT (@0x65ba) received by PID 26042 (TID 0x845d9010)
> from PID 26042; stack trace: ***
> [ DEATH ] @ 0x85875688 ([vdso]+0x687)
> [ DEATH ] @ 0x84cba4d8 raise
> [ DEATH ] @ 0x84cba464 raise
> [ DEATH ]
> I0309 02:17:29.752290 26035 test_util.cc:147]
> ---
> I0309 02:17:29.752316 26035 test_util.cc:148] Had fatal failures, leaving
> test files at
> /tmp/kudutest-0/minidump-te
[jira] [Commented] (KUDU-3072) minidump-test failed on aarch64 server
[
https://issues.apache.org/jira/browse/KUDU-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17066008#comment-17066008
]
ASF subversion and git services commented on KUDU-3072:
---
Commit 6dd3fc104198ced9849711c1ed4c860eff75f3bd in kudu's branch
refs/heads/master from huangtianhua
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=6dd3fc1 ]
KUDU-3072 Add glog patch to support stacktrace for aarch64
According to the comments in glog-0.3.5/src/utilities.h,
there are three different ways we can try to get the stack trace:
1) The libunwind library
2) Our hand-coded stack-unwinder
3) The gdb unwinder
We use first way to get stack trace by default, the function
"GetStackTrace" is defined in stacktrace_libunwind-inl.h, but
it doesn't work for aarch64, this changes to use the
implementation of aarch64 which defined in
stacktrace_aarch64-inl.h no matter libunwind exist or not.
I have proposed a PR to google/glog:
github.com/google/glog/pull/529
Change-Id: Ia8ca769b2bef5fa658d56d11b7ac9537fd9ca637
Reviewed-on: http://gerrit.cloudera.org:8080/15420
Reviewed-by: Grant Henke
Tested-by: Kudu Jenkins
> minidump-test failed on aarch64 server
> --
>
> Key: KUDU-3072
> URL: https://issues.apache.org/jira/browse/KUDU-3072
> Project: Kudu
> Issue Type: Sub-task
>Reporter: huangtianhua
>Priority: Major
>
> I test kudu on aarch64 server based on https://gerrit.cloudera.org/#/c/14964/
> , the test minidump-test failed, error details info see
> http://paste.openstack.org/show/790470/ :
> [==] Running 8 tests from 2 test cases.
> [--] Global test environment set-up.
> [--] 2 tests from MinidumpDeathTest
> [ RUN ] MinidumpDeathTest.TestRegisterAndDelete
> WARNING: Logging before InitGoogleLogging() is written to STDERR
> I0309 02:17:29.248252 26035 minidump.cc:241] Setting minidump size limit to
> 20M
> [WARNING]
> /home/jenkins/workspace/kudu/thirdparty/src/googletest-release-1.8.0/googletest/src/gtest-death-test.cc:836::
> Death tests use fork(), which is unsafe particularly in a threaded context.
> For this test, Google Test detected 3 threads.
> Wrote minidump to
> /tmp/kudutest-0/minidump-test.MinidumpDeathTest.TestRegisterAndDelete.1583720249245925-26035/minidumps/minidump-test/884bfadb-15be-463e-ab19968c-be52ffe0.dmp
> /home/jenkins/workspace/kudu/src/kudu/util/minidump-test.cc:71: Failure
> Death test: { abort(); }
> Result: died but not with expected error.
> Expected: kudu::MinidumpDeathTest_TestRegisterAndDelete_Test::TestBody()
> Actual msg:
> [ DEATH ] Wrote minidump to
> /tmp/kudutest-0/minidump-test.MinidumpDeathTest.TestRegisterAndDelete.1583720249245925-26035/minidumps/minidump-test/884bfadb-15be-463e-ab19968c-be52ffe0.dmp
> [ DEATH ] *** Aborted at 1583720249 (unix time) try "date -d @1583720249"
> if you are using GNU date ***
> [ DEATH ] PC: @0x0 (unknown)
> [ DEATH ] *** SIGABRT (@0x65b6) received by PID 26038 (TID 0x845d9010)
> from PID 26038; stack trace: ***
> [ DEATH ] @ 0x85875688 ([vdso]+0x687)
> [ DEATH ] @ 0x84cba4d8 raise
> [ DEATH ] @ 0x84cba464 raise
> [ DEATH ]
> I0309 02:17:29.562698 26035 test_util.cc:147]
> ---
> I0309 02:17:29.562726 26035 test_util.cc:148] Had fatal failures, leaving
> test files at
> /tmp/kudutest-0/minidump-test.MinidumpDeathTest.TestRegisterAndDelete.1583720249245925-26035
> [ FAILED ] MinidumpDeathTest.TestRegisterAndDelete (316 ms)
> [ RUN ] MinidumpDeathTest.TestCheckStackTraceAndMinidump
> I0309 02:17:29.563597 26035 minidump.cc:241] Setting minidump size limit to
> 20M
> [WARNING]
> /home/jenkins/workspace/kudu/thirdparty/src/googletest-release-1.8.0/googletest/src/gtest-death-test.cc:836::
> Death tests use fork(), which is unsafe particularly in a threaded context.
> For this test, Google Test detected 3 threads.
> Wrote minidump to
> /tmp/kudutest-0/minidump-test.MinidumpDeathTest.TestCheckStackTraceAndMinidump.1583720249245925-26035/minidumps/minidump-test/578fe2af-ffae-47a9-54c969bb-d909b4b5.dmp
> /home/jenkins/workspace/kudu/src/kudu/util/minidump-test.cc:97: Failure
> Death test: { while (google::_Check_string* _result = google::Check_EQImpl(
> google::GetReferenceableValue(1), google::GetReferenceableValue(0), "1" " "
> "==" " " "0"))
> google::LogMessageFatal("/home/jenkins/workspace/kudu/src/kudu/util/minidump-test.cc",
> 97, google::CheckOpString(_result)).stream(); }
> Result: died but not with expected error.
> Expected:
> kudu::MinidumpDeathTest_TestCheckStackTraceAndMinidump_Test::TestBody()
> Actual msg:
> [ DEATH ] F0309 02:17:29.564812 26042 minidump-test.cc:97] Check failed: 1
> == 0 (1 vs. 0)
> [ DEATH ] *** Check failure stack
[jira] [Commented] (KUDU-3089) ERROR when running tests on ARM64 server with TSAN or ASAN enabled
[
https://issues.apache.org/jira/browse/KUDU-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17065549#comment-17065549
]
liusheng commented on KUDU-3089:
yes, I will try to ask for help from sanitizer community, the error of TSAN is
same with ASAN.
> ERROR when running tests on ARM64 server with TSAN or ASAN enabled
> --
>
> Key: KUDU-3089
> URL: https://issues.apache.org/jira/browse/KUDU-3089
> Project: Kudu
> Issue Type: Bug
>Reporter: liusheng
>Priority: Major
>
>
> Fow now I am trying to build and test Kudu on ARM server, for Debug build
> type, the building process and almost all tests can pass. but for TSAN and
> ASAN building type, I can build sucessfully, but all the test cases will
> raise follow error.
> {code:java}
> root@kudu-asan2:/opt/kudu/build/asan# bin/kudu-ts-cli-test
> AddressSanitizer:DEADLYSIGNAL
> =
> ==14378==ERROR: AddressSanitizer: SEGV on unknown address 0x (pc
> 0x bp 0xc2649d10 sp 0xc2649d10 T0)
> ==14378==Hint: pc points to the zero page.
> ==14378==The signal is caused by a READ memory access.
> ==14378==Hint: address points to the zero page.AddressSanitizer can not
> provide additional info.
> SUMMARY: AddressSanitizer: SEGV ()
> ==14378==ABORTING
> {code}
> I have struggle for a while but no progress, could anyone help to give any
> suggestion ? thanks a lot!
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (KUDU-3088) build-if-necessary.sh don't rebuild even if thirdparty directory is changed
[ https://issues.apache.org/jira/browse/KUDU-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RuiChen updated KUDU-3088: -- Wired, I can't reproduce the issue in latest master branch, let's close the patch and jira issue first, I will keep eye open it. > build-if-necessary.sh don't rebuild even if thirdparty directory is changed > --- > > Key: KUDU-3088 > URL: https://issues.apache.org/jira/browse/KUDU-3088 > Project: Kudu > Issue Type: Bug > Components: build >Reporter: RuiChen >Priority: Minor > > I update the thirdparty directory in my forked kudu project, and run > *build-if-necessary.sh* , it can't know the changes and don't rebuild > thirdparty libs, I find we use *git ls-tree -d HEAD thirdparty* to check the > changes in git, it will return HASH of directory "*thirdparty*", but actually > it will never be updated after the directory is created, even if the subtree > of directory "thirdparty" have been changed in git. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (KUDU-3088) build-if-necessary.sh don't rebuild even if thirdparty directory is changed
[ https://issues.apache.org/jira/browse/KUDU-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RuiChen closed KUDU-3088. - Resolution: Cannot Reproduce > build-if-necessary.sh don't rebuild even if thirdparty directory is changed > --- > > Key: KUDU-3088 > URL: https://issues.apache.org/jira/browse/KUDU-3088 > Project: Kudu > Issue Type: Bug > Components: build >Reporter: RuiChen >Priority: Minor > > I update the thirdparty directory in my forked kudu project, and run > *build-if-necessary.sh* , it can't know the changes and don't rebuild > thirdparty libs, I find we use *git ls-tree -d HEAD thirdparty* to check the > changes in git, it will return HASH of directory "*thirdparty*", but actually > it will never be updated after the directory is created, even if the subtree > of directory "thirdparty" have been changed in git. -- This message was sent by Atlassian Jira (v8.3.4#803005)
