@nitefly Welcome to the Rockstor community and thanks for helping to support Rockstor development.
Wow that’s quite some jump. Anyway you are right re:
Yes, we change the django migration system mid point and so there is a requirement to ‘stop off’ at an interim release version. That is a direct upgrade, such as you have done (bypassing ver 3.8.15), is broken. Please see the following, now pretty old, forum thread which will hopefully assist:
So if you follow the directions in that post you will hopefully be able to salvage you existing install.
Either that or re-install using the latest iso and then subscribe to stable and then run ‘yum update rockstor’, however I think the generation of the product id has changed since 3.8-12 so you most likely will end up with a new product id and hence will require an activation code transfer to this new product id - plans in the works to do this via self service web page but not there yet. Modern code, such as the most recent iso onwards, generates a persistent product id based on /sys/class/dmi/id/product_uuid to avoid this inconvenience; where a unique motherboard product_uuid is available.
Hope that helps and let us know how you get on. Much has changed since your prior version.