@Hackrus Welcome to the Rockstor community and good day to yourself.
Sorry for the slow response and thanks for reporting your findings.
Yes: this was a rather unfortunate regression bug that ended up in the last stable release. But the good news is that it has now been fixed in our current testing channel updates as of:
via the following issue:
We are in the process of re-thinking our release strategies / timings etc in an attempt to improve on stable release quality / frequency but that is as yet still ‘in flux’.
As per:
the next stable release is pending but otherwise your options are to switch to the testing channel for your updates, which is expected to break often, apply this specific fix by hand: the essence of it is an additional line as per:
followed by a reboot or a rockstor.service restart. I would not advise you attempt this is you are not happy with using the command line in linux and happy to edit python code. But we do include nano which is quite user friendly (use spaces not tabs).
Or await the next stable release.
All of which nicely highlights the reason for re-thinking the release strategy / frequency.
Hope that helps and apologies for not catching this one earlier.