[CASSANDRA-10613] Upgrade test on 2.1->3.0 path fails with NPE in getExistingFiles (likely known bug)

• Type: Sub-task
• Status: Resolved
• Priority: Normal
• Resolution: Not A Problem
• Fix Version/s: 3.0.3
• Assignee: Russ Hatch
• Reporter: Jim Witschey

Authors

Russ Hatch

• Created: 28/Oct/15 15:02
• Updated: 01/Aug/21 12:42
• Resolved: 20/Jan/16 19:10

Description

In this job:

http://cassci.datastax.com/view/Upgrades/job/cassandra_upgrade_2.1_to_3.0_proto_v3/10/

The following tests fail due to an NPE in org.apache.cassandra.db.lifecycle.LogRecord.getExistingFiles:

upgrade_through_versions_test.py:TestUpgrade_from_3_0_latest_tag_to_3_0_HEAD.bootstrap_test
upgrade_through_versions_test.py:TestUpgrade_from_3_0_latest_tag_to_3_0_HEAD.rolling_upgrade_test
upgrade_through_versions_test.py:TestUpgrade_from_3_0_latest_tag_to_3_0_HEAD.parallel_upgrade_with_internode_ssl_test
upgrade_through_versions_test.py:TestUpgrade_from_3_0_latest_tag_to_3_0_HEAD.rolling_upgrade_with_internode_ssl_test
upgrade_through_versions_test.py:TestUpgrade_from_cassandra_2_1_HEAD_to_cassandra_3_0_HEAD.rolling_upgrade_with_internode_ssl_test
upgrade_through_versions_test.py:TestUpgrade_from_3_0_latest_tag_to_3_0_HEAD.parallel_upgrade_test

I believe this is likely happening because of CASSANDRA-10602, so let's hold off on messing with this until that's merged.