[CASSANDRA-19650] CCM wrongly interprets CASSANDRA_USE_JDK11 for Cassandra 4.x

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.31, 3.11.18, 4.0.14, 4.1.6
• Component/s: Build, Test/dtest/python
• Bug Category: Correctness - Test Failure
• Severity: Normal
• Complexity: Low Hanging Fruit
• Discovered By: DTest
• Platform: All
• Since Version: NA

Source Control Link

https://github.com/riptano/ccm/commit/4aae08061347075f25964db7aebc889719ffc83b

Test and Documentation Plan

manual test

• Assignee: Jacek Lewandowski
• Reporter: Jacek Lewandowski

Authors

Jacek Lewandowski

Reviewers

Michael Semb Wever

• Created: 21/May/24 06:57
• Updated: 19/Jul/24 08:11
• Resolved: 24/May/24 10:59

Description

CCM interprets CASSANDRA_USE_JDK11 only by its existence in the environment rather than by its actual value (true/false).

I can see two solutions:

• make it interpret CASSANDRA_USE_JDK11 properly
• do not take into account CASSANDRA_USE_JDK11 in the current env and set it or unset it automatically when starting a node basing on which Java version was selected

Issue Links

• relates to: CASSANDRA-19636 Fix CCM for Cassandra 5.0 and add arg to the command line which let the user explicitly select JVM
• links to: PR