@Reynevan & @Hooverdan from the /opt/rockstor directory listing posted it looks like the prior rockstor was uninstalled, likely as part of dependency management/resolution during the presumed zypper dup. This is expected, and we have yet to release our new stable where we can then establish a proper procedure to ease this Leap 15.6 to Leap 16.0 transition, akin to our existing how-tos for this.
So that’s good news - it may well be that a rockstor package re-install can then just pick-up from that DB. But there may be some foot-work involved if the DB from the last instance is in need of a format update. We have a script that does this on rpm install/update when an older format is detected. So any feedback on that script failing would be good of course. Especially with some knowledge of Postgress a-foot :).
Just wanted to pop in this context and to link to the following prior post that also observed the ‘rockstor’ package being uninstalled in a similar scenario. They later move to Leap 16.0 with related SELinux and ‘rockstor’ package uninstalled issued (the linked post).
Note also that before any ‘rockstor’ package install/re-install you should update to the OS specific repo as in the above forum post. We build all rpms in each repo on the indicated OS - to help to ensure compatibility.
Don’t know what’s going on with the dbus service!!
In the future we are going to take-up @Hooverdan advice and go with the now provided CLI update too for future updates - along with guiding folks on who to change our own repos, as we do in our existing/prior “Distribution update from * to *” howo-tos to avoid rockstor being uninstalled at all. We have also, internally, had to adopt a rather heavy handed approach to our package update that addresses issues of Postgres versions being maintained to facilitate DB format updates, see:
Where we added a --force-resolution to our own unattended zypper based Web-UI enacted update that fixed an issue for us at that time when updating from an older install; which was at the very start of our current testing phase so v5.5.0-0 so pertains to the update experience here given this move was from 5.1.0-0 to 5.5.5-0.
Remember that it is important to match our repos to the host OS as we have had to modify slightly our dependencies per OS target. Once we have our next Stable out we can iron all this out hopefully, so that Stable to Stable updates are a more known entity 
.
Hope that helps.