[
https://issues.apache.org/jira/browse/KUDU-3507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881719#comment-17881719
]
ASF subversion and git services commented on KUDU-3507:
-------------------------------------------------------
Commit da30538bd269772cda4a8acefa6579690d14354c in kudu's branch
refs/heads/branch-1.17.x from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=da30538bd ]
KUDU-3507 instruct mini-ranger-{kms} JVM to use IPv4
Per the root cause analysis outlined in another take [1] to address
the issue, it makes sense to limit the network stack of mini-ranger's
and mini-ranger-kms' JVM to IPv4. With that and one more patch [2],
WaitForTcpBind() works as expected and two KMS-related scenarios of the
SecurityITest test now pass where they used to fail before.
[1] https://gerrit.cloudera.org/#/c/20514/
[2] https://gerrit.cloudera.org/#/c/20583/
Change-Id: I2f38a0b7df153108d7072a66813068a764e4e601
Reviewed-on: http://gerrit.cloudera.org:8080/20582
Tested-by: Kudu Jenkins
Reviewed-by: Zoltan Martonka <zmarto...@cloudera.com>
Reviewed-by: Yingchun Lai <laiyingc...@apache.org>
(cherry picked from commit 19fbacfc3685b1ec2ed7f20c0dc22d4bd0618135)
Reviewed-on: http://gerrit.cloudera.org:8080/21791
Reviewed-by: Alexey Serbin <ale...@apache.org>
Tested-by: Abhishek Chennaka <achenn...@cloudera.com>
> TestEncryptionWithKMSIntegration fails in some network configurations
> ---------------------------------------------------------------------
>
> Key: KUDU-3507
> URL: https://issues.apache.org/jira/browse/KUDU-3507
> Project: Kudu
> Issue Type: Bug
> Components: security, test
> Affects Versions: 1.17.0
> Reporter: Alexey Serbin
> Assignee: Alexey Serbin
> Priority: Major
> Fix For: 1.18.0
>
> Attachments: security-itest.txt.xz
>
>
> Scenarios {{TestEncryptionWithKMSIntegration}} and
> {{SecurityITest.TestEncryptionWithKMSIntegrationMultipleServers}} from the
> {{security-itest}} reliably fail in some network configurations. The error
> looks like below:
> {noformat}
> I20230828 12:24:12.427765 20192 mini_ranger_kms.cc:279] Ranger KMS bound to
> 36383
> I20230828 12:24:12.427812 20192 mini_ranger_kms.cc:280] Ranger KMS URL:
> http://127.19.184.20:51048
> I20230828 12:24:12.427848 20192 mini_ranger_kms.cc:206] Time spent starting
> Ranger KMS: real 4.807s user 0.008s sys 0.139s
> I20230828 12:24:12.427896 20192 mini_ranger_kms.cc:388]
> {"name":"kuduclusterkey",
> "cipher":"AES/CTR/NoPadding","length":128,"description":"kuduclusterkey"}
> I20230828 12:24:12.427939 20192 mini_ranger_kms.cc:392]
> 127.19.184.20:36383/kms/
> v1/keys
> E20230828 12:24:12.428130 20192 mini_ranger_kms.cc:397]
> src/kudu/integration-tests/security-itest.cc:993: Failure
> Failed
> Bad status: Network error: Failed to create cluster key: curl error: Couldn't
> connect to server: Failed to connect to 127.19.184.20 port 36383: Connection
> refused
> I20230828 12:24:12.428778 20192 mini_ranger_kms.cc:59] Stopping Ranger KMS...
> I20230828 12:24:12.781246 20192 mini_ranger_kms.cc:61] Stopped Ranger KMS
> {noformat}
> It seems the issue is related to the expected and the actual interface that
> Ranger KMS server binds to.
> I'm attaching full logs of the failed tests scenarios just in case.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
