I am delighted, and somewhat relieved, to finally announce after more than 2 years of transition from our CentOS base, our first BETA release within our “Built on openSUSE” only testing channel.
We are, as yet, not quite at feature parity with our prior CentOS variant (Stable Channel) but getting very close. The intention is to finally offer a Stable Channel rpm for our “Built on openSUSE” rpms once we have this final beta testing phase completed successfully. As always there are wrinkles and one is that our current target disto Leap15.2 is still in beta; but this is our attempt to skate to where the puck is going. There after the testing channel for the Rockstor4 series will settle into the some what non trivial task of dealing with our other outstanding ‘out-of-date’ elements, Python and Django versions mainly, so it will return to being very much more developers only.
This forum thread picks up in part from the following thread but for a wider audience:
But as we still as yet only have private beta testing releases of our new ‘Built on openSUSE’ installer there are sill a few hoops to jump through. Currently they are all still as documented in the above early-adopters post.
And given we are now on the ‘last leg’ of this rather long and drawn out journey I’m also going to pickup from the following thread/post:
Given we are now deviating away from the CentOS base and can finally concentrate fully on our ‘Built on openSUSE’ endeavour; which is the future of the to-be Rockstor4 variant, I’ll begin this beta changelog thread.
Thanks to all those helping to support this endeavour, either via testing/code/doc contributions or via a Stable Channel subscription.
So this one is just a little tricky. As per this threads into, we have finally tackled one of the all time outstanding feature disparities between our current CentOS based Stable channel and our ongoing ‘same source’ ‘Built on openSUSE’ variant. This ongoing dual distro target approach has in many ways slowed our progress, but we absolutely depend on our Stable Channel subscribers to ‘keep the light on’ so we have maintained compatibility with both distro bases with a priority on our Stable Channel release. But as from this release, our source code is only intended to run on an openSUSE server install with the very specific configurations discussed in the “early-adopters” link. And as such we can finally make the fairly major changes required to support user share functionality on a boot-to-snap, aka rollback capable, system poll that is default on all openSUSE based installs when the system disk is greater than around 17.5 GB. Previously, and share created on the system pool of our ‘Built on openSUSE’ variant, assuming no other issues were in play, would seem to have been created as normal but disappear from the Web-UI upon browser refresh. There were in fact created as btrfs subvols but, as it turns out, in the wrong place. Primarily because were were just plain ‘doing it wrong’ on these boot-to-snapshot root rollback capable systems. Which leads me to a potential wrinkle here. If you are updating from a pre beta ‘Built on openSUSE’ version and you attempted to create a share on the system pool then you will have a little tidying up to do.
There is no migration of these prior user created ROOT pool shares as they were never functional within the Web-UI (as per the early adopter thread), unless you did not have a boot-to-snap config in play, and are only now actually persistent given we now no longer place them in the boot-to-snap root subvol, but more correctly within the @/ subvol akin to the also surfaced with the Web-UI “home”. Please note the following forum post if you want to clean up ‘by hand’ any previously inadvertently created shares in the ROOT pool:
But in all cases, with 3.9.2-58 onwards, post reboot, you should expect to see the following mount details, subvol wise, for the ROOT pool.
If you see mention of “snapshot” within that subvol for the ROOT pool then stuff is not going to work as intended. Look to the logs for clues and it could be that prior use of the ROOT pool, when we ‘did it wrong’ for the openSUSE may be the cause. And given we are now starting a fresh it may just be worth doing a fresh install anyway. Depending on your own btrfs / linux capabilities. Remember that this is our very first beta in the ‘Built on openSUSE’ endeavour and the testing channel is just that. A testing channel for our Stable release developments. We are trying to achieve production capable Stable Channel releases ultimately, via the well trodden but rarely sustainable open source development model. So if you do encounter any strangeness re ROOT system pool shares that is not covered in this announcement and it’s linked threads, then try a fresh start (re-install) beginning with this release or any that superseded it before reporting your issues. That way we have a known datum from which to work.
First off I would like to welcome first time contributor @kupan787 who has effectively updated our scrub reporting to include an ETA and observed rate by interpreting some upstream btrfs improvements, and when they are not found (i.e in when btrfs-progs is not quite new enought) the code adapts accordingly. Nice. This is a long planned Rockstor feature that is now finally here. So thanks again to @kupan787 for stepping up to this task. Aided by the venerable @Flox via a super helpfull code review or two.
The rest are as detailed in the linked issue and as can be seen @Flox, our intrepid forum moderator and code/doc/rock-on/forum contributor has been at it again. Dealing with three independant issues getting us ever close to our next Stable release. Thanks @Flox. And as a matter of interest my initial main pull request for this release (the ROOT shares thing) was also reviewed by @Flox, and lets just say I’m glad it was. Code reviewing is a major part of helping to develop better behaved software, so if anyone feels they can contribute in that fashion then do please step up whenever you see a pull request go in. On occasions a specific reviewer is requested but often times anyone with the capability to review the proposed changes and is able to build the code from source on the indicated distro is more than welcome to do so.
I would also like to thank recent forum member @freaktechnik, for stepping up to some early testing in our pre-beta testing channel related to this release. The SFTP issue referenced was submitted by them and they have now duely confirmed it’s fix.
So bit by bit and thanks to all those continuing to chip in here.
Finally, as always, a special thanks to all Stable channel subscribers without whom this whole endeavour would be unsustainable. The Rockstor 4 ‘Built on openSUSE’ days are nearing.
I am delighted to be releasing our second ‘Built on openSUSE’ beta rpm version. The main upset (we are in the testing channel here) as per the header, is that we have a new signing key. This one is my fault as I wanted to get this chicken/egg problem over and done with for the next keys duration (5 years) before we began our new Stable channel releases. All that is required is to re-run the prior rpm key import command introduced in our ‘… early adopters…’ post. Namely:
Then all should be set in this regard for the next 5 years (hopefully ).
As usual all rpms were build natively on their target distro platforms but of note in this release is that our base openSUSE Leap15.2 distro has turned from it’s prior beta status to Release Candidate (RC), and Tumbleweed has been build, from the ground up, with gcc10.1. All build systems were fully updated prior to their respective build tasks so if you do have any issue make sure your systems are fully updated.
To the change points. Again, as usual, I would like to thank @Flox the intrepid, who in responsible for 2 of the 3 changes in this changelog:
establish new rpm/repo/project signing key ready for relaunch. Fixes #2176 @phillxnet
Configure SFTP server at buildtime and update customization settings. Fixes #2168 @FroggyFlox
I have already covered the new signing key, ready for the ‘Built on openSUSE’ Stable Channel re-launch, and as is our current focus both of @Flox’s linked issues also concern our pending re-launch. There has also been a few changes in our backend build system as we prepare for the pending Rockstor4 Stable Channel re-lanuch (Built on openSUSE only). @Flox has also been helping greatly with our closed beta installer release. We have a few odds and ends to sort on that front that has begun to slow our normal release cadance but once sorted we should be back to normal but with a shiny new installer.
Thanks also to all our testers. We do have a little way to go and I’m slowly working though my own backlog but we are getting there. If you have submitted a bug of late please be patient as this has ended up being quite the journey. Also note that we are now no longer able to build on CentOS. But as we are now almost at feature parity we should soon be able to recommend folks use our new installer anyway. A call will be put out here for beta installer testers shortly. But given our target re-launch distro platform is Leap 15.2 we have a few short weeks before it’s final release anyway. So do please keep the bug reports rolling and we can see what we can make of all this.
So in that light I would like, as usual, to thank our Stable Channel subscribers without whom this whole endeavour would be unsustainable. The Rockstor 4 ‘Built on openSUSE’ days are nearing.
In this release I would like to welcome another new contributor, mcbridematt (on GitHub) with what was our 800th pull request merge in the main git repo. In this case an exciting move toward AArch64 compatibility; in which mcbridematt has non trivial expertise. Nice. Encouraged by this contribution and mcbridematt multi year interest in Rockstor behind the scenes, I’ve set to on popping in a couple of trivial arm64 compatibility improvements myself.
And I would also like to thank forum members and intrepid testers @Azzazel, @Zonk, and @kupan787 for their reporting, and patience, with regard to the remaining change detailed above, that of Rockstor’s inability to allow for the removal of ‘detached’ disk in some (read a lot) of circumstances. This was predominantly cosmetic but was also a functional hole in our more recently re-vamped disk/pool management systems. And thanks as usual to our talented forum moderator and across the board contributor @Flox for also reviewing this long awaited fix. Please note that the Changelog entry within the rpm only includes the first “Fixes” link for this last detailed issue as we have an outstanding bug where our Web-UI can only link successfully to a single issue.
So thanks again to all our testers. We are getting there, bit by bit, but only with the continued help and experimentation of those happy to chip in where they can with their time and expertise. Your contributions are of course much appreciated. Soon we should be able to move an ‘earmarked’ rpm from testing to our ‘Built on openSUSE’ Stable channel repos. So again, please keep all bug reports rolling as we do, soon, need to move onto our ‘other’ technical debts of moving to Python 3 et al (read Tumblweed again). Which is the intended next focus for the testing channel once we have a workable ‘Built on openSUSE’ stable release rpm out and about.
Oh, and did I mention we have AArm64 rpms now; natively build, as per all our rpms, on their target distro and architecture.
Finally; thanks to our Stable Channel subscribers, without whom this whole endeavour would be unsustainable. The Rockstor 4 ‘Built on openSUSE’ re-release is just around the corner, just in time for Leap 15.2’s official release.