Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Duplicate
-
None
-
None
-
Code
-
Normal
-
Low Hanging Fruit
-
Unit Test
-
All
-
None
Description
The current 4.0 versioning has a tag to denote that 4.0 isn’t in public release yet (currently beta3). dtest does version parsing which is much more restive and doesn’t support preRelease tags (like the client version parsing does), so skips the 4.0 jar. This then leads to a exception while running the upgrade tests
java.lang.RuntimeException: No v4 versions found at org.apache.cassandra.distributed.impl.Versions.lambda$getLatest$2(Versions.java:166) at java.util.Optional.orElseThrow(Optional.java:290) at org.apache.cassandra.distributed.impl.Versions.getLatest(Versions.java:166) at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) at java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:546) at java.util.stream.AbstractPipeline.evaluateToArrayNode(AbstractPipeline.java:260) at java.util.stream.ReferencePipeline.toArray(ReferencePipeline.java:505) at org.apache.cassandra.distributed.upgrade.UpgradeTestBase$TestCase.upgrade(UpgradeTestBase.java:92) at org.apache.cassandra.distributed.upgrade.UpgradeTest.upgradeTest(UpgradeTest.java:35)
Attachments
Issue Links
- duplicates
-
CASSANDRA-15509 In-jvm upgrade dtest version parsing does not support 4.0 alpha/beta/rc builds
- Resolved