5.0.1-0
Released in testing channel updates on 24th July 2023.
Overview
DEVELOPERS ONLY AGAIN:
As we have now significantly updated our Python in the prior release of 5.0.0-0 we have had to employ a brute force wipe of the virtual environment we actually run in/on! This will be happening for the forceable future in testing updates. See: (t) in wiping venv we need to restart all services · Issue #32 · rockstor/rockstor-rpmbuild · GitHub for future plans to smoothing out this mechanism. So:
command line reboot may be requried
once this update has completed.
What’s Changed
- (t) Failure to check for updates in locales other than en_US #2627 by @phillxnet in #2628
- venv not updating re python version change #2626 by @phillxnet in #2629
Thanks to @Mark93 & @eriklysoe for reporting and helping to diagnose these issues.
Also thanks to @Flox for helping extensively with both the above issues.
Also thanks to @StephenBrown2 for taking a looks at our ongoing development - we nearly go a pull request in by them but unfortunately there was just too much going on with these issues which needed to be addressed before we have the feature addition associated with their ongoing pull request.
Test away and report rapidly as we work against the forces of kipple.
5.0.2-0
Released in testing channel updates on 2nd August 2023
Overview
DEVELOPERS ONLY - we are still early on in the new testing phase.
Thanks to @Flox and forum members @agjbond007 and @anborn for helping to identify a zypper dup related issue that left older (but distribution updated) rockstor installs with an incompatibility re pg_config availability. This has now been resolved in this update. If you were affected and have not applied the issue-linked forum fix then a cli update to this version and rebooting there-after should fix things. All helps with improving our robustness re updates so many thanks all-around there.
And we have a feature add by forum member @StephenBrown2, a now long in the tooth Rockstor users (returning contributor) who has enabled ZSTD compression within our Web-UI (default level for now). Nice. And as always much appreciated.
And of course thanks to our intrepid forum moderator @Hooverdan for helping here, there, and everywhere .
What’s Changed
- user admin enable without password change not internal error #2635 by @phillxnet in #2636
- Improve OS independence re unit tests #2633 by @phillxnet in #2637
- Add option for ZSTD compression #2618 by @StephenBrown2 in #2619
- resolve indeterminate or inappropriate postgresql alternative conf #2632 by @phillxnet in #2638
New Contributors
@StephenBrown2 made their first contribution in #2619
Test away and report rapidly as we work against the forces of kipple.
5.0.3-0
Released in testing channel updates on 19th August 2023
Overview
DEVELOPERS ONLY - we are still early on in the new testing phase.
Thanks to @Flox (co-maintainer) and @Hooverdan (forum moderator and all around help).
As always thanks also to all those attributed below for development/review/issue work. And to forum members @marciopamplona (reporting our ghosting of prior config-backups) and @eriklysoe for confirming the same. @Hooverdan & @Flox worked out what we (read my mistake) had missing in our rpm scriptlets during update using our new Poetry build/deploy system. I have provided a fix in this release for the core issue here, but we have (as always) more room for improvements in this area.
We also have some on-boarding and development niceties comming in with this release and @StephenBrown2 has followed up with yet more compression improvements within the Web-UI. Following-up on their prior introduction of zstd as a compression option.
Overall we have a number of update/development improvements that should help with easing the dependency updates we have planned.
What’s Changed
- Update .gitignore with Rockstor build artifacts #2644 by @StephenBrown2 in #2643
- Address compression cosmetics #2640 by @StephenBrown2 in #2641
- Establish on_delete for ForeignKey re Django update #2645 by @phillxnet in #2648
- Web-UI update fails to recreate venv #2652 by @FroggyFlox @phillxnet in #2654
- Enhance development ease #2653 by @phillxnet in #2655
- Improve Web-UI update re systemd service management #2651 by @phillxnet in #2656
- Improve rockstor.service re robustness #2657 by @phillxnet in #2658
- (t) Update django-pipeline to 1.7.0 #2646 by @FroggyFlox in #2659
- Save and Restore config back-up files during rpm update #2660 by @Hooverdan96 @phillxnet @FroggyFlox in #2661
Test away and report rapidly as we work against the forces of kipple.
5.0.4-0
Released in testing channel updates on 15th September 2023
Overview
DEVELOPERS ONLY - we are still early-mid cycle in our current testing phase.
Thanks to @Flox (co-maintainer) & @Hooverdan (forum moderator and all around help).
This update is the first for a while to not include any changes to our rpmbuild specification. This is a good thing and follows-on from a series of recent changes to fix various update issue that were reported here on the forum. This time around, post 5.0.3-0, we have had no such reports. Time will tell if we have these all resolved now, so keep an eye out; as always.
This release concerns mainly some preparation/fixes re our next Django update, and some AD/LDAP fixes/improvements: thanks to @Flox for these, and recent form member @bhotrock for reporting and assisting with the latter. We also have a nice user experience upgrade from @Hooverdan re our new, more obvious display of our “Uses openSUSE Leap/Tumblewed …” OS version.
What’s Changed
- Migrate to New Middleware style #2662 by @FroggyFlox in #2663
- Use user.is_authenticated as an attribute #2664 by @FroggyFlox in #2665
- Set
Meta.base_manager_name
on ‘storageadmin.Disk’ #2666 by @FroggyFlox in #2667 - surface Distro Version to breadcrumb bar #2668 by @Hooverdan96 in #2670
- Explicitly set REALM when querying workgroup #2671 by @FroggyFlox in #2672
- Catch DBusException to not throw error on LDAP group lookup #2673 by @FroggyFlox in #2674
- Bump versions to a 5.0.4 base (Testing) - testing branch #2675 by @phillxnet in #2676
Test away and report rapidly as we work against the forces of kipple.
5.0.5-0
Released in testing channel updates on 19th October 2023
Apparently this is our 100th GitHub Release
Overview
DEVELOPERS & TESTERS - we are more like mid cycle in our current testing phase now.
Thanks to @Flox (co-maintainer) & @Hooverdan (forum moderator and all around help).
Here we have a continuation of our technical dept resolution. Bit by bit.
We also have some improvements re Rock-on definition retrieval. Thanks to @Hooverdan & @Flox working with forum members @greven, @jimla1965 to help to highlight and investigate this issue. We should now take around 1/3 of the time, and we run this task in a better thread type. If you had this problem before, please report here on the forum if it is now fixed for you.
And … drum roll … @Flox has done our initial Tailscale intergration.
This one will definitely need some domain expertise (that I don’t have) so if you use Tailscale, please given this new service a try. It will not work without first by-hand following an upstream Tailscale repo addition and install. See the following comment from an issue in our rockstor-install for install instructions: Pre-install Tailscale · Issue #142 · rockstor/rockstor-installer · GitHub
Also note we have a current blocker on our TW/arm64 target: Tumbleweed-aarch64 .venv build fails on gevent wheel · Issue #2693 · rockstor/rockstor-core · GitHub
What’s Changed
- Don’t throw exception when getting supervisord service status #2681 by @FroggyFlox in #2682
- Add PyCharm rock-tests run config #2686 by @phillxnet in #2687
- Provisional Django 2.2 LTS update #2625 by @phillxnet in #2690
- Update Python dependency to 3.9 #2691 by @phillxnet in #2692
- Update django-pipeline to latest #2689 by @phillxnet in #2694
- Update Django REST Framework within Django version constraint #2695 by @phillxnet in #2697
- Update python-socketio & python-engineio to latest #2591 by @phillxnet @Hooverdan96 in #2701
- Update Requests library to latest #2704 by @phillxnet in #2705
- Update gunicorn to latest - use gthread - discrete config file #2702 by @phillxnet in #2706
- Use single https session to retrieve all rock-on definitions #2707 by @phillxnet in #2708
- remove django-braces dependency #2709 by @phillxnet in #2711
- Implement Tailscale service #2679 by @FroggyFlox in #2712
- Bump versions to a 5.0.5 base (Testing) - testing branch #2715 by @phillxnet in #2716
Test away and report rapidly as we work against the forces of kipple.
5.0.6-0
Released in testing channel updates on 16th January 2024
1st Stable Release Candidate (RC1)
As can be seen by these changes and those preceeding it in our ongoing 5.0.* testing phase: we are in process of updating our base dependencies. And hopefully fixing all that ‘falls’ in the process. This release is marked RC1 as we now need wider testing to begin our push towards a more production/tested release that we can promote as Stable. Our last of which was 4.6.1-0 (after 4.1.0-0 before it), and our next intended Stable release version will be 5.1.0-0, if our plans pan-out.
Overview
We now run on Python 3.11 and Django 4.2 LTS; and have updated all our Python dependencies to their latest versions, as of each updates implementation. This was the primary, and rather ambitious goal of this current testing phase.
There are inevitably regressions, with such fundamental updates, and one particularly gnarly one has been our replication code: this had many Py2.7isms and we paid for this in the delay getting to this release. Thanks to forum member @niko for their reporting on this regression. It is now expected that we have restored our prior stable version replication function with this release. There will inevitably be improvements to be made but initially we needed what we had in our last stable release: at least.
As usual I would like to thank all testers, developers, & reporters, and specifically @Flox and @Hooverdan for their stellar efforts across the project.
Caveats
With this release we have now adoped a proper secrets management system. As such, the default/predefined/special-case cliapp credentials had to be redefined. This will break all existing replication and is unavoidable with our other ongoing update orientated goals. However replication in this testing phase has been broken for some time now. But for those intending to update to this release who rely-on, or are willing to test replication: you will need to re-establish any existing replication configuration. Just start over to be sure of a clean start.
See our current GitHub Milestone for context:
What’s Changed
- Fix mocking insufficiencies in system.network.py #2717 by @FroggyFlox in #2718
- Use regular expressions to validate tailscale hostname #2714 by @FroggyFlox @Hooverdan96 in #2719
- SyntaxWarning: “is not” with a literal #2713 by @phillxnet in #2722
- Address redundancy re database setup #2729 by @phillxnet in #2733
- Update django-oauth-toolkit #2710 by @phillxnet in #2727
- Ease database diagnosis via local IP access configuration #2730 by @phillxnet in #2736
- Update Django to next LTS #2734 by @phillxnet in #2737
- Update Huey task queue library #2731 by @phillxnet in #2741
- Update Django-rest-framework to latest #2738 by @phillxnet in #2743
- Update dbus python dependency to latest #2744 by @phillxnet in #2745
- Update pyzmq dependency to latest #2746 by @phillxnet in #2747
- Update Django to latest 4.2 LTS #2750 by @phillxnet @Hooverdan96 @FroggyFlox in #2752
- update to latest psycopg 3 #2740 by @phillxnet in #2753
- Update Poetry build system & normalise on Python 3.11 #2703 #2754 #2693 by @phillxnet @FroggyFlox in #2755
- Add/Update help icon linking to docs #2720 by @FroggyFlox in #2725
- Adopt dedicated secrets management library #2728 by @phillxnet in #2758
- Make explicit to systemd our NetworkManager dependency #2685 by @phillxnet in #2762
- Replication secret encrypted in Web-UI #2759 by @phillxnet in #2764
- Account for eventual double slahes in the conversion from legacy to poetry paths #2757 by @FroggyFlox in #2771
- (t) replication spawn error #2766 by @phillxnet in #2777
- Bump versions to a 5.0.6 base (Testing) - testing branch #2778 by @phillxnet in #2779
Test away and report rapidly as we work against the forces of kipple.
5.0.7-0
Released in testing channel updates on 29th January 2024
2nd Stable Release Candidate (RC2)
Note, there were a few surprised reporters here on the forum that our TESTING-channel-only release of RC1 (5.0.6-0) rpm failed to update from a number of older releases. This is entirely normal, every rpm we publish is tested before release for it’s fresh install capability (no .initrock so DB wipe). But updates, from any prior install (regardless of channel), are in no way guaranteed/tested/indicated-as-working. But given that; as we enter the last stage of each testing phase (RC* releases) we begin, resources/contributions/time allowing, to make best efforts on updating from the last Stable release only (currently 4.6.1-0). But given the extensive changes we have made, and usually make in each testing run, this often also ensures updates from any prior testing version in the current phase: but only later on in said phase.
Overview
With the above as context, we got our much appreciated high quality feedback from forum engaged testers/developers to further our collective effort. Special thanks to @KarstenV for their patient and productive persistence engaging with our stalwart Open Collective team members of @Flox & @Hooverdan. The result diagnosed some subtle issues (cause not effect ) around our very first Poetry update combined (happenstance - looking on the bright side) by way of yet-another Django update; with a PostgreSQL format incompatibility.
We have now, in this testing phase alone, updated virtually every dependency we have; some, like our Python and Django versions, as many as 3 times each. This step-by-step approach was taken to maintain a fresh install rpm capability during all these changes. Greatly easing community engagement/feedback on our priorities and progress. And further testing our developing update mechanisms. The testing channel is our way to reach production quality releases, consequently the first stable release rpm is always also published in testing first (at the end): as a result of our existing methods, unchanged for the lifetime of the project.
All 3 functional changes in this release pertain to testing-channel-only rpm update regressions introduced/reported/uncovered in our last testing rpm. Thanks also to @hmete1, @Warbucks, and @phemmy22 for their positive engaging on these and other issues here on the forum. We still have some ‘5.1.X-X Stable release’ Milestone issues to address, and are open to adding smaller ones if well defined.
What’s Changed
- Failure to remove legacy poetry version in 5.0.6-0 rpm #2782 by @phillxnet in #2784
- Establish Postgres database format upgrade #2780 by @phillxnet in #2787
- Failure to re-create venv - pre 5.0.3-0 updating to 5.0.6-0 rpm #2788 by @phillxnet in #2790
- Bump versions to a 5.0.7 base - testing branch #2791 by @phillxnet in #2792
Test away and report rapidly as we work against the forces of kipple.
5.0.8-0
Released in testing channel updates on 12th Feburary 2024
3rd Stable Release Candidate (RC3)
Thanks to @Mark93, @Warbucks, @DrHolzer, @Tex1954, @McFaul for some excellent reporting, diagnostic, & confirmation efforts here on the forum with the venerable @Flox & @Hooverdan . We have here a specific fix for an SMB export regression introduced in 5.0.6-0 and persisted in 5.0.7-0 testing channel releases. The fix rolls in a more centralised approach to managing our environmental variables under Poetry; the root cause of the issue indicated: lack of universal access to a required environmental variable associated with our new-in-5.0.6-0 dedicated secrets management.
- Adopt dedicated secrets management library #2728 by @phillxnet in #2758
We also have an unburdening of our prior excessive use of rpm’s %posttrans scriptlet. We had rather over-stretched its intended use I think. Hence the adoption of a new rockstor-build.service to more easily surface issues associated with our build.sh script: in-turn associated with a number of update failures experienced in this and the last testing phases. Future such issues should now be easier to identify and resolve on testing instances. There has also been an improvement in our debug content of the now well appreciated poetry-install.txt file!
For all those involved in the current SMB export investigations: please also note the following ongoing (open) issue:
What’s Changed
- Add rockstor-build systemd service #2793 by @phillxnet in #2795
- (t) Samba shares not accessible - 5.0.6-0 & 5.0.7-0 #2794 by @phillxnet @FroggyFlox @Hooverdan96 in #2797
- Bump versions to a 5.0.8 base - testing branch #2800 by @phillxnet in #2801
Test away and report rapidly as we work against the forces of kipple.
5.0.9-0
Released in testing channel updates on 19th April 2024
4th Stable Release Candidate (RC4)
As usual: thanks to all those who have helped here on the forum, in GitHub issues (i.e. GitHub user ubenmackin’s estensive reporting/interactions re “Disk miss-attribution to ROOT”) and in side channel chats/support email.
The main fixes here are hopefully the last remaining issues re our multiple Python updates within this single testing phase (now on Py3.11), a re-vamp/extensive clean-up/simplification of our lowest level of drive/pool management, and a lot of background maintenance updates to our first-and-more order dependencies. Plus a few Web-UI tidies.
An interesting, and long awaited (by me) improvement that has come from the low-level disk management re-do, is our new stance on the ROOT (OS/System) Pool. We no longer recommend that this is ever imported/used. It import option is now marked as “Advanced Users Only”: however this will only be evident on completely fresh install. I’ll try and cook-up a DB command to return existing installs to this state: as it has some significant Web-UI speed/usability improvements associated with it. The ROOT pool is never really managed by Rockstor’s Web-UI and that has to always be the case: and we should strongly discourage its use from now on. This new stance further enforces a separation of OS from Data. And the ‘ROOT’ pool that we inherit from upstream is actually pretty complex given we enforce a boot-to-snapshot capability. And our ‘view’ of it has always been very simplified. Again, existing installs updating to this version will maintain their existing ‘ROOT’ Pool managed status. But plan on this not being the case for fresh installs resulting from all future installers.
What’s Changed
- Replace raw_input() with input() #2803 by @Hooverdan96 in #2804
- Scheduled shutdown task fails due to type issue #2805 by @phillxnet @Hooverdan96 in #2812
- [t] Add Group with custom GID fails with type error #2807 by @phillxnet @Hooverdan96 in #2815
- TypeError when deleting unused Rocknet #2814 by @phillxnet @FroggyFlox in #2817
- Change Quota Status Display Wording #2810 by @Hooverdan96 in #2818
- Adapt net interface delete to ‘rockstor’ service null config #2819 by @phillxnet in #2822
- Modernise scan_disks() - no functional change intended #2826 by @phillxnet in #2827
- Unit test improvements re Disk miss-attribution to ROOT pool #2828 by @phillxnet in #2829
- Un special-case system drive btrfs-in-partition treatment #2824 by @phillxnet in #2835
- DRF, Django LTS, and Gunicorn maintenance updates #2820 by @phillxnet @FroggyFlox in #2836
- Bump versions to a 5.0.9 base - testing branch #2837 by @phillxnet @FroggyFlox in #2838
Test away and report rapidly as we work against the forces of kipple.
5.0.10-0
Released in testing channel updates on 17th June 2024
5th Stable Release Candidate (RC5)
Our usual thanks to all those who have tested and reported here on the forum to get us ever close to our first 5.1.x-x Stable release. Special mention this time to our intrepid forum moderator and all-over contributor @Hooverdan who found a rather prominent bug that crept in at 5.0.6-0 and remained through to 5.0.9-0: see changelog below for details. As always we have also @Flox to thank for yet more investigations & interpretations.
Due to the imminent Stable release, and the fact that our recently refreshed downloadable installers (including one based on openSUSE Leap 15.6) contain this bug where, an upstream default wasn’t, I’ll get to publishing quickly.
What’s Changed
- 5.0.6-0 to 5.0.9-0 Configuration Backup file upload fails #2846 by @Hooverdan96 @FroggyFlox @phillxnet in #2850
- Routine update of dependencies #2849 by @phillxnet in #2851
- Bump versions to a 5.0.10 base - testing branch #2848 by @phillxnet in #2852
Test away and report rapidly as we work against the forces of kipple.