So I am signed up for testing channels, and I have run the upgrade (tried several times) and even though it appears to run and restart, it does not upgrade. The OS is openSUSE Leap: 15.4 if that matters. All other testing upgrades worked just fine, as you can see I am on 5.0.4-0 already. Just wondering why every time I run it (I tried several times) it does not actually upgrade.
Hi @njmike73 ,
Thanks for the report.
Curiousā¦ I wonder what happened. Would you mind pasting the output from the install log file?
cat /opt/rockstor/poetry-install.log
1 Like
I didnāt see poetry-install.log, but I did see poetry-install.txt in that directory. Here is what that contains:
Creating virtualenv rockstor in /opt/rockstor/.venv
Installing dependencies from lock file
Package operations: 30 installs, 0 updates, 0 removals
ā¢ Installing certifi (2023.7.22)
ā¢ Installing charset-normalizer (2.0.12)
ā¢ Installing greenlet (2.0.2)
ā¢ Installing idna (3.4)
ā¢ Installing pytz (2023.3)
ā¢ Installing six (1.16.0)
ā¢ Installing urllib3 (1.26.16)
ā¢ Installing zope.event (4.6)
ā¢ Installing zope.interface (5.5.2)
ā¢ Installing django (1.11.29)
ā¢ Installing gevent (22.10.2)
ā¢ Installing oauthlib (3.1.0)
ā¢ Installing python-engineio (2.3.2)
ā¢ Installing requests (2.27.1)
ā¢ Installing dbus-python (1.2.18)
ā¢ Installing distro (1.8.0)
ā¢ Installing django-oauth-toolkit (1.1.2)
ā¢ Installing djangorestframework (3.9.3)
ā¢ Installing gunicorn (19.10.0)
ā¢ Installing psutil (5.9.4)
ā¢ Installing psycogreen (1.0)
ā¢ Installing django-braces (1.13.0)
ā¢ Installing gevent-websocket (0.10.1)
ā¢ Installing psycopg2 (2.8.6)
ā¢ Installing huey (2.3.0)
ā¢ Installing django-pipeline (1.7.0)
ā¢ Installing python-socketio (1.6.0)
ā¢ Installing pyzmq (19.0.2)
ā¢ Installing supervisor (4.2.4)
ā¢ Installing urlobject (2.1.1)
Installing the current project: rockstor (5.0.4)
MERCURY:/opt/rockstor #
2 Likes
Also here is what is in the directory in case this matters:
MERCURY:/opt/rockstor # ls
build.sh etc poetry-install.txt README.md rockstor-tasks-huey.db-shm var
certs .initrock poetry.lock rockstor-jslibs.tar.gz rockstor-tasks-huey.db-wal .venv
conf jslibs poetry.toml rockstor-jslibs.tar.gz.sha256sum src
COPYING PKG-INFO pyproject.toml rockstor-tasks-huey.db static
MERCURY:/opt/rockstor #
Thanks a lot for the outputs, @njmike73
My apologies for giving you the wrong extension for that log fileā¦ it is indeed .txt and all files look as they should on your system.
There is one thing, though:
This should say 5.0.5 so this log file is the one from the previous update/install. If you look at the file dates, it should indicate as such:
ls -lah /opt/rockstor/
That seems to indicate that the update/install of the 5.0.5 rpm didnāt begin or failed before poetry-install.txt could begin to be generated. Letās try to see why that is.
First, to make sure, how did you initiate the update? Did you click on the āupā arrow next to the Rockstor version in the top right corner of the page, or clicking the āStart updateā in the System > Software update page (the page listing you have activated the āTestingā channel)?
See our docs for a better explanation of what Iām trying to describe:
https://rockstor.com/docs/installation/install.html#install-updates-from-the-web-ui
1 Like
Yes thatās exactly what I have done (several times) where it says itās updating and I get the 5 minute etc updating notice, and then when itās done, itās steill 5.0.4, and the arrow is still there.
Thanks for the confirmation, @njmike73 ,
Letās see what happens when you trigger the update manually from the command line, then. Can you try the following and the output? Also, please let us know if you notice any slowdown; it should only take a short time so more than that would indicate some issue.
sudo zypper update --no-recommends rockstor
Ah here we goā¦ so what should I do here? Not sure which to pick:
sudo zypper update --no-recommends rockstor
Loading repository dataā¦
Reading installed packagesā¦
Resolving package dependenciesā¦
Problem: the to be installed rockstor-5.0.5-0.x86_64 requires āpython39-develā, but this requirement cannot be provided
not installable providers: python39-devel-3.9.10-150300.4.8.1.x86_64[Leap_15_4]
python39-devel-3.9.10-150300.4.8.1.x86_64[repo-sle-update]
python39-devel-3.9.13-150300.4.13.1.x86_64[repo-sle-update]
python39-devel-3.9.14-150300.4.16.1.x86_64[repo-sle-update]
python39-devel-3.9.15-150300.4.21.1.x86_64[repo-sle-update]
python39-devel-3.9.16-150300.4.24.1.x86_64[repo-sle-update]
python39-devel-3.9.16-150300.4.27.1.x86_64[repo-sle-update]
python39-devel-3.9.17-150300.4.30.1.x86_64[repo-sle-update]
python39-devel-3.9.18-150300.4.33.1.x86_64[repo-sle-update]
Solution 1: Following actions will be done:
deinstallation of python310-base-3.10.13-150400.4.36.1.x86_64
deinstallation of libpython3_10-1_0-3.10.13-150400.4.36.1.x86_64
deinstallation of wsdd-0.7.1-lp154.24.1.noarch
Solution 2: do not install rockstor-5.0.5-0.x86_64
Solution 3: break rockstor-5.0.5-0.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/c/d/?] (c):
1 Like
Oh interestingā¦ keep the default of ācā (cancel) for now.
Iām going to try to verify that on my end because that is unexpected.
Could you, in the meantime, verify your repos are as they should (they probably are, but we need to make sure, just in case):
sudo zypper lr -U
1 Like
Here you go! - sorry about the format - if you cant read let me see if I can do this another wayā¦
# | Alias | Name | Enabled | GPG Check | Refresh | URI
---+-----------------------------+-----------------------------+---------+-----------+---------+----------------------------------
--------------------------------------------
2 | Leap_15_4 | Leap_15_4 | Yes | (r ) Yes | Yes | http://download.opensuse.org/distribution/leap/15.4/repo/oss/
4 | Rockstor-Testing | Rockstor-Testing | Yes | (r ) Yes | Yes | http://updates.rockstor.com:8999/rockstor-testing/leap/15.4
10 | repo-sle-debug-update | repo-sle-debug-update | Yes | (r ) Yes | Yes | https://download.opensuse.org/debug/update/leap/15.4/sle/
1 | Kernel_stable_Backport | Kernel_stable_Backport | Yes | (r ) Yes | Yes | https://download.opensuse.org/repositories/Kernel:/stable:/Backport/standard/
5 | filesystems | filesystems | Yes | (r ) Yes | Yes | https://download.opensuse.org/repositories/filesystems/15.4/
7 | network | network | Yes | (r ) Yes | Yes | https://download.opensuse.org/repositories/network/15.4/
9 | repo-backports-update | repo-backports-update | Yes | (r ) Yes | Yes | https://download.opensuse.org/update/leap/15.4/backports/
8 | repo-backports-debug-update | repo-backports-debug-update | Yes | (r ) Yes | Yes | https://download.opensuse.org/update/leap/15.4/backports_debug/
3 | Leap_15_4_Updates | Leap_15_4_Updates | Yes | (r ) Yes | Yes | https://download.opensuse.org/update/leap/15.4/oss/
11 | repo-sle-update | repo-sle-update | Yes | (r ) Yes | Yes | https://download.opensuse.org/update/leap/15.4/sle/
6 | home_rockstor | home_rockstor | Yes | (r ) Yes | Yes | https://mirrorcache-us.opensuse.org/repositories/home:/rockstor/15.4/
MERCURY:/ #
2 Likes
I reformatted your post just for clarity (wrapped between triple backticks ```); my apologies for the editing.
This is rather curious. For reference, a base Leap 15.4 install should have:
rockstable:~ # zypper lr -U -p
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | URI
--+------------------------------------+---------------------------------------------------------------------------------------------+---------+-----------+---------+----------+----------------------------------------------------------------------------------------
8 | repo-sle-debug-update | Update repository with debuginfo for updates from SUSE Linux Enterprise 15 | No | ---- | ---- | 99 | http://download.opensuse.org/debug/update/leap/15.4/sle/
1 | Leap_15_4 | Leap_15_4 | Yes | (r ) Yes | Yes | 99 | http://download.opensuse.org/distribution/leap/15.4/repo/oss/
7 | repo-backports-update | Update repository of openSUSE Backports | Yes | (r ) Yes | Yes | 99 | http://download.opensuse.org/update/leap/15.4/backports/
6 | repo-backports-debug-update | Update repository with updates for openSUSE Leap debuginfo packages from openSUSE Backports | No | ---- | ---- | 99 | http://download.opensuse.org/update/leap/15.4/backports_debug/
9 | repo-sle-update | Update repository with updates from SUSE Linux Enterprise 15 | Yes | (r ) Yes | Yes | 99 | http://download.opensuse.org/update/leap/15.4/sle/
3 | Rockstor-Testing | Rockstor-Testing | Yes | (r ) Yes | Yes | 99 | http://updates.rockstor.com:8999/rockstor-testing/leap/15.4
4 | home_rockstor | home_rockstor | Yes | (r ) Yes | Yes | 105 | https://download.opensuse.org/repositories/home:/rockstor/15.4/
5 | home_rockstor_branches_Base_System | home_rockstor_branches_Base_System | Yes | (r ) Yes | Yes | 97 | https://download.opensuse.org/repositories/home:/rockstor:/branches:/Base:/System/15.4/
2 | Leap_15_4_Updates | Leap_15_4_Updates | Yes | (r ) Yes | Yes | 99 | https://download.opensuse.org/update/leap/15.4/oss/
So the differences I can see:
- your debug repos are enabled. You could try re-disable them as you shouldnāt need that:
zypper mr --disable repo-sle-debug-update
zypper mr --disable repo-backports-debug-update - you have the
networkrepo.
I honestly do not see any of these as an issue, but letās try again once you have disabled the debug repositories.
On a side note, I also notice the following:
deinstallation of wsdd-0.7.1-lp154.24.1.noarch
Did you remember installing anything in particular to have wsdd? I wonder why that is there and if that is part of why you seem to have something conflicting with the python install.
Also, maybe the following could verify what you see:
zypper se python39-devel
and
zypper info python39-devel
For reference, what I have is:
rockstable:~ # zypper info python39-devel
Loading repository data...
Reading installed packages...
Information for package python39-devel:
---------------------------------------
Repository : Update repository with updates from SUSE Linux Enterprise 15
Name : python39-devel
Version : 3.9.18-150300.4.33.1
Arch : x86_64
Vendor : SUSE LLC <https://www.suse.com/>
Installed Size : 918.6 KiB
Installed : No
Status : not installed
Source package : python39-core-3.9.18-150300.4.33.1.src
Upstream URL : https://www.python.org/
Summary : Include Files and Libraries Mandatory for Building Python Modules
Description :
The Python programming language's interpreter can be extended with
dynamically loaded extensions and can be embedded in other programs.
This package contains header files, a static library, and development
tools for building Python modules, extending the Python interpreter or
embedding Python in applications.
This also includes the Python distutils, which were in the Python
package up to version 2.2.2.
rockstable:~ #
rockstable:~ # zypper update --no-recommends rockstor
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following package is going to be upgraded:
rockstor
The following 4 NEW packages are going to be installed:
libpython3_9-1_0 python39 python39-base python39-devel
1 package to upgrade, 4 new.
Overall download size: 12.8 MiB. Already cached: 0 B. After the operation, additional 37.2 MiB will be used.
Continue? [y/n/v/...? shows all options] (y): n
I am following along here - I did the disbles you mentioned first, then the 2 commands as below:
MERCURY:/ # zypper se python39-devel
Loading repository dataā¦
Reading installed packagesā¦
S | Name | Summary | Type
āĀ±---------------Ā±------------------------------------------------------------------Ā±-------
| python39-devel | Include Files and Libraries Mandatory for Building Python Modules | package
and then:
MERCURY:/ # zypper info python39-devel
Loading repository dataā¦
Reading installed packagesā¦
Information for package python39-devel:
Repository : repo-sle-update
Name : python39-devel
Version : 3.9.18-150300.4.33.1
Arch : x86_64
Vendor : SUSE LLC https://www.suse.com/
Installed Size : 918.6 KiB
Installed : No
Status : not installed
Source package : python39-core-3.9.18-150300.4.33.1.src
Upstream URL : https://www.python.org/
Summary : Include Files and Libraries Mandatory for Building Python Modules
Description :
The Python programming languageās interpreter can be extended with
dynamically loaded extensions and can be embedded in other programs.
This package contains header files, a static library, and development
tools for building Python modules, extending the Python interpreter or
embedding Python in applications.
This also includes the Python distutils, which were in the Python
package up to version 2.2.2.
MERCURY:/ #
I donāt remember installing anything wsdd unless it was a rock-on for Windows Discovery.
Iāll reboot now and see if I can update, and let you know what happens.
Same thing:
MERCURY:/ # sudo zypper update --no-recommends rockstor
Loading repository dataā¦
Reading installed packagesā¦
Resolving package dependenciesā¦
Problem: the to be installed rockstor-5.0.5-0.x86_64 requires āpython39-develā, but this requirement cannot be provided
not installable providers: python39-devel-3.9.10-150300.4.8.1.x86_64[Leap_15_4]
python39-devel-3.9.10-150300.4.8.1.x86_64[repo-sle-update]
python39-devel-3.9.13-150300.4.13.1.x86_64[repo-sle-update]
python39-devel-3.9.14-150300.4.16.1.x86_64[repo-sle-update]
python39-devel-3.9.15-150300.4.21.1.x86_64[repo-sle-update]
python39-devel-3.9.16-150300.4.24.1.x86_64[repo-sle-update]
python39-devel-3.9.16-150300.4.27.1.x86_64[repo-sle-update]
python39-devel-3.9.17-150300.4.30.1.x86_64[repo-sle-update]
python39-devel-3.9.18-150300.4.33.1.x86_64[repo-sle-update]
Solution 1: Following actions will be done:
deinstallation of python310-base-3.10.13-150400.4.36.1.x86_64
deinstallation of libpython3_10-1_0-3.10.13-150400.4.36.1.x86_64
deinstallation of wsdd-0.7.1-lp154.24.1.noarch
Solution 2: do not install rockstor-5.0.5-0.x86_64
Solution 3: break rockstor-5.0.5-0.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/c/d/?] (c):
As another note regarding wsdd - I have this installed - but I donāt even know if I need it at allā¦ not sure why or when I installed thatā¦
@njmike73 , sorry for the delayā¦
Iām wondering where all of this comes from, to be honest, but I wonder if allowing vendor change would help. As you can see, it finds the pyhton39-devel package in the repo-sle-update repo, for instance, so letās see what the resolver says if you specifically allow that (answer no to any change so that we can know for sure):
sudo zypper update --allow-vendor-change --no-recommends rockstor
I hit cancel for nowā¦ here is belowā¦
MERCURY:/ # sudo zypper update --allow-vendor-change --no-recommends rockstor
Loading repository dataā¦
Reading installed packagesā¦
Resolving package dependenciesā¦
Problem: the to be installed rockstor-5.0.5-0.x86_64 requires āpython39-develā, but this requirement cannot be provided
not installable providers: python39-devel-3.9.10-150300.4.8.1.x86_64[Leap_15_4]
python39-devel-3.9.10-150300.4.8.1.x86_64[repo-sle-update]
python39-devel-3.9.13-150300.4.13.1.x86_64[repo-sle-update]
python39-devel-3.9.14-150300.4.16.1.x86_64[repo-sle-update]
python39-devel-3.9.15-150300.4.21.1.x86_64[repo-sle-update]
python39-devel-3.9.16-150300.4.24.1.x86_64[repo-sle-update]
python39-devel-3.9.16-150300.4.27.1.x86_64[repo-sle-update]
python39-devel-3.9.17-150300.4.30.1.x86_64[repo-sle-update]
python39-devel-3.9.18-150300.4.33.1.x86_64[repo-sle-update]
Solution 1: Following actions will be done:
deinstallation of python310-base-3.10.13-150400.4.36.1.x86_64
deinstallation of libpython3_10-1_0-3.10.13-150400.4.36.1.x86_64
deinstallation of wsdd-0.7.1-lp154.24.1.noarch
Solution 2: do not install rockstor-5.0.5-0.x86_64
Solution 3: break rockstor-5.0.5-0.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/c/d/?] (c):
Also not sure if this matters which is in the top right:
Linux: 6.6.1-lp155.6.g1b0014b-default
is there anything else I can do? Like maybe solution 1? will it break something?
Could it be one of my rock-ons?
Just strange that it says ānot installable providersā and all of those are in the listā¦
@njmike73 Just wanted to chip in here re:
That is the linux kernel version (package version actually) that you are running. As a result of:
Which likely comes from the following howto:
Installing the Stable Kernel Backport: Installing the Stable Kernel Backport ā Rockstor documentation
and you have the associated newer filesystems repository also to match the newer version of the kernel than is found in standard Leap:
And regarding:
Could you tell us the history of this install, i.e. was it once a 15.3, and if so did you update it according to the following howto:
Distribution update from 15.3 to 15.4: Distribution update from 15.3 to 15.4 ā Rockstor documentation
Donāt do anything just yet, but it may help for context. Some of the packages involved in this criss-cross of dependencies look like they come from a 15.3, just exploring what may have happened here to help explain what has gone strange.
Incidentally we shall soon be updating our python dependency so this may just go away. But still good to know how it came-to-be. Plus openSUSE Leap are in the throws of introducing a Python 3.11 package set, so we hope to be moving to that.
From a quick look here, it looks like the python3.10 they have introduced along the way, native to 15.4 (python310-base-3.10.13-150400.4.36.1.x86_64) is seen as conflicting with the 3.9 that we depend upon in our testing rpm.
Also note that sometimes a:
zypper refresh
can help, as it refreshes the local database on what is available and what depends on what. This changes all the time. Rockstor will have done that already however, but it may help to try it at the terminal to see if some repository has changed its signing key or the like.
On a Leap 15.4 system I have here I get the following for the Py3.9 dev package:
rleap15-4:~ # zypper se -s python39-devel
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+----------------+---------+----------------------+--------+-------------------------------------------------------------
i+ | python39-devel | package | 3.9.18-150300.4.33.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
v | python39-devel | package | 3.9.17-150300.4.30.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
v | python39-devel | package | 3.9.16-150300.4.27.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
v | python39-devel | package | 3.9.16-150300.4.24.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
v | python39-devel | package | 3.9.15-150300.4.21.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
v | python39-devel | package | 3.9.14-150300.4.16.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
v | python39-devel | package | 3.9.13-150300.4.13.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
v | python39-devel | package | 3.9.10-150300.4.8.1 | x86_64 | Main Repository
v | python39-devel | package | 3.9.10-150300.4.8.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
And actaully they look to have a 150300 ending like yours so that may be a read herring.
Hand in there, you are still likely able to put in all other updates and we are on the move re dependencies currently. Plus soon you will be looking at a distribution update to 15.5 anyway given the near end of life (EOL) for Leap 15.4. Iāve not yet written the howto for that one however.
Incidentally the above Leap 15.4 example does allow for a 5.0.5 to be installed as we have the following:
rleap15-4:~ # zypper info rockstor
Loading repository data...
Reading installed packages...
Information for package rockstor:
---------------------------------
Repository : Local-Repository
Name : rockstor
Version : 5.0.5-2727
Arch : x86_64
Vendor : YewTreeApps
Installed Size : 7.7 MiB
Installed : Yes
Status : up-to-date
Source package : rockstor-5.0.5-2727.src
Upstream URL : https://rockstor.com/
Summary : Btrfs Network Attached Storage (NAS) Appliance.
Description :
Software raid, snapshot capable NAS solution with built-in file integrity protection.
Allows for file sharing between network attached devices.
Which is a development RPM build to ensure installability etc for the now merged 2727 pull request.
Sorry no answers, but we are moving on these things and this may just go away with our next Python dependency update, or a plain old zypper refresh, try that at the command line and let us know here what it states. If it asks to update signing keys they you can agree given the list of repositories you have (they are all official ones).
It may do, not sure in this case as this is part of Leaps ongoing Python update, however Py3.9 and Py3.10 should be able to co-exist. But they are moving to providing Py3.11 which we hope to jump on with our current efforts, but many moving parts currently as we are still mid testing phase so this sort of thing can crop up and then just go away.
Hope that helps, at least for some context.
2 Likes
Hello,
Iām using Opensuse TW with the updated version 5.0.5-0, after a lot of trouble to get it to work (validated on several machines).
The key to a successful update is to wait, wait and wait some more, on average and whatever the power of the base machine. You have to wait more than 2 hours with nothing to do but wait (at best on a console, I display the log
journalctl -f). After this long, long Update delay, I find the web console in perfect working order. My only piece of advice: When you launch an update in test mode of an Opensuse version (TW or Leap) āPatience and length of time, Do more than strength or rage (Jean de La Fontaine)ā.If that helps .
But I have other concerns that Iāll explain in another thread.
1 Like