@Vojtech_Vidra First off, welcome to the Rockstor community forum.
The problem you have encountered / reported was as a result of a fairly major change from how Rockstor migrates it’s databases and unfortunately things did not go quite as smoothly as was hoped. Anyway the following forum thread coverts this same issue:
Essence a db migration too place but in your case was not properly registered and so a repeat application is attempted and result in failure and the consequent error: hence the:
Essentially if the output of:
/opt/rockstor/bin/django showmigrations --list
shows the last section, “storageadmin”, as having the “0003_auto_20170114_1332” not been applied (ie no cross by it) ie:
storageadmin
[X] 0001_initial
[X] 0002_auto_20161125_0051
[ ] 0003_auto_20170114_1332
Then the migration system thinks it needs applying and so goes ahead and applies it, but the db then responds with it having already been applied and fails.
Only if your commands output this then you can “fake” apply as per @suman post in that thread:
which should then bring the db migrations system up to date with the actual state. Note that you should not update Rockstor further just yet as there is yet another db migration pending that may complicate things. Best get this sorted first. Though once sorted you should be OK, and if so reboot and check before upgrading further.
Hope that helps and let us know how it goes.