Beyond Leap 15.6: will Rockstor use Leap 16, MicroOS, Slowroll

simon-77 · November 24, 2025, 10:20am

As I am thinking about some changes to my Rockstor Server, I am also curiouse about the plans of Rockstor in moving beyond openSUSE Leap 15.6 (which is only maintained till April 2026).

Is there already a discussion (or decission), what the next “recommended” base system will be?

Simply Leap 16.0
Is the new openSUSE MicroOS distro on the table for discussion?
Or maybe remove the whole OS version dependency by using slowroll?

As I could not find a discussion neither in the forums nor on github, and as the end of Leap 15.6 is approaching, I am just curiouse about the plans of Rockstor moving forward.

Cheers
Simon

Flox · November 24, 2025, 4:43pm

Great points to bring up, @simon-77 !

These are questions we constantly ask ourselves but there’s unfortunately no quick answer. I’ll thus take the time to reply properly a bit later today as I’m currently a bit short on time at this very moment, I’m afraid.

John1 · December 17, 2025, 3:51pm

Depending on how slow the roll is in the rolling release, may affect stability of the Rockstor software as a NAS appliance. If the rolling release is too fast it will definitely affect stability of the Rockstor NAS software. Using rolling releases can also introduce breakage even more so than stable, which would require more testing before each release build.

Flox · December 23, 2025, 2:57pm

First off, my sincere apologies for such a delay in getting back to you, @simon-77.

This is an important topic (thank you so much for your interest in it and for taking the time to bring it up) and as I mentioned in my previous message, we are constantly asking ourselves these questions. The short answer to your questions could be “yes” but that would be overly simplistic and hide a lot of the reality. It actually does follow a simple logic, but the road is a bit more complex, of course. I’ll thus try to share my current train of thoughts on that logic in an attempt to illustrate that point thoughts on each of the different options you’ve listed.

Before I do that, though, and as you prefaced it yourself, this is all in the context of the upcoming end-of-life of Leap 15.6. While this was originally scheduled to be by the end of this year if I remember correctly, it has been pushed by a few months and Leap 15.6 will be “maintained until at least April 2026” (Lifetime - openSUSE Wiki).

Now that we have a timeframe set, let’s briefly discuss the options you listed as these are indeed exactly those that need to be considered:

This is indeed the most natural next step for us given Leap is our current main target. Leap 16, however, does come with some requirements that explain why we have not yet released an rpm for it. @phillxnet recently detailed this well in a Github issue (Missing build dependencies #101 by phillxnet · Pull Request #104 · rockstor/rockstor-rpmbuild · GitHub) but the gist of it is as follows: the only python version available on Leap 16 is 3.13, which means Rockstor needs to be running on Python 3.13, which requires a Django upgrade, which itself requires us to upgrade our dependencies. We started that work but that’s a substantial upgrade throughout the project (rockstor-core, but also our rpm build, ISO build, our infrastructure); this and its related issues are part of milestones: GitHub · Where software is built and GitHub · Where software is built.
Of note, there is no overlapping Python version between Leap 15.6 and Leap 16, which further complicates things as we now need to maintain two pipelines, one for 15.6 and a different one for 16.
This is all good, though, as all these upgrades were planned and we’ve already accomplished many of them; it just explains why we don’t yet have a Leap 16 release.

There is also an important point about Leap 16, one that is unrelated to Rockstor: the openSUSE release summary explains it well:

The hardware requirements have changed. Leap 16 now requires x86-64-v2 as a minimum CPU architecture level, which generally means CPUs bought in 2008 or later. Users with older hardware can migrate to Slowroll or Tumbleweed.

It’s unclear how many Rockstor users will be impacted by it; maybe not many but it is something to keep in mind.

That brings us to the next target you mentioned:

We’ve had the exact same thought and it is something I’ve been personally excited about. On paper, it seems to match exactly what we would need and that’s why we’ve included it as one of our targets (although for advanced users for now: Downloads). It is, unfortunately, not a universal solution. We would lose aarch64 compatibility if we were to focus exclusively on Slowroll as no arm builds/repositories are available at the moment and it is unclear when/if this would happen. There are also a few other points of concerns and uncertainty that do tone down my excitement about it for the moment.

Last but not least:

Yes, this is something that has been in the back of our head (MicroOS or Leap micro). It has been brought up a little while ago and @phillxnet did detail the points we needed to consider at the time: Base on openSUSE MicroOS · Issue #2217 · rockstor/rockstor-core · GitHub. It definitely is an interesting option but while we’re closer to being able to actually consider it, we are not quite there yet, I think.

We are a small team and as you can see from the above, there already are a lot of targets and architectures that we do need to support and provide releases so we unfortunately need to remain realistic in our choices. We’re making substantial improvements in our infrastructure and much progress to ease the workload required for each rpm release and target but each still requires a lot of work so we’re trying to be careful and not stretch ourselves too thin.

The openSUSE project is moving fast and making a lot of exciting releases. It does come with its own “pain points” at times as there’s a lot to do, but it’s great to have all these options at our disposal too!

I probably rambled a bit too much (and sorry again for taking such a long time to get back to you), but I hope I was able to provide some elements of answer.

aremiaskfa · December 23, 2025, 8:13pm

Interesting! I didn’t know that microarchitectures are a thing.

I am -v3 compatible it seems.

Thanks for the write-up.

simon-77 · December 26, 2025, 9:57pm

Thanky you @Flox for taking your time writing this insightfull post and taking us behind the scenes.

After reading about all the hurdels regarding the different python versions and supported CPU architectures, I can definitely imagine that the choise of the right openSUSE OS is not as straight forward as it might seem in the first place.

Of course I do understand the relevance of stable release distributions for servers, though I think that openSUSE did release two ingeniouse distros with MicroOS and Slowroll, that sound really promising for servers too.

About 2 years ago I set up another server with openSUSE MicroOS and I was amazed how easy the installation and setup procedure was and how stable the daily automatic updates did go, including the possibility to roll back to a previouse version. I would actually be very keen on trying that distro on my rockstor server tpp, once it does get compatible.

Regarding Slowroll, I assume that it might be a more balance middle ground as server OS, though I would think of Slowroll more as a Leap with faster release cycles than a slower Tumbleweed . I would actually love to see the future of Rockstor beeing built on Slowroll, though I was not aware of the limitations regarding available CPU architectures, which is very unfortunate.

Cheers and merry christmas
Simon

simon-77 · May 9, 2026, 5:48pm

Hi Folks

Just want to catch up on how to update a running rockstor server, as I am a bit confused …

On one hand, you have the Testing Channel Announcements about V5.5 RC2 built on Leap 16.0 and also the overview table suggesting that V5.5 is the “testing” channel currently for Leap 15.6 & 16.0

But on my (Backup) Rockstor server with the testing channel enabled, I do not get any update options:

Additionally, as Leap 15.6 is now definitely EOL, I would actually prefere upgrading to Leap 16.0, but I could find no information for this, neither in the forum nor in the how-tos.

I would appreciate some information on how to update or links to according instructions in case I missed them.

Cheers Simon

Hooverdan · May 9, 2026, 10:58pm

I’ll let @phillxnet provide the more in-depth answer.

I am curious why you’re not seeing any testing channel updates on your backup Rockstor server. Did you find anything in the logs related to zypper timing out when it is attempting to look for upgradable packages? Or do you get the non-Rockstor updates just fine, just not the Rockstor testing update offering?

A couple of points from my side:
I believe, the Leap 16.0 iso rollout will become available with the next stable release, which will hopefully not be too far off.

In the meantime, for testing, to upgrade from Leap 15.6 to Leap 16.0, I’ve used the command line based OpenSuse migration tool.

You can run it first as a dry run using:

opensuse-migration-tool --dry-run

and then without the dry-run option.

The caveat is:
Since there is no current 16.0 specific repo available here yet, I stuck with the “old” 15.6 for now. Still seems to work.

To force the rockstor update, you can use zypper directly as well (but the correct update channel has to be set first, as the repository changes (you also want to do that before you perform the distribution upgrade).

Checking on my 16.0 test system, I see this in the “normal updates” (the blinking radio signal next to the OpenSUSE version (I set this one to the Edge channel, moving from testing):

This is as expected. It will not update the Rockstor version, but shows that there is an update. Taking a look at the what’s happening in the background (checking the root mailbox):

Specified lock has been successfully added.
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...

The following item is locked and will not be changed by any action:
 Installed:
  rockstor

The following package update will NOT be installed:
  rockstor

The following 11 packages are going to be upgraded:
  apparmor-abstractions apparmor-parser apparmor-profiles dracut-kiwi-lib dracut-kiwi-oem-dump dracut-kiwi-oem-repart iproute2 libapparmor1 libcares2 libselinux1 libselinux-devel

11 packages to upgrade.

Package download size:     5.6 MiB

Package install size change:
              |       5.9 MiB  required by packages that will be installed
    42.0 KiB  |  -    5.8 MiB  released by packages that will be removed

Interestingly however, there is still no notification in the Software update WebUI screen, so that appears similar to your experience.

After the update of all of the other packages and a subsequent reboot, there is now only one Update listed (but still not “software update”):

All I can see in the log after switching from dashboard to the Software Update screen is:

[09/May/2026 15:33:20] INFO [zypper_changelog_lib.zyppchangelog:130] Zypper locked: attempt 1, retrying in 1s.
[09/May/2026 15:33:21] INFO [zypper_changelog_lib.zyppchangelog:130] Zypper locked: attempt 2, retrying in 1s.
[09/May/2026 15:33:22] INFO [zypper_changelog_lib.zyppchangelog:130] Zypper locked: attempt 3, retrying in 1s.

though when executing e.g. zypper info rockstor, no locking is occuring.

After a few manual screen refreshes, finally the latest “edge” package is announced:

And the rockstor log shows:

[09/May/2026 15:33:20] INFO [zypper_changelog_lib.zyppchangelog:130] Zypper locked: attempt 1, retrying in 1s.
[09/May/2026 15:33:21] INFO [zypper_changelog_lib.zyppchangelog:130] Zypper locked: attempt 2, retrying in 1s.
[09/May/2026 15:33:22] INFO [zypper_changelog_lib.zyppchangelog:130] Zypper locked: attempt 3, retrying in 1s.
[09/May/2026 15:43:28] INFO [system.pkg_mgmt:621] Skipped fetching updates, zypper busy.
[09/May/2026 15:45:00] INFO [system.pkg_mgmt:621] Skipped fetching updates, zypper busy.
[09/May/2026 15:45:02] INFO [zypper_changelog_lib.zyppchangelog:527] Assuming repo requires no authentication

In any case, you can still use zypper up --no-recommends to see the latest package for rockstor:

Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...

The following package is going to be upgraded:
  rockstor

1 package to upgrade.

Package download size:     2.2 MiB

Package install size change:
              |       6.6 MiB  required by packages that will be installed
   -12.3 KiB  |  -    6.6 MiB  released by packages that will be removed

Backend:  classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y):

After the installation (and a little waiting for the bootstrap tasks to complete) and going back to the WebUI (and login), the new version shows up:

For my “production” system, I am planning to do an in-place upgrade first (like described above but likely using testing channel), but once the stable version comes with a Leap 16.0, I might go and just do a fresh re-install (taking advantage of the config backup) to clean out other stuff I might have installed via the command line unrelated to Rockstor and start afresh …

That was probably way more detail than you were looking for, sorry.

simon-77 · May 11, 2026, 7:41am

Thank you @Hooverdan for the prompt reply

Regarding the logs - although I did find some older errors related to zypper, I couldn’t find anything recent, with the latest log lines:

[04/May/2026 04:15:05] INFO [storageadmin.tasks:63] Task [start_balance], id: 616ad992-f32d-49b7-907f-e9c701163fbd completed OK
[04/May/2026 04:15:05] INFO [storageadmin.tasks:66] Updating end_time accordingly to 2026-05-04 02:15:05.064579+00:00
[04/May/2026 04:15:05] INFO [storageadmin.tasks:55] Now executing Huey task [update_end_time], id: 82e879a9-90ff-496c-b6a9-625f1e0f241f.
[04/May/2026 04:15:05] INFO [storageadmin.tasks:63] Task [update_end_time], id: 82e879a9-90ff-496c-b6a9-625f1e0f241f completed OK
[09/May/2026 19:29:40] ERROR [system.pkg_mgmt:575] Consider applying updates to reduce backlog: Command '['zypper', '--xmlout', 'list-updates']' timed out after 15 seconds
[09/May/2026 19:33:05] INFO [system.pkg_mgmt:344] ++ switch_repo(Testing, enable_repo=True) called.
[09/May/2026 19:33:05] INFO [system.pkg_mgmt:414] *** Testing already enabled.
[09/May/2026 19:33:27] INFO [system.pkg_mgmt:344] ++ switch_repo(Testing, enable_repo=True) called.
[09/May/2026 19:33:27] INFO [system.pkg_mgmt:414] *** Testing already enabled.
[09/May/2026 19:33:43] ERROR [system.pkg_mgmt:575] Consider applying updates to reduce backlog: Command '['zypper', '--xmlout', 'list-updates']' timed out after 15 seconds
[09/May/2026 19:35:03] INFO [system.pkg_mgmt:344] ++ switch_repo(Testing, enable_repo=True) called.
[09/May/2026 19:35:03] INFO [system.pkg_mgmt:414] *** Testing already enabled.
[09/May/2026 19:35:19] ERROR [system.pkg_mgmt:575] Consider applying updates to reduce backlog: Command '['zypper', '--xmlout', 'list-updates']' timed out after 15 seconds
[09/May/2026 19:44:29] INFO [system.pkg_mgmt:344] ++ switch_repo(Testing, enable_repo=True) called.
[09/May/2026 19:44:29] INFO [system.pkg_mgmt:414] *** Testing already enabled.
[09/May/2026 19:44:45] ERROR [system.pkg_mgmt:575] Consider applying updates to reduce backlog: Command '['zypper', '--xmlout', 'list-updates']' timed out after 15 seconds
[11/May/2026 09:24:10] ERROR [system.pkg_mgmt:575] Consider applying updates to reduce backlog: Command '['zypper', '--xmlout', 'list-updates']' timed out after 15 seconds

… although I don’t remember that I would have manually switched the channel in the last days

Feel free to take a look at my logs here: [11/Oct/2025 16:47:29] INFO [scripts.initrock:525] Creating openssl cert...[11 - Pastebin.com

Interestingly enough, the manual update did proceed without any complications, but it did not update rockstor too …

sudo zypper up --no-recommends 
Loading repository data...
Reading installed packages...

The following 13 package updates will NOT be installed:
  btrfsmaintenance btrfsprogs btrfsprogs-udev-rules e2fsprogs gptfdisk libbtrfs0 libcom_err-devel libcom_err2 libext2fs2 libfuse2 ntfs-3g rockstor xfsprogs

The following 143 packages are going to be upgraded:
  NetworkManager NetworkManager-branding-upstream NetworkManager-tui adcli apparmor-parser avahi bind-utils ca-certificates-mozilla containerd crypto-policies cups-config curl
  docker docker-buildx dracut-kiwi-lib dracut-kiwi-oem-dump dracut-kiwi-oem-repart git git-core glib2-devel glib2-tools glibc glibc-devel glibc-locale glibc-locale-base gpg2
  grub2 grub2-branding-upstream grub2-i386-pc grub2-snapper-plugin grub2-x86_64-efi haveged kpartx libapparmor1 libatomic1 libavahi-client3 libavahi-common3 libavahi-core7
  libblkid-devel libblkid1 libcups2 libcurl4 libdns_sd libecpg6 libexpat1 libfdisk1 libfreebl3 libgcc_s1 libgio-2_0-0 libglib-2_0-0 libgmodule-2_0-0 libgnutls30 libgobject-2_0-0
  libgomp1 libgthread-2_0-0 libhavege2 libitm1 libldap-2_4-2 libldap-data liblsan0 libmount-devel libmount1 libnfsidmap1 libnghttp2-14 libnm0 libopensm9 libopenssl-3-devel
  libopenssl1_1 libopenssl3 libosmcomp5 libosmvendor5 libpng16-16 libpolkit-agent-1-0 libpolkit-gobject-1-0 libpq5 libpython3_11-1_0 libpython3_6m1_0 libsmartcols1 libsnmp40
  libsodium23 libsoftokn3 libsqlite3-0 libssh-config libssh4 libsss_certmap0 libsss_idmap0 libsss_nss_idmap0 libstdc++6 libsystemd0 libtasn1 libtasn1-6 libudev1 libusb-0_1-4
  libuuid1 libwebp7 libxml2-2 libxml2-devel libxml2-tools libxslt-devel libxslt-tools libxslt1 libz1 login_defs mdadm mozilla-nss mozilla-nss-certs net-snmp nfs-client
  nfs-kernel-server openssl-3 perl-Git perl-SNMP polkit python3 python3-base python3-sssd-config python311 python311-base python311-devel rsync runc shadow shim snmp-mibs
  sqlite3-tcl sssd sssd-ad sssd-dbus sssd-krb5-common sssd-ldap sssd-tools suse-module-tools systemd systemd-sysvcompat tar typelib-1_0-NM-1_0 udev util-linux util-linux-systemd
  vim vim-data-common xen-libs zlib-devel

The following 3 NEW packages are going to be installed:
  kernel-default-6.4.0-150600.23.100.1 libldap-2_5-0 libsubid5

The following package requires a system reboot:
  kernel-default-6.4.0-150600.23.100.1

143 packages to upgrade, 3 new.

Package download size:
              |     283.4 MiB  overall package size
   160.0 MiB  |  -  123.4 MiB  already in cache

Package install size change:
              |     994.8 MiB  required by packages that will be installed
   190.7 MiB  |  -  804.2 MiB  released by packages that will be removed

    Note: System reboot required.

Backend:  classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y):

Cheers Simon

simon-77 · May 11, 2026, 8:32am

I just had another look into the update issue with rockstor:

rockstor repo is enabled:

$ zypper lr -dE
#  | Alias                              | Name                               | Enabled | GPG Check | Refresh | Keep | Priority | Type   | URI                                                                                                | Service
---+------------------------------------+------------------------------------+---------+-----------+---------+------+----------+--------+----------------------------------------------------------------------------------------------------+--------
 1 | Leap_15_6                          | Leap_15_6                          | Yes     | (r ) Yes  | Yes     | Yes  |   99     | rpm-md | http://download.opensuse.org/distribution/leap/15.6/repo/oss/                                      | 
 2 | Leap_15_6_Updates                  | Leap_15_6_Updates                  | Yes     | (r ) Yes  | Yes     | Yes  |   99     | rpm-md | https://download.opensuse.org/update/leap/15.6/oss/                                                | 
 3 | Rockstor-Testing                   | Rockstor-Testing                   | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md | http://updates.rockstor.com:8999/rockstor-testing/leap/15.6                                        | 
 4 | Virtualization_Appliances_Builder  | Virtualization_Appliances_Builder  | Yes     | (r ) Yes  | Yes     | Yes  |   99     | rpm-md | https://download.opensuse.org/repositories/Virtualization:/Appliances:/Builder/openSUSE_Leap_15.6/ | 
 5 | filesystems                        | Filesystem tools and FUSE-relate-> | Yes     | (r ) Yes  | No      | -    |  200     | rpm-md | https://download.opensuse.org/repositories/filesystems/15.6/                                       | 
 6 | home_rockstor                      | home_rockstor                      | Yes     | (r ) Yes  | Yes     | Yes  |  105     | rpm-md | https://download.opensuse.org/repositories/home:/rockstor/15.6/                                    | 
 7 | home_rockstor_branches_Base_System | home_rockstor_branches_Base_System | Yes     | (r ) Yes  | Yes     | Yes  |   97     | rpm-md | https://download.opensuse.org/repositories/home:/rockstor:/branches:/Base:/System/15.6/            | 
 9 | repo-backports-update              | Update repository of openSUSE Ba-> | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md | http://download.opensuse.org/update/leap/15.6/backports/                                           | 
10 | repo-openh264                      | repo-openh264                      | Yes     | (r ) Yes  | Yes     | Yes  |   99     | rpm-md | http://codecs.opensuse.org/openh264/openSUSE_Leap                                                  | 
12 | repo-sle-update                    | Update repository with updates f-> | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md | http://download.opensuse.org/update/leap/15.6/sle/

Newer versions are listed:

$ zypper pa -r Rockstor-Testing
Loading repository data...
Reading installed packages...
S  | Repository       | Name     | Version  | Arch
---+------------------+----------+----------+-------
v  | Rockstor-Testing | rockstor | 5.5.3-0  | x86_64
v  | Rockstor-Testing | rockstor | 5.5.2-1  | x86_64
v  | Rockstor-Testing | rockstor | 5.5.1-0  | x86_64
v  | Rockstor-Testing | rockstor | 5.5.0-0  | x86_64
i+ | Rockstor-Testing | rockstor | 5.1.0-0  | x86_64
v  | Rockstor-Testing | rockstor | 5.0.15-0 | x86_64
v  | Rockstor-Testing | rockstor | 5.0.14-0 | x86_64
v  | Rockstor-Testing | rockstor | 5.0.13-0 | x86_64
v  | Rockstor-Testing | rockstor | 5.0.12-0 | x86_64
v  | Rockstor-Testing | rockstor | 5.0.11-0 | x86_64
v  | Rockstor-Testing | rockstor | 5.0.10-0 | x86_64
v  | Rockstor-Testing | rockstor | 5.0.9-0  | x86_64
v  | Rockstor-Testing | rockstor | 5.0.8-0  | x86_64

not even a zypper dup would try to update rockstor:

$ sudo zypper dup
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...
Nothing to do.

When updating it manually, I have to upgrade postgres

$ sudo zypper up rockstor
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: 1: the to be installed rockstor-5.5.3-0.x86_64 requires 'postgresql17-devel', but this requirement cannot be provided
not installable providers: postgresql17-devel-17.2-150600.13.5.1.x86_64[repo-sle-update]
                   postgresql17-devel-17.4-150600.13.10.1.x86_64[repo-sle-update]
                   postgresql17-devel-17.5-150600.13.13.1.x86_64[repo-sle-update]
                   postgresql17-devel-17.6-150600.13.16.1.x86_64[repo-sle-update]
                   postgresql17-devel-17.7-150600.13.19.1.x86_64[repo-sle-update]
                   postgresql17-devel-17.9-150600.13.24.1.x86_64[repo-sle-update]

 Solution 1: Following actions will be done:
  deinstallation of postgresql13-devel-13.23-150600.14.14.1.x86_64
  deinstallation of postgresql13-server-devel-13.23-150600.14.14.1.x86_64
 Solution 2: do not install rockstor-5.5.3-0.x86_64
 Solution 3: break rockstor-5.5.3-0.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): 1

Resolving dependencies...
Resolving package dependencies...

The following package is going to be upgraded:
  rockstor

The following 8 NEW packages are going to be installed:
  lsb-release postgresql17 postgresql17-contrib postgresql17-devel postgresql17-server postgresql17-server-devel python3-rpm whois

The following 2 packages are going to be REMOVED:
  postgresql13-devel postgresql13-server-devel

1 package to upgrade, 8 new, 2 to remove.

Package download size:    12.9 MiB

Package install size change:
              |      56.5 MiB  required by packages that will be installed
    42.3 MiB  |  -   14.2 MiB  released by packages that will be removed

Backend:  classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): 
Retrieving: lsb-release-3.1-1.16.noarch (Leap_15_6)                                                                                                           (1/9),  19.8 KiB    
Retrieving: lsb-release-3.1-1.16.noarch.rpm ................................................................................................................................[done]
Retrieving: whois-5.5.20-150600.1.4.x86_64 (Leap_15_6)                                                                                                        (2/9), 106.9 KiB    
Retrieving: whois-5.5.20-150600.1.4.x86_64.rpm .............................................................................................................................[done]
Retrieving: postgresql17-17.9-150600.13.24.1.x86_64 (Update repository with updates from SUSE Linux Enterprise 15)                                            (3/9),   2.0 MiB    
Retrieving: postgresql17-17.9-150600.13.24.1.x86_64.rpm ........................................................................................................[done (1.5 MiB/s)]
Retrieving: python3-rpm-4.14.3-150400.59.16.1.x86_64 (Update repository with updates from SUSE Linux Enterprise 15)                                           (4/9),  56.2 KiB    
Retrieving: python3-rpm-4.14.3-150400.59.16.1.x86_64.rpm ...................................................................................................................[done]
Retrieving: postgresql17-server-17.9-150600.13.24.1.x86_64 (Update repository with updates from SUSE Linux Enterprise 15)                                     (5/9),   5.7 MiB    
Retrieving: postgresql17-server-17.9-150600.13.24.1.x86_64.rpm .................................................................................................[done (5.0 MiB/s)]
Retrieving: postgresql17-contrib-17.9-150600.13.24.1.x86_64 (Update repository with updates from SUSE Linux Enterprise 15)                                    (6/9), 764.7 KiB    
Retrieving: postgresql17-contrib-17.9-150600.13.24.1.x86_64.rpm ..............................................................................................[done (450.2 KiB/s)]
Retrieving: postgresql17-devel-17.9-150600.13.24.1.x86_64 (Update repository with updates from SUSE Linux Enterprise 15)                                      (7/9), 304.0 KiB    
Retrieving: postgresql17-devel-17.9-150600.13.24.1.x86_64.rpm ................................................................................................[done (256.3 KiB/s)]
Retrieving: postgresql17-server-devel-17.9-150600.13.24.1.x86_64 (Update repository with updates from SUSE Linux Enterprise 15)                               (8/9),   1.9 MiB    
Retrieving: postgresql17-server-devel-17.9-150600.13.24.1.x86_64.rpm ...........................................................................................[done (1.7 MiB/s)]
Retrieving: rockstor-5.5.3-0.x86_64 (Rockstor-Testing)                                                                                                        (9/9),   2.1 MiB    
Retrieving: rockstor-5.5.3-0.x86_64.rpm ........................................................................................................................[done (1.3 MiB/s)]

Checking for file conflicts: ...............................................................................................................................................[done]
( 1/11) Installing: lsb-release-3.1-1.16.noarch ............................................................................................................................[done]
( 2/11) Installing: whois-5.5.20-150600.1.4.x86_64 .........................................................................................................................[done]
( 3/11) Installing: postgresql17-17.9-150600.13.24.1.x86_64 ................................................................................................................[done]
( 4/11) Installing: python3-rpm-4.14.3-150400.59.16.1.x86_64 ...............................................................................................................[done]
( 5/11) Installing: postgresql17-server-17.9-150600.13.24.1.x86_64 .........................................................................................................[done]
( 6/11) Installing: postgresql17-contrib-17.9-150600.13.24.1.x86_64 ........................................................................................................[done]
( 7/11) Installing: postgresql17-devel-17.9-150600.13.24.1.x86_64 ..........................................................................................................[done]
( 8/11) Installing: postgresql17-server-devel-17.9-150600.13.24.1.x86_64 ...................................................................................................[done]
Failed to stop rockstor-scheduling.service: Unit rockstor-scheduling.service not loaded.
Failed to stop rockstor-replication.service: Unit rockstor-replication.service not loaded.
Failed to stop rockstor-collector.service: Unit rockstor-collector.service not loaded.
Copying contents of static/config-backups to config-backups-rpmsave.
update-alternatives: using /usr/lib/postgresql17 to provide /usr/lib/postgresql (postgresql) in manual mode
( 9/11) Installing: rockstor-5.5.3-0.x86_64 ................................................................................................................................[done]
(10/11) Removing: postgresql13-server-devel-13.23-150600.14.14.1.x86_64 ....................................................................................................[done]
(11/11) Removing: postgresql13-devel-13.23-150600.14.14.1.x86_64 ...........................................................................................................[done]
%posttrans(rockstor-5.5.3-0.x86_64) script output:
Current DB format is already 13.
Updating DB format from 13 to 17 via /usr/lib/postgresql17/bin/pg_upgrade.
/var/lib/pgsql /

Adopting installs' LANG=en_US.UTF-8
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.UTF-8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

creating directory /var/lib/pgsql/data17 ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default "max_connections" ... 100
selecting default "shared_buffers" ... 128MB
selecting default time zone ... Europe/Vienna
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

initdb: warning: enabling "trust" authentication for local connections
initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.

Success. You can now start the database server using:

    /usr/lib/postgresql17/bin/pg_ctl -D /var/lib/pgsql/data17 -l logfile start

Stopping postgresql systemd service

mv /var/lib/pgsql/data /var/lib/pgsql/data13

Performing Consistency Checks
-----------------------------
Checking cluster versions                                     ok
Checking database user is the install user                    ok
Checking database connection settings                         ok
Checking for prepared transactions                            ok
Checking for contrib/isn with bigint-passing mismatch         ok
Checking data type usage                                      ok
Checking for user-defined encoding conversions                ok
Checking for user-defined postfix operators                   ok
Checking for incompatible polymorphic functions               ok
Checking for not-null constraint inconsistencies              ok
Creating dump of global objects                               ok
Creating dump of database schemas                             ok
Checking for presence of required libraries                   ok
Checking database user is the install user                    ok
Checking for prepared transactions                            ok
Checking for new cluster tablespace directories               ok

If pg_upgrade fails after this point, you must re-initdb the
new cluster before continuing.

Performing Upgrade
------------------
Setting locale and encoding for new cluster                   ok
Analyzing all rows in the new cluster                         ok
Freezing all rows in the new cluster                          ok
Deleting files from new pg_xact                               ok
Copying old pg_xact to new server                             ok
Setting oldest XID for new cluster                            ok
Setting next transaction ID and epoch for new cluster         ok
Deleting files from new pg_multixact/offsets                  ok
Copying old pg_multixact/offsets to new server                ok
Deleting files from new pg_multixact/members                  ok
Copying old pg_multixact/members to new server                ok
Setting next multixact ID and offset for new cluster          ok
Resetting WAL archives                                        ok
Setting frozenxid and minmxid counters in new cluster         ok
Restoring global objects in the new cluster                   ok
Restoring database schemas in the new cluster                 ok
Copying user relation files                                   ok
Setting next OID for new cluster                              ok
Sync data directory to disk                                   ok
Creating script to delete old cluster                         ok
Checking for extension updates                                ok

Upgrade Complete
----------------
Optimizer statistics are not transferred by pg_upgrade.
Once you start the new server, consider running:
    /usr/lib/postgresql17/bin/vacuumdb --all --analyze-in-stages
Running this script will delete the old cluster's data files:
    ./delete_old_cluster.sh

Linking data -> data17

Starting postgresql systemd service

Running /usr/lib/postgresql17/bin/vacuumdb
vacuumdb: processing database "postgres": Generating minimal optimizer statistics (1 target)
vacuumdb: processing database "smartdb": Generating minimal optimizer statistics (1 target)
vacuumdb: processing database "storageadmin": Generating minimal optimizer statistics (1 target)
vacuumdb: processing database "template1": Generating minimal optimizer statistics (1 target)
vacuumdb: processing database "postgres": Generating medium optimizer statistics (10 targets)
vacuumdb: processing database "smartdb": Generating medium optimizer statistics (10 targets)
vacuumdb: processing database "storageadmin": Generating medium optimizer statistics (10 targets)
vacuumdb: processing database "template1": Generating medium optimizer statistics (10 targets)
vacuumdb: processing database "postgres": Generating default (full) optimizer statistics
vacuumdb: processing database "smartdb": Generating default (full) optimizer statistics
vacuumdb: processing database "storageadmin": Generating default (full) optimizer statistics
vacuumdb: processing database "template1": Generating default (full) optimizer statistics

Running /usr/lib/postgresql17/bin/reindexdb
reindexdb: reindexing database "postgres"
reindexdb: reindexing database "smartdb"
reindexdb: reindexing database "storageadmin"
reindexdb: reindexing database "template1"

Restoring pior pwd
/

All Rockstor services, if running, will have been stopped.
Restart via 'systemctl start rockstor-bootstrap.service'
Restoring config-backups-rpmsave contents to static/config-backups.
mkdir: cannot create directory '/opt/rockstor/static/config-backups': No such file or directory
cp: target '/opt/rockstor/static/config-backups' is not a directory
Running post-transaction scripts ...........................................................................................................................................[done]

simon-77 · May 11, 2026, 9:49am

Regarding the OS upgrade to Leap 16.0

After updating everything (inkluding Rockstor with the postgres migration) on leap 15.6, I installed the opensuse-migration-tool and ran it for the OS migration. The rockstor-testing repo was the only old repo I kept, as @Hooverdan pointed out there is not yet a rockstor 16.0 repo.

Nevertheless, after the update the machine rebooted successfully, but rockstor is not installed anymore - as it seems to still have the dependency to Python 3.11

$ systemctl list-unit-files 'rockstor*'
UNIT FILE               STATE   PRESET  
rockstor-hdparm.service enabled disabled

1 unit files listed.

$ sudo zypper in rockstor 
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: 1: nothing provides 'python311' needed by the to be installed rockstor-5.5.3-0.x86_64
 Solution 1: do not install rockstor-5.5.3-0.x86_64
 Solution 2: break rockstor-5.5.3-0.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/c/d/?] (c): c

According to the announcement of by @phillxnet the new V5.5.3 should already have made the move to Python 3.13 if I read it correctly. V5.5+ Testing Channel Changelog - #7 by phillxnet

How should I proceed, in order to be able to install rockstor on leap 16.0?

Cheers Simon

Hooverdan · May 11, 2026, 3:24pm

check whether python3-rpm is installed, and if not, install it. I used option 2 (breaking Rockstor), which worked for me.

simon-77 · May 11, 2026, 3:39pm

There is no python3-rpm …

$ zypper info python3-rpm
Loading repository data...
Reading installed packages...


package 'python3-rpm' not found.
No matching items found.

But python313 and a bunch of related packages is installed.

Alright, so the not so nice way of using zypper is still required?

But are there still any dependencies to Python 3.11, or is it just an artifact and should be fixed? Is there already a bug report for this (in case this is a bug)?

Hooverdan · May 11, 2026, 5:30pm

sorry, I should have said python313-rpm and since the Leap16.0 rpm is not yet published in its own repo but this scenario relies on the one defined for 15.6, I believe this dependency is still highlighted by zypper. So, once that’s sorted, this dependency should be taken care of automagically.

Warbucks · May 12, 2026, 12:40am

I also did not have the 5.5 update option in the gui with the 5.1 testing channel.

edit: My NAS is a very simple fileshare and tailscale home server. Theres nothing fancy going on. So i dont think i did anything out of the ordinary pripr to this?

I just now sshd in and ran “zypper update rockstor”

Then saw the prompt noting postgresql dependencies. chose 1.

If it helps heres the output. Everything seems to be working now?

# zypper update rockstor

Building repository 'Update repository with updates from SUSE Linux Enterpris
Building repository 'Update repository with updates from SUSE Linux Enterpris
Building repository 'Update repository with updates from SUSE Linux Enterpris[|]
Building repository 'Update repository with updates from SUSE Linux Enterpris[/]
Building repository 'Update repository with updates from SUSE Linux Enterp[done]
Loading repository data…
Reading installed packages…
Resolving package dependencies…

Problem: 1: the to be installed rockstor-5.5.3-0.x86_64 requires ‘postgresql17-devel’, but this requirement cannot be provided
not installable providers: postgresql17-devel-17.2-150600.13.5.1.x86_64[repo-sle-update]
postgresql17-devel-17.4-150600.13.10.1.x86_64[repo-sle-update]
postgresql17-devel-17.5-150600.13.13.1.x86_64[repo-sle-update]
postgresql17-devel-17.6-150600.13.16.1.x86_64[repo-sle-update]
postgresql17-devel-17.7-150600.13.19.1.x86_64[repo-sle-update]
postgresql17-devel-17.9-150600.13.24.1.x86_64[repo-sle-update]

Solution 1: Following actions will be done:
deinstallation of postgresql13-devel-13.23-150600.14.14.1.x86_64
deinstallation of postgresql13-server-devel-13.23-150600.14.14.1.x86_64
deinstallation of postgresql13-llvmjit-devel-13.23-150600.14.14.1.x86_64
Solution 2: do not install rockstor-5.5.3-0.x86_64
Solution 3: break rockstor-5.5.3-0.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): 1

Resolving dependencies…
Resolving package dependencies…

The following package is going to be upgraded:
rockstor

The following 13 NEW packages are going to be installed:
lsb-release postgresql17 postgresql17-contrib postgresql17-devel
postgresql17-llvmjit postgresql17-llvmjit-devel postgresql17-server
postgresql17-server-devel python3-rpm sudo sudo-plugin-python whois
whois-bash-completion

The following 3 packages are going to be REMOVED:
postgresql13-devel postgresql13-llvmjit-devel postgresql13-server-devel

1 package to upgrade, 13 new, 3 to remove.

Package download size: 24.4 MiB

Package install size change:
| 86.5 MiB required by packages that will be installed
72.3 MiB | - 14.2 MiB released by packages that will be removed

Backend: classic_rpmtrans
Continue? [y/n/v/…? shows all options] (y): y
Retrieving: lsb-release-3.1-1.16.noarch (Leap_15_6) (1/14), 19.8 KiB

Retrieving: lsb-release-3.1-1.16.noarch.rpm --------------------------[starting]
Retrieving: lsb-release-3.1-1.16.noarch.rpm ---------------------------------
Retrieving: lsb-release-3.1-1.16.noarch.rpm …=[| (19.5 KiB/s)]
Retrieving: lsb-release-3.1-1.16.noarch.rpm …[done (19.5 KiB/s)]
Retrieving: whois-5.5.20-150600.1.4.x86_64 (Leap_15_6) (2/14), 106.9 KiB

Retrieving: whois-5.5.20-150600.1.4.x86_64.rpm -----------------------[starting]
Retrieving: whois-5.5.20-150600.1.4.x86_64.rpm ------------------------------[/]
Retrieving: whois-5.5.20-150600.1.4.x86_64.rpm …[- (106.9 KiB/s)]
Retrieving: whois-5.5.20-150600.1.4.x86_64.rpm …[done (106.9 KiB/s)]
Retrieving: whois-bash-completion-5.5.20-150600.1.4.noarch (Leap_15_6)
(3/14), 21.0 KiB

Retrieving: whois-bash-completion-5.5.20-150600.1.4.noarch.rpm -------[starting]
Retrieving: whois-bash-completion-5.5.20-150600.1.4.noarch.rpm --------------
Retrieving: whois-bash-completion-5.5.20-150600.1.4.noarch.rpm …[done]
Retrieving: postgresql17-17.9-150600.13.24.1.x86_64 (Update repository with
updates from SUSE Linux Enterprise 15)
(4/14), 2.0 MiB

Retrieving: postgresql17-17.9-150600.13.24.1.x86_64.rpm --------------[starting]
Retrieving: postgresql17-17.9-150600.13.24.1.x86_64.rpm ---------------------[|]
Retrieving: postgresql17-17.9-150600.13.24.1.x86_64.rpm …[not found]

Retrieving: postgresql17-17.9-150600.13.24.1.x86_64.rpm --------------[starting]
Retrieving: postgresql17-17.9-150600.13.24.1.x86_64.rpm ---------------------[/]
Retrieving: postgresql17-17.9-150600.13.24.1.x86_64.rpm …[not found]

Retrieving: postgresql17-17.9-150600.13.24.1.x86_64.rpm --------------[starting]
Retrieving: postgresql17-17.9-150600.13.24.1.x86_64.rpm ---------------------[-]
Retrieving: postgresql17-17.9-150600.13.24.1.x86_64.rpm ====[\ (44.4 KiB/s)]
Retrieving: postgresql17-17.9-150600.13.24.1.x86_64.rpm ==[| (397.2 KiB/s)]
Retrieving: postgresql17-17.9-150600.13.24.1.x86_64.rpm …[done (1.1 MiB/s)]
Retrieving: python3-rpm-4.14.3-150400.59.16.1.x86_64 (Update repository with
updates from SUSE Linux Enterprise 15)
(5/14), 56.2 KiB

Retrieving: python3-rpm-4.14.3-150400.59.16.1.x86_64.rpm -------------[starting]
Retrieving: python3-rpm-4.14.3-150400.59.16.1.x86_64.rpm --------------------[/]
Retrieving: python3-rpm-4.14.3-150400.59.16.1.x86_64.rpm .=[- (54.4 KiB/s)]
Retrieving: python3-rpm-4.14.3-150400.59.16.1.x86_64.rpm …[done (54.4 KiB/s)]
Retrieving: sudo-1.9.15p5-150600.3.12.1.x86_64 (Update repository with updates
from SUSE Linux Enterprise 15)
(6/14), 1.9 MiB

Retrieving: sudo-1.9.15p5-150600.3.12.1.x86_64.rpm -------------------[starting]
Retrieving: sudo-1.9.15p5-150600.3.12.1.x86_64.rpm --------------------------
Retrieving: sudo-1.9.15p5-150600.3.12.1.x86_64.rpm …[not found]

Retrieving: sudo-1.9.15p5-150600.3.12.1.x86_64.rpm -------------------[starting]
Retrieving: sudo-1.9.15p5-150600.3.12.1.x86_64.rpm --------------------------[|]
Retrieving: sudo-1.9.15p5-150600.3.12.1.x86_64.rpm …[not found]

Retrieving: sudo-1.9.15p5-150600.3.12.1.x86_64.rpm -------------------[starting]
Retrieving: sudo-1.9.15p5-150600.3.12.1.x86_64.rpm --------------------------[/]
Retrieving: sudo-1.9.15p5-150600.3.12.1.x86_64.rpm …[done]
Retrieving: sudo-plugin-python-1.9.15p5-150600.3.12.1.x86_64 (Update repository
with updates from SUSE Linux Enterprise 15)
(7/14), 172.7 KiB

Retrieving: sudo-plugin-python-1.9.15p5-150600.3.12.1.x86_64.rpm -----[starting]
Retrieving: sudo-plugin-python-1.9.15p5-150600.3.12.1.x86_64.rpm ------------[-]
Retrieving: sudo-plugin-python-1.9.15p5-150600.3.12.1.x86_64.rpm …[not found]

Retrieving: sudo-plugin-python-1.9.15p5-150600.3.12.1.x86_64.rpm -----[starting]
Retrieving: sudo-plugin-python-1.9.15p5-150600.3.12.1.x86_64.rpm ------------
Retrieving: sudo-plugin-python-1.9.15p5-150600.3.12.1.x86_64.rpm …[not found]

Retrieving: sudo-plugin-python-1.9.15p5-150600.3.12.1.x86_64.rpm -----[starting]
Retrieving: sudo-plugin-python-1.9.15p5-150600.3.12.1.x86_64.rpm ------------[|]
Retrieving: sudo-plugin-python-1.9.15p5-150600.3.12.1.x86_64.rpm …[done]
Retrieving: postgresql17-server-17.9-150600.13.24.1.x86_64 (Update repository
with updates from SUSE Linux Enterprise 15)
(8/14), 5.7 MiB

Retrieving: postgresql17-server-17.9-150600.13.24.1.x86_64.rpm -------[starting]
Retrieving: postgresql17-server-17.9-150600.13.24.1.x86_64.rpm --------------[/]
Retrieving: postgresql17-server-17.9-150600.13.24.1.x86_64.rpm …[not found]

Retrieving: postgresql17-server-17.9-150600.13.24.1.x86_64.rpm -------[starting]
Retrieving: postgresql17-server-17.9-150600.13.24.1.x86_64.rpm --------------[-]
Retrieving: postgresql17-server-17.9-150600.13.24.1.x86_64.rpm …[not found]

Retrieving: postgresql17-server-17.9-150600.13.24.1.x86_64.rpm -------[starting]
Retrieving: postgresql17-server-17.9-150600.13.24.1.x86_64.rpm --------------
Retrieving: postgresql17-server-17.9-150600.13.24.1.x86_64.rpm ==[| (1.4 MiB/s)]
Retrieving: postgresql17-server-17.9-150600.13.24.1.x86_64.rpm .=[/ (3.9 MiB/s)]
Retrieving: postgresql17-server-17.9-150600.13.24.1.x86_64.rpm[done (3.9 MiB/s)]
Retrieving: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64 (Update repository
with updates from SUSE Linux Enterprise 15)
(9/14), 9.4 MiB

Retrieving: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64.rpm ------[starting]
Retrieving: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64.rpm -------------[-]
Retrieving: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64.rpm …[not found]

Retrieving: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64.rpm ------[starting]
Retrieving: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64.rpm -------------
Retrieving: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64.rpm …[not found]

Retrieving: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64.rpm ------[starting]
Retrieving: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64.rpm -------------[|]
Retrieving: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64.rpm =[/ (1.3 MiB/s)]
Retrieving: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64.rpm =[- (4.2 MiB/s)]
Retrieving: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64.rpm =[\ (7.7 MiB/s)]
Retrieving: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64.rp[done (7.7 MiB/s)]
Retrieving: postgresql17-contrib-17.9-150600.13.24.1.x86_64 (Update repository
with updates from SUSE Linux Enterprise 15)
(10/14), 764.7 KiB

Retrieving: postgresql17-contrib-17.9-150600.13.24.1.x86_64.rpm ------[starting]
Retrieving: postgresql17-contrib-17.9-150600.13.24.1.x86_64.rpm -------------[|]
Retrieving: postgresql17-contrib-17.9-150600.13.24.1.x86_64.rpm …[not found]

Retrieving: postgresql17-contrib-17.9-150600.13.24.1.x86_64.rpm ------[starting]
Retrieving: postgresql17-contrib-17.9-150600.13.24.1.x86_64.rpm -------------[/]
Retrieving: postgresql17-contrib-17.9-150600.13.24.1.x86_64.rpm …[not found]

Retrieving: postgresql17-contrib-17.9-150600.13.24.1.x86_64.rpm ------[starting]
Retrieving: postgresql17-contrib-17.9-150600.13.24.1.x86_64.rpm -------------[-]
Retrieving: postgresql17-contrib-17.9-150600.13.24.1.x86_64.rpm …[done]
Retrieving: postgresql17-devel-17.9-150600.13.24.1.x86_64 (Update repository
with updates from SUSE Linux Enterprise 15)
(11/14), 304.0 KiB

Retrieving: postgresql17-devel-17.9-150600.13.24.1.x86_64.rpm --------[starting]
Retrieving: postgresql17-devel-17.9-150600.13.24.1.x86_64.rpm ---------------
Retrieving: postgresql17-devel-17.9-150600.13.24.1.x86_64.rpm …[not found]

Retrieving: postgresql17-devel-17.9-150600.13.24.1.x86_64.rpm --------[starting]
Retrieving: postgresql17-devel-17.9-150600.13.24.1.x86_64.rpm ---------------[|]
Retrieving: postgresql17-devel-17.9-150600.13.24.1.x86_64.rpm …[not found]

Retrieving: postgresql17-devel-17.9-150600.13.24.1.x86_64.rpm --------[starting]
Retrieving: postgresql17-devel-17.9-150600.13.24.1.x86_64.rpm ---------------[/]
Retrieving: postgresql17-devel-17.9-150600.13.24.1.x86_64.rpm …[done]
Retrieving: postgresql17-server-devel-17.9-150600.13.24.1.x86_64 (Update
repository with updates from SUSE Linux Enterprise 15)
(12/14), 1.9 MiB

Retrieving: postgresql17-server-devel-17.9-150600.13.24.1.x86_64.rpm -[starting]
Retrieving: postgresql17-server-devel-17.9-150600.13.24.1.x86_64.rpm --------[-]
Retrieving: postgresql17-server-devel-17.9-150600.13.24.1.x86_64.rpm [not found]

Retrieving: postgresql17-server-devel-17.9-150600.13.24.1.x86_64.rpm -[starting]
Retrieving: postgresql17-server-devel-17.9-150600.13.24.1.x86_64.rpm --------
Retrieving: postgresql17-server-devel-17.9-150600.13.24.1.x86_64.rpm [not found]

Retrieving: postgresql17-server-devel-17.9-150600.13.24.1.x86_64.rpm -[starting]
Retrieving: postgresql17-server-devel-17.9-150600.13.24.1.x86_64.rpm --------[|]
Retrieving: postgresql17-server-devel-17.9-150600.13.24.1.x86_64.rpm …[done]
Retrieving: rockstor-5.5.3-0.x86_64 (Rockstor-Testing) (13/14), 2.1 MiB

Retrieving: rockstor-5.5.3-0.x86_64.rpm ------------------------------[starting]
Retrieving: rockstor-5.5.3-0.x86_64.rpm -------------------------------------[/]
Retrieving: rockstor-5.5.3-0.x86_64.rpm -------------------------------------[-]
Retrieving: rockstor-5.5.3-0.x86_64.rpm ------------------------[\ (13.9 KiB/s)]
Retrieving: rockstor-5.5.3-0.x86_64.rpm ====================[| (42.2 KiB/s)]
Retrieving: rockstor-5.5.3-0.x86_64.rpm ====================[/ (67.7 KiB/s)]
Retrieving: rockstor-5.5.3-0.x86_64.rpm ===================[- (122.8 KiB/s)]
Retrieving: rockstor-5.5.3-0.x86_64.rpm ==================[\ (220.4 KiB/s)]
Retrieving: rockstor-5.5.3-0.x86_64.rpm ==================[| (465.0 KiB/s)]
Retrieving: rockstor-5.5.3-0.x86_64.rpm …===========[/ (910.4 KiB/s)]
Retrieving: rockstor-5.5.3-0.x86_64.rpm …====[- (1.8 MiB/s)]
Retrieving: rockstor-5.5.3-0.x86_64.rpm …[done (1.8 MiB/s)]
Retrieving: postgresql17-llvmjit-devel-17.9-150600.13.24.1.x86_64 (Update
repository with updates from SUSE Linux Enterprise 15)
(14/14), 26.9 KiB

Retrieving: postgresql17-llvmjit-devel-17.9-150600.13.24.1.x86_64.rpm [starting]
Retrieving: postgresql17-llvmjit-devel-17.9-150600.13.24.1.x86_64.rpm -------
Retrieving: postgresql17-llvmjit-devel-17.9-150600.13.24.1.x86_64.rpm[not found]

Retrieving: postgresql17-llvmjit-devel-17.9-150600.13.24.1.x86_64.rpm [starting]
Retrieving: postgresql17-llvmjit-devel-17.9-150600.13.24.1.x86_64.rpm -------[|]
Retrieving: postgresql17-llvmjit-devel-17.9-150600.13.24.1.x86_64.rpm[not found]

Retrieving: postgresql17-llvmjit-devel-17.9-150600.13.24.1.x86_64.rpm [starting]
Retrieving: postgresql17-llvmjit-devel-17.9-150600.13.24.1.x86_64.rpm -------[/]
Retrieving: postgresql17-llvmjit-devel-17.9-150600.13.24.1.x86_64.rpm …[done]

Checking for file conflicts: ------------------------------------------------[-]
Checking for file conflicts: ------------------------------------------------[|]
Checking for file conflicts: ============================================
Checking for file conflicts: ============================================[|]
Checking for file conflicts: ===========================================[/]
Checking for file conflicts: …=====================================[-]
Checking for file conflicts: …=================================
Checking for file conflicts: …===========================[|]
Checking for file conflicts: …======================[/]
Checking for file conflicts: …[-]
Checking for file conflicts: …[done]

( 1/17) Removing: postgresql13-llvmjit-devel-13.23-150600.14.14.1.x86_64 ----
( 1/17) Removing: postgresql13-llvmjit-devel-13.23-150600.14.14.1.x86_64 …[|]
( 1/17) Removing: postgresql13-llvmjit-devel-13.23-150600.14.14.1.x86_64 .[done]

( 2/17) Installing: lsb-release-3.1-1.16.noarch -----------------------------[/]
( 2/17) Installing: lsb-release-3.1-1.16.noarch -----------------------------[/]
( 2/17) Installing: lsb-release-3.1-1.16.noarch …================[-]
( 2/17) Installing: lsb-release-3.1-1.16.noarch …=
( 2/17) Installing: lsb-release-3.1-1.16.noarch …[done]

( 3/17) Installing: whois-5.5.20-150600.1.4.x86_64 --------------------------[|]
( 3/17) Installing: whois-5.5.20-150600.1.4.x86_64 --------------------------[-]
( 3/17) Installing: whois-5.5.20-150600.1.4.x86_64 …[done]

( 4/17) Installing: whois-bash-completion-5.5.20-150600.1.4.noarch ----------[/]
( 4/17) Installing: whois-bash-completion-5.5.20-150600.1.4.noarch ----------
( 4/17) Installing: whois-bash-completion-5.5.20-150600.1.4.noarch …[done]

( 5/17) Installing: postgresql17-17.9-150600.13.24.1.x86_64 -----------------[-]
( 5/17) Installing: postgresql17-17.9-150600.13.24.1.x86_64 -----------------[|]
( 5/17) Installing: postgresql17-17.9-150600.13.24.1.x86_64 =============
( 5/17) Installing: postgresql17-17.9-150600.13.24.1.x86_64 ============[|]
( 5/17) Installing: postgresql17-17.9-150600.13.24.1.x86_64 …======[/]
( 5/17) Installing: postgresql17-17.9-150600.13.24.1.x86_64 …==[-]
( 5/17) Installing: postgresql17-17.9-150600.13.24.1.x86_64 …=
( 5/17) Installing: postgresql17-17.9-150600.13.24.1.x86_64 …[done]

( 6/17) Installing: python3-rpm-4.14.3-150400.59.16.1.x86_64 ----------------[|]
( 6/17) Installing: python3-rpm-4.14.3-150400.59.16.1.x86_64 ----------------[/]
( 6/17) Installing: python3-rpm-4.14.3-150400.59.16.1.x86_64 …[done]

( 7/17) Installing: sudo-1.9.15p5-150600.3.12.1.x86_64 ----------------------[/]
( 7/17) Installing: sudo-1.9.15p5-150600.3.12.1.x86_64 ----------------------[-]
( 7/17) Installing: sudo-1.9.15p5-150600.3.12.1.x86_64 =================[-]
( 7/17) Installing: sudo-1.9.15p5-150600.3.12.1.x86_64 …==========
( 7/17) Installing: sudo-1.9.15p5-150600.3.12.1.x86_64 …=====[|]
( 7/17) Installing: sudo-1.9.15p5-150600.3.12.1.x86_64 …[done]

( 8/17) Installing: sudo-plugin-python-1.9.15p5-150600.3.12.1.x86_64 --------[/]
( 8/17) Installing: sudo-plugin-python-1.9.15p5-150600.3.12.1.x86_64 --------
( 8/17) Installing: sudo-plugin-python-1.9.15p5-150600.3.12.1.x86_64 …[done]

( 9/17) Installing: postgresql17-server-17.9-150600.13.24.1.x86_64 ----------[-]
( 9/17) Installing: postgresql17-server-17.9-150600.13.24.1.x86_64 ----------[|]
( 9/17) Installing: postgresql17-server-17.9-150600.13.24.1.x86_64 ======
( 9/17) Installing: postgresql17-server-17.9-150600.13.24.1.x86_64 =====[|]
( 9/17) Installing: postgresql17-server-17.9-150600.13.24.1.x86_64 =====[/]
( 9/17) Installing: postgresql17-server-17.9-150600.13.24.1.x86_64 =====[-]
( 9/17) Installing: postgresql17-server-17.9-150600.13.24.1.x86_64 =====
( 9/17) Installing: postgresql17-server-17.9-150600.13.24.1.x86_64 =====[|]
( 9/17) Installing: postgresql17-server-17.9-150600.13.24.1.x86_64 =====[/]
( 9/17) Installing: postgresql17-server-17.9-150600.13.24.1.x86_64 …==[-]
( 9/17) Installing: postgresql17-server-17.9-150600.13.24.1.x86_64 …==
( 9/17) Installing: postgresql17-server-17.9-150600.13.24.1.x86_64 …=[|]
( 9/17) Installing: postgresql17-server-17.9-150600.13.24.1.x86_64 …=[/]
( 9/17) Installing: postgresql17-server-17.9-150600.13.24.1.x86_64 …[done]

(10/17) Installing: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64 ---------[-]
(10/17) Installing: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64 ---------[/]
(10/17) Installing: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64 =====
(10/17) Installing: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64 =====[|]
(10/17) Installing: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64 ====[/]
(10/17) Installing: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64 ====[-]
(10/17) Installing: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64 ====
(10/17) Installing: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64 ====[|]
(10/17) Installing: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64 ====[/]
(10/17) Installing: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64 ====[-]
(10/17) Installing: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64 ====
(10/17) Installing: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64 ====[|]
(10/17) Installing: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64 ====[/]
(10/17) Installing: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64 ..==[-]
(10/17) Installing: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64 ..==
(10/17) Installing: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64 …=[|]
(10/17) Installing: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64 …=[/]
(10/17) Installing: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64 …=[-]
(10/17) Installing: postgresql17-llvmjit-17.9-150600.13.24.1.x86_64 …[done]

(11/17) Installing: postgresql17-contrib-17.9-150600.13.24.1.x86_64 ---------
(11/17) Installing: postgresql17-contrib-17.9-150600.13.24.1.x86_64 ---------[-]
(11/17) Installing: postgresql17-contrib-17.9-150600.13.24.1.x86_64 ====[|]
(11/17) Installing: postgresql17-contrib-17.9-150600.13.24.1.x86_64 …=[/]
(11/17) Installing: postgresql17-contrib-17.9-150600.13.24.1.x86_64 …[done]

(12/17) Installing: postgresql17-devel-17.9-150600.13.24.1.x86_64 -----------[-]
(12/17) Installing: postgresql17-devel-17.9-150600.13.24.1.x86_64 -----------
(12/17) Installing: postgresql17-devel-17.9-150600.13.24.1.x86_64 …[done]

(13/17) Installing: postgresql17-server-devel-17.9-150600.13.24.1.x86_64 ----
(13/17) Installing: postgresql17-server-devel-17.9-150600.13.24.1.x86_64 ----[|]
(13/17) Installing: postgresql17-server-devel-17.9-150600.13.24.1.x86_64 ====[|]
(13/17) Installing: postgresql17-server-devel-17.9-150600.13.24.1.x86_64 ====[/]
(13/17) Installing: postgresql17-server-devel-17.9-150600.13.24.1.x86_64 .===[-]
(13/17) Installing: postgresql17-server-devel-17.9-150600.13.24.1.x86_64 .===
(13/17) Installing: postgresql17-server-devel-17.9-150600.13.24.1.x86_64 ..==[|]
(13/17) Installing: postgresql17-server-devel-17.9-150600.13.24.1.x86_64 ..==[/]
(13/17) Installing: postgresql17-server-devel-17.9-150600.13.24.1.x86_64 …=[-]
(13/17) Installing: postgresql17-server-devel-17.9-150600.13.24.1.x86_64 .[done]

(14/17) Installing: rockstor-5.5.3-0.x86_64 ---------------------------------
(14/17) Installing: rockstor-5.5.3-0.x86_64 ---------------------------------[/]
Failed to stop rockstor-scheduling.service: Unit rockstor-scheduling.service not loaded.
Failed to stop rockstor-replication.service: Unit rockstor-replication.service not loaded.
Failed to stop rockstor-collector.service: Unit rockstor-collector.service not loaded.
No static/config-backups directory found.

(14/17) Installing: rockstor-5.5.3-0.x86_64 ---------------------------------[-]
(14/17) Installing: rockstor-5.5.3-0.x86_64 ============================[|]
(14/17) Installing: rockstor-5.5.3-0.x86_64 …=====================[/]
(14/17) Installing: rockstor-5.5.3-0.x86_64 …===============[-]
(14/17) Installing: rockstor-5.5.3-0.x86_64 …==========
(14/17) Installing: rockstor-5.5.3-0.x86_64 …======[|]
update-alternatives: using /usr/lib/postgresql17 to provide /usr/lib/postgresql (postgresql) in manual mode

(14/17) Installing: rockstor-5.5.3-0.x86_64 ---------------------------------
(14/17) Installing: rockstor-5.5.3-0.x86_64 …=[/]
(14/17) Installing: rockstor-5.5.3-0.x86_64 …[done]

(15/17) Removing: postgresql13-server-devel-13.23-150600.14.14.1.x86_64 -----[-]
(15/17) Removing: postgresql13-server-devel-13.23-150600.14.14.1.x86_64 …
(15/17) Removing: postgresql13-server-devel-13.23-150600.14.14.1.x86_64 ..===[|]
(15/17) Removing: postgresql13-server-devel-13.23-150600.14.14.1.x86_64 ..[done]

(16/17) Removing: postgresql13-devel-13.23-150600.14.14.1.x86_64 ------------[/]
(16/17) Removing: postgresql13-devel-13.23-150600.14.14.1.x86_64 …[-]
(16/17) Removing: postgresql13-devel-13.23-150600.14.14.1.x86_64 …[done]

(17/17) Installing: postgresql17-llvmjit-devel-17.9-150600.13.24.1.x86_64 —
(17/17) Installing: postgresql17-llvmjit-devel-17.9-150600.13.24.1.x86_64 —[|]
(17/17) Installing: postgresql17-llvmjit-devel-17.9-150600.13.24.1.x86_64 [done]

Running post-transaction scripts --------------------------------------------[|]
Running post-transaction scripts --------------------------------------------[/]
%posttrans(rockstor-5.5.3-0.x86_64) script output:
Current DB format is already 13.
Updating DB format from 13 to 17 via /usr/lib/postgresql17/bin/pg_upgrade.
/var/lib/pgsql /

Adopting installs’ LANG=en_US.UTF-8
The files belonging to this database system will be owned by user “postgres”.
This user must also own the server process.

The database cluster will be initialized with locale “en_US.UTF-8”.
The default text search configuration will be set to “english”.

Data page checksums are disabled.

creating directory /var/lib/pgsql/data17 … ok
creating subdirectories … ok
selecting dynamic shared memory implementation … posix
selecting default “max_connections” … 100
selecting default “shared_buffers” … 128MB
selecting default time zone … America/New_York
creating configuration files … ok
running bootstrap script … ok
performing post-bootstrap initialization … ok
syncing data to disk … ok

initdb: warning: enabling “trust” authentication for local connections
initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.

Success. You can now start the database server using:

/usr/lib/postgresql17/bin/pg_ctl -D /var/lib/pgsql/data17 -l logfile start

Stopping postgresql systemd service

mv /var/lib/pgsql/data /var/lib/pgsql/data13

Performing Consistency Checks

Checking cluster versions ok
Checking database user is the install user ok
Checking database connection settings ok
Checking for prepared transactions ok
Checking for contrib/isn with bigint-passing mismatch ok
Checking data type usage ok
Checking for user-defined encoding conversions ok
Checking for user-defined postfix operators ok
Checking for incompatible polymorphic functions ok
Checking for not-null constraint inconsistencies ok
Creating dump of global objects ok
Creating dump of database schemas ok
Checking for presence of required libraries ok
Checking database user is the install user ok
Checking for prepared transactions ok
Checking for new cluster tablespace directories ok

If pg_upgrade fails after this point, you must re-initdb the
new cluster before continuing.

Performing Upgrade

Setting locale and encoding for new cluster ok
Analyzing all rows in the new cluster ok
Freezing all rows in the new cluster ok
Deleting files from new pg_xact ok
Copying old pg_xact to new server ok
Setting oldest XID for new cluster ok
Setting next transaction ID and epoch for new cluster ok
Deleting files from new pg_multixact/offsets ok
Copying old pg_multixact/offsets to new server ok
Deleting files from new pg_multixact/members ok
Copying old pg_multixact/members to new server ok
Setting next multixact ID and offset for new cluster ok
Resetting WAL archives ok
Setting frozenxid and minmxid counters in new cluster ok
Restoring global objects in the new cluster ok
Restoring database schemas in the new cluster ok
Copying user relation files ok
Setting next OID for new cluster ok
Sync data directory to disk ok
Creating script to delete old cluster ok
Checking for extension updates ok

Upgrade Complete

Optimizer statistics are not transferred by pg_upgrade.
Once you start the new server, consider running:
/usr/lib/postgresql17/bin/vacuumdb --all --analyze-in-stages
Running this script will delete the old cluster’s data files:
./delete_old_cluster.sh

Linking data → data17

Starting postgresql systemd service

Running /usr/lib/postgresql17/bin/vacuumdb
vacuumdb: processing database “postgres”: Generating minimal optimizer statistics (1 target)
vacuumdb: processing database “smartdb”: Generating minimal optimizer statistics (1 target)
vacuumdb: processing database “storageadmin”: Generating minimal optimizer statistics (1 target)
vacuumdb: processing database “template1”: Generating minimal optimizer statistics (1 target)
vacuumdb: processing database “postgres”: Generating medium optimizer statistics (10 targets)
vacuumdb: processing database “smartdb”: Generating medium optimizer statistics (10 targets)
vacuumdb: processing database “storageadmin”: Generating medium optimizer statistics (10 targets)
vacuumdb: processing database “template1”: Generating medium optimizer statistics (10 targets)
vacuumdb: processing database “postgres”: Generating default (full) optimizer statistics
vacuumdb: processing database “smartdb”: Generating default (full) optimizer statistics
vacuumdb: processing database “storageadmin”: Generating default (full) optimizer statistics
vacuumdb: processing database “template1”: Generating default (full) optimizer statistics

Running /usr/lib/postgresql17/bin/reindexdb
reindexdb: reindexing database “postgres”
reindexdb: reindexing database “smartdb”
reindexdb: reindexing database “storageadmin”
reindexdb: reindexing database “template1”

Restoring pior pwd
/

All Rockstor services, if running, will have been stopped.
Restart via ‘systemctl start rockstor-bootstrap.service’
Restoring config-backups-rpmsave contents to static/config-backups.
mkdir: cannot create directory ‘/opt/rockstor/static/config-backups’: No such file or directory
cp: cannot create regular file ‘/opt/rockstor/static/config-backups’: No such file or directory

Running post-transaction scripts …[/]
Running post-transaction scripts …[-]
Running post-transaction scripts …[done]

reboot

Connection is closed

Remote side unexpectedly closed network connection

phillxnet · May 12, 2026, 12:39pm

@simon-77 Re:

This is note actually what @Hooverdan stated; in:

The contained link is to the OBS repo we normally use for the upstream Shellinabox package which is in the throws of gaining Leap 16.0 inclusion (hopefully), in part thanks to @Flox for chasing that one up. We have, since publishing for Leap 16.0, carried a dedicated repo (edge & testing only) and build on that platform specifically with the Shellinabox package dependency removed; for now at least. But only for that repo target as OBS has Shellinabox for all our other targets.

This is mostly likely why you are getting:

As our Leap 15.6 rpms must depend on Py3.11 as that is all we have there, but the packages we build for Leap 16.0 user Py3.13 on the OS side.

Manually add the proper/dedicated Leap16.0 testing repo, just as it was for 15.6 but with 16.0 numbering and then install the ‘rockstor’ package. N.B. you will need to start the rockstor-bootstrap service in order to kick-off our multi-systemd service cascade. This will then rebuild the .venv environment that the rpm install should have wiped ready for it to be re-created.

Note that we now use Poetry managed standalone Py3.13 to run our code on both Leap 15.6 and 16.0, but our poetry itself is meant to be hosted by the OS provided Py3.11 (15.6) & Py3.13 (16.0) - with some work left to be done on that front in our TW & SR targets.

Thanks for your reports here, always good to have folks testing stuff and reporting back to help us get to the next Stable out-of-the-box target.

In time, as we approach later RC releases we can prepare the howtos aimed at getting stable from one OS to the next - with a nod to later testing rpms doing the same.

Hope that helps.

simon-77 · May 12, 2026, 12:54pm

Awesome, thank you @phillxnet for the reply.

Could you please point briefly out on where I can find the Leap 16.0 testing repo for now?

And thank’s for the hint regarding the bootstrap service - I will definitely let you know how it went.
Cheers Simon

simon-77 · May 12, 2026, 2:52pm

Never mind, I found it and at least the installation did work. As reference:

Remove old repo

$ sudo zypper removerepo Rockstor-Testing
Removing repository 'Rockstor-Testing' ............................................................................................................................................................[done]
Repository 'Rockstor-Testing' has been removed.

Add Leap 16.0 repo

$ sudo zypper addrepo --refresh http://updates.rockstor.com:8999/rockstor-testing/leap/16.0 Rockstor-Testing
Adding repository 'Rockstor-Testing' ..............................................................................................................................................................[done]
Repository 'Rockstor-Testing' successfully added

URI         : http://updates.rockstor.com:8999/rockstor-testing/leap/16.0
Enabled     : Yes
GPG Check   : Yes
Autorefresh : Yes
Priority    : 99 (default priority)

Repository priorities are without effect. All enabled repositories share the same priority.
admin@Kolibri:~> sudo zypper refresh
Retrieving repository 'Rockstor-Testing' metadata .................................................................................................................................................[done]
Building repository 'Rockstor-Testing' cache ......................................................................................................................................................[done]
Repository 'repo-openh264 (16.0)' is up to date.                                                                                                                                                         
Looking for gpg keys in repository repo-oss (16.0).
  gpgkey=http://cdn.opensuse.org/distribution/leap/16.0/repo/oss/x86_64/repodata/repomd.xml.key
Retrieving repository 'repo-oss (16.0)' metadata ..................................................................................................................................................[done]
Building repository 'repo-oss (16.0)' cache .......................................................................................................................................................[done]
All repositories have been refreshed

And for this package, the requirements are set correctly, so I could install rockstor without further ado:

$ sudo zypper in rockstor
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following 7 NEW packages are going to be installed:
  python313-argcomplete python313-click python313-devel python313-pipx python313-platformdirs python313-userpath rockstor

7 new packages to install.

Package download size:     3.6 MiB

Package install size change:
              |      10.9 MiB  required by packages that will be installed
    10.9 MiB  |  -      0 B    released by packages that will be removed

Backend:  classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): 
Preloading: python313-platformdirs-4.3.8-160000.2.2.noarch.rpm [done]
Preloading: python313-click-8.2.1-160000.2.2.noarch.rpm [done]
Preloading: python313-argcomplete-3.5.3-160000.2.2.noarch.rpm [done]
Preloading: python313-userpath-1.9.2-160000.2.2.noarch.rpm [done]
Preloading: python313-pipx-1.7.1-160000.2.2.noarch.rpm [done]
Preloading: python313-devel-3.13.13-160000.1.1.x86_64.rpm [done]
Preloading: rockstor-5.5.3-0.x86_64.rpm [done]
Preload finished. [success (2.9 MiB/s) ] ..........................................................................................................................................................[done]
Retrieving: python313-argcomplete-3.5.3-160000.2.2.noarch (repo-oss (16.0))                                                                                                          (1/7),  99.7 KiB    
Retrieving: python313-click-8.2.1-160000.2.2.noarch (repo-oss (16.0))                                                                                                                (2/7), 265.0 KiB    
Retrieving: python313-devel-3.13.13-160000.1.1.x86_64 (repo-oss (16.0))                                                                                                              (3/7), 884.8 KiB    
Retrieving: python313-platformdirs-4.3.8-160000.2.2.noarch (repo-oss (16.0))                                                                                                         (4/7),  48.0 KiB    
Retrieving: python313-userpath-1.9.2-160000.2.2.noarch (repo-oss (16.0))                                                                                                             (5/7),  31.2 KiB    
Retrieving: python313-pipx-1.7.1-160000.2.2.noarch (repo-oss (16.0))                                                                                                                 (6/7), 204.9 KiB    
Retrieving: rockstor-5.5.3-0.x86_64 (Rockstor-Testing)                                                                                                                               (7/7),   2.2 MiB    

Checking for file conflicts: ......................................................................................................................................................................[done]
(1/7) Installing: python313-argcomplete-3.5.3-160000.2.2.noarch ...................................................................................................................................[done]
(2/7) Installing: python313-click-8.2.1-160000.2.2.noarch .........................................................................................................................................[done]
(3/7) Installing: python313-devel-3.13.13-160000.1.1.x86_64 .......................................................................................................................................[done]
(4/7) Installing: python313-platformdirs-4.3.8-160000.2.2.noarch ..................................................................................................................................[done]
(5/7) Installing: python313-userpath-1.9.2-160000.2.2.noarch ......................................................................................................................................[done]
(6/7) Installing: python313-pipx-1.7.1-160000.2.2.noarch ..........................................................................................................................................[done]
Failed to stop rockstor-bootstrap.service: Unit rockstor-bootstrap.service not loaded.
Failed to stop rockstor-scheduling.service: Unit rockstor-scheduling.service not loaded.
Failed to stop rockstor-replication.service: Unit rockstor-replication.service not loaded.
Failed to stop rockstor-collector.service: Unit rockstor-collector.service not loaded.
Failed to stop rockstor.service: Unit rockstor.service not loaded.
Failed to stop rockstor-pre.service: Unit rockstor-pre.service not loaded.
Failed to stop rockstor-build.service: Unit rockstor-build.service not loaded.
No static/config-backups directory found.
update-alternatives: error: alternative /usr/bin/pipx-3.11 for pipx not registered; not setting
(7/7) Installing: rockstor-5.5.3-0.x86_64 .........................................................................................................................................................[done]
%posttrans(rockstor-5.5.3-0.x86_64) script output:
Current DB format is 17, This differs from expected format 10 entered.
Current DB format is already 17.
Restoring config-backups-rpmsave contents to static/config-backups.
mkdir: cannot create directory '/opt/rockstor/static/config-backups': No such file or directory
cp: target '/opt/rockstor/static/config-backups': No such file or directory
Running post-transaction scripts ..................................................................................................................................................................[done]

simon-77 · May 12, 2026, 3:33pm

I just ran into another issue, as I have enabled SELinux during the OS upgrade. Turns out this needs to be disabled for Rockstor. So initially I could not start the rockstor-bootstrap service:

$ sudo systemctl start rockstor-bootstrap.service 
A dependency job for rockstor-bootstrap.service failed. See 'journalctl -xe' for details.
$ sudo systemctl --failed
  UNIT                    LOAD   ACTIVE SUB    DESCRIPTION                              
● rockstor-hdparm.service loaded failed failed Rockstor hdparm settings
● rockstor-pre.service    loaded failed failed Tasks required prior to starting Rockstor
● shellinaboxd.service    loaded failed failed shellinaboxd HTTP service

Legend: LOAD   → Reflects whether the unit definition was properly loaded.
        ACTIVE → The high-level unit activation state, i.e. generalization of SUB.
        SUB    → The low-level unit activation state, values depend on unit type.

3 loaded units listed.
$ sudo systemctl status rockstor-pre.service
× rockstor-pre.service - Tasks required prior to starting Rockstor
     Loaded: loaded (/usr/lib/systemd/system/rockstor-pre.service; disabled; preset: disabled)
     Active: failed (Result: exit-code) since Tue 2026-05-12 16:47:00 CEST; 2min 5s ago
 Invocation: 7c28e55f8b7146378871c91e3c076bd5
    Process: 13700 ExecStartPre=/usr/bin/gpg --quick-generate-key --batch --passphrase  rockstor@localhost (code=exited, status=203/EXEC)
    Process: 13701 ExecStartPre=/usr/bin/pass init rockstor@localhost (code=exited, status=0/SUCCESS)
    Process: 13735 ExecStartPre=/usr/bin/pass rename --force python-keyring/rockstor/SECRET_KEY python-keyring/rockstor/SECRET_KEY_FALLBACK (code=exited, status=0/SUCCESS)
    Process: 13766 ExecStartPre=/usr/bin/pass generate --no-symbols --force python-keyring/rockstor/SECRET_KEY 100 (code=exited, status=0/SUCCESS)
    Process: 13780 ExecStartPre=/usr/bin/rpm --erase gpg-pubkey-5f043187 (code=exited, status=0/SUCCESS)
    Process: 13781 ExecStartPre=/usr/bin/rpm --import /opt/rockstor/conf/ROCKSTOR-GPG-KEY (code=exited, status=0/SUCCESS)
    Process: 13782 ExecStart=/usr/local/bin/poetry run initrock (code=exited, status=1/FAILURE)
   Main PID: 13782 (code=exited, status=1/FAILURE)
        CPU: 1.471s

May 12 16:46:58 Kolibri [RPM][13780]: erase gpg-pubkey-5f043187-68331efe: success
May 12 16:46:58 Kolibri [RPM][13780]: erase gpg-pubkey-5f043187-68331efe: success
May 12 16:46:58 Kolibri [RPM][13780]: Transaction ID 6a033d62 finished: 0
May 12 16:47:00 Kolibri su[13976]: (to postgres) root on none
May 12 16:47:00 Kolibri su[13976]: pam_unix(su-l:session): session opened for user postgres(uid=474) by (uid=0)
May 12 16:47:00 Kolibri su[13976]: pam_unix(su-l:session): session closed for user postgres
May 12 16:47:00 Kolibri systemd[1]: rockstor-pre.service: Main process exited, code=exited, status=1/FAILURE
May 12 16:47:00 Kolibri systemd[1]: rockstor-pre.service: Failed with result 'exit-code'.
May 12 16:47:00 Kolibri systemd[1]: Failed to start Tasks required prior to starting Rockstor.
May 12 16:47:00 Kolibri systemd[1]: rockstor-pre.service: Consumed 1.471s CPU time.

Then, disabling SELinux:

For this session only:

sudo setenforce 0

Permanently, starting with the next boot:

sudo sed -i 's/^SELINUX=.*/SELINUX=permissive/' /etc/selinux/config
sudo cp /etc/default/grub /etc/default/grub.bak
sudo sed -i 's/enforcing=1/enforcing=0/g' /etc/default/grub
sudo grub2-mkconfig -o /boot/grub2/grub.cfg

And verify the state of SELinux:

sudo getenforce

The output is Enforcing (Enabled) or Permissive (Disabled)

Afterwards, I could start rockstor successfully with:

sudo systemctl enable --now rockstor-bootstrap.service

And the webUI was up and running

Thank you again @phillxnet and @Hooverdan for the help

Cheers Simon

simon-77 · May 12, 2026, 6:23pm

As I now did the migration on another machine, these are the commands I executed for the migration:

On Leap 15.6: update to the latest version, including the postgres migration & install the migration tool:

sudo zypper up --no-recommends
sudo zypper up rockstor
sudo zypper in opensuse-migration-tool
reboot

Run the migration tool opensuse-migration-tool and select:
- openSUSE Leap 16.0
- keep all repos selected (in order to get disabled after the update)
- select 10_keepselinux (although we have to disable it afterwards, I still like to have it installed)
Reboot - this might take a very long time (SELinux will go through all the data)
Switch Rockstor repo to Leap 16.0:

sudo zypper removerepo Rockstor-Testing
sudo zypper addrepo --refresh http://updates.rockstor.com:8999/rockstor-testing/leap/16.0 Rockstor-Testing

Disable SELinux right away, and then reboot

sudo sed -i 's/^SELINUX=.*/SELINUX=permissive/' /etc/selinux/config
sudo cp /etc/default/grub /etc/default/grub.bak
sudo sed -i 's/enforcing=1/enforcing=0/g' /etc/default/grub
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
sudo reboot

Warning: the reboot might take a long time

Check if SELinux is Permissive after rebooting

sudo getenforce

Install Rockstor

sudo zypper in rockstor

Start Rockstor

sudo systemctl enable --now rockstor-bootstrap.service

Finally, I did list old orphaned packages, remove them and cleaned the zypper cache:

sudo zypper pa --orphaned --unneeded
sudo zypper remove --clean-deps $(zypper packages --unneeded | awk -F'|' '/^i/ {print $3}' | tr -d ' ')
sudo zypper clean --all

Cheers Simon