Cassandra version is always set to '-' instead of '1'

[bsimmons123]

Environment

• Kubernetes:

  Client Version: v1.28.5+k3s1
  Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
  Server Version: v1.28.5+k3s1

• Helm

  version.BuildInfo{Version:"v3.13.1", GitCommit:"3547a4b5bf5edb5478ce352e18858d8a552a4110", GitTreeState:"clean", GoVersion:"go1.20.8"}

• Testrails:

  testrail/apache:7.0.2.1016 -> testrail/apache:7.5.1.7010

• Cassandra/MySQL:

  testrail/mysql:default && testrail/cassandra:default

Whats the Issue

When I try to update from Testrail v7.0.1.1013 to v7.5.1.7010 I get stuck in a loop with the updater.

It initially loads stating that my database version (MySQL) is currently set to 20210320140000 and it wants to update it to 20220425000001, and it states that my Cassandra version is - and the new version is 1. It will run through the updater and tell me that it was a successful update (Only updating the database version (MySQL)) and that i can go to testrail to login, but when i try to transition back to the login screen it pushes me back to the updater stating that Cassandra is still set to - instead of 1

Workarounds

I can exec into the pod that is running the mysql instance and insert the following into the settings table:

insert into settings (name, value) values ('cassandra_version', 1);

After inserting this into the settings table, if i transition back to the Testrail UI and reload the page it'll work like a charm.

Closing

Is there something I am doing wrong here that is causing this update process to act this way? I haven't seen any of this behavior documented in the documentation and I don't think I should have to manually update the database to get the application to work properly. Any help would be appreciated!

[MedUnes]

yes confirmed to solve the issue for me out of curiosity @bsimmons123, how did you come to the solution that you should insert that setting with that value to the settings Table? thanks.

[bsimmons123]

I started and stopped a LOT of different versions of testrails and checked the sql entries for that settings table on all versions and determined that was the one difference. I'm glad that did the trick for you, hopefully this is fixed in their future versions