You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ekaterina Dimitrova (Jira)" <ji...@apache.org> on 2021/07/16 17:41:00 UTC
[jira] [Comment Edited] (CASSANDRA-16736) CQL shell should prefer
newer TLS version by default
[ https://issues.apache.org/jira/browse/CASSANDRA-16736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17382208#comment-17382208 ]
Ekaterina Dimitrova edited comment on CASSANDRA-16736 at 7/16/21, 5:40 PM:
---------------------------------------------------------------------------
[Cassandra 2.2 Patch |https://github.com/apache/cassandra/compare/trunk...ekaterinadimitrova2:16695-2.2] | [DTest patch |https://github.com/ekaterinadimitrova2/cassandra-dtest/commit/67e40a1d0497fc72432816609ab7125989fea073] | [CI |https://jenkins-cm4.apache.org/job/Cassandra-devbranch/942/]
The issue with the cqlsh DTests turned out to be with [this |https://github.com/ekaterinadimitrova2/cassandra-dtest/commit/67e40a1d0497fc72432816609ab7125989fea073#diff-3bea526a144bcaa34c75abdf1527667d2fc0d17f05995effbf891c3becaa1d41R100] fixture.
One thing is that there is a comment that the fixture is needed for only one of the tests but for some still unknown to me reason running the tests with --setup-plan shows that it is applied also to the rest of the tests. I believe this property change does not affect the other tests but I felt I should mention it that the fixture does not really do what it was supposed to do. (and I didn't manage to ix that)
There are still some failing cqlsh tests but they don't seem to be related to this patch and if we decide to fix them, that should be done in follow up tickets.
was (Author: e.dimitrova):
[Cassandra 2.2 Patch |https://github.com/apache/cassandra/compare/trunk...ekaterinadimitrova2:16695-2.2] | [DTest patch |https://github.com/ekaterinadimitrova2/cassandra-dtest/commit/67e40a1d0497fc72432816609ab7125989fea073] | [CI |https://jenkins-cm4.apache.org/job/Cassandra-devbranch/942/]
The issue with the cqlsh DTests turned out to be with [this |https://github.com/ekaterinadimitrova2/cassandra-dtest/commit/67e40a1d0497fc72432816609ab7125989fea073#diff-3bea526a144bcaa34c75abdf1527667d2fc0d17f05995effbf891c3becaa1d41R100] fixture.
One thing is that there is a comment that the fixture is needed for only one of the tests but for some still unknown to me reason running the tests with --setup-plan shows that it is applied also to the rest of the tests. I believe this property change does not affect the other tests but I felt I should mention it that the fixture does not really do what it was supposed to do.
There are still some failing cqlsh tests but they don't seem to be related to this patch and if we decide to fix them, that should be done in follow up tickets.
> CQL shell should prefer newer TLS version by default
> ----------------------------------------------------
>
> Key: CASSANDRA-16736
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16736
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/cqlsh
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 2.2.x
>
>
> This is a follow up to CASSANDRA-16695 where a patch was committed to 3.0, 3.11, 4.0 and trunk.
> As part of it we saw that CQL shell python DTests are failing due to config issues for version 2.2.
> As part of the current ticket we need to produce a fix to be able to run the CQL shell tests and verify and apply the patch from CASSANDRA-16695 to Cassandra 2.2
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org