3.8.16-8 is now released. Please update right away as I’ve fixed a regression I’ve introduced in the previous update that killed the UI(if rebooted or rockstor-pre service restarted). It’s a simple nginx configuration error, but it looks like a major problem.
My thanks and apologies to @phillxnet and @Flyer who came to the rescue of users swiftly. You are the heroes of our community!
For those of you running 3.8.16-7 and no UI, you’ll have to update via the terminal. Please follow these steps
reboot or systemctl restart rockstor-pre rockstor rockstor-bootstrap
We are bit backed up on testing releases and there’s a build related bug that’s preventing me to push updates at this time. Hope to get that going very soon.
After switching from testing to stable channel, you’d need to use yum to downgrade. Something like yum downgrade rockstor should work, though I have not tested that. So make sure to read what it says before accepting to continue the downgrade.
One question before trying any manual downgrade…
As soon as the next stable release 3.9 is out - will Rockstor upgrade automatically from 3.8.16-8 (test release) by having enabled auto update (stable releases) or would there be any manual work needed from my side?
Last couple of weeks have been a roller coaster of problems, but we are finally back on track. 3.8.16-9 was released a few hours ago. We closed two issues in this update. One is a code style fix and the other adds support for 512e HDDs sector size display in the UI. Thank you @chrstphrchvz and @Flyer for your contributions!
We just released 3.8.16-10. Two issues were closed. First is a fix to test code and the second is a significant design improvement to disk roles that will let us support cool new features in the future. This was contributed by @phillxnet and I encourage all code contributors to look at his pull request, we can all learn to be more thorough and document better from it. It was a pleasure to read and review these changes.
Every time i update the rockons service will be turned off after update is complete.
I found that reboot is the best way to get everything up and running nicely. Is this what is expected if so should there not be a prompt showing that reboot is required once the update process is complete or is it a bug?
Looks like some users ran into issues with 3.8.16-11. I have not been able to reproduce the problem on my side. Our systems here have updated without any db migration issue. But we are looking into possible bugs and while we do that, I don’t see a reason to stop further updates. So, 3.8.16-12 is now released!
Two issues are closed in this update, one is a bug fix in config restore and the other a UI fix also having to do with samba config management. Both are contributed by @Flyer. Thank you @Flyer!
3.8.16-13 is now available. I found a bug in the way we are applying migrations and fixed it. This is a painful one that I am glad to have caught before this update. It doesn’t however explain the db issues a few users complained with last update. @Flyer contributed a big change in which our frontend stack is now tidy and style compliant. @phillxnet fixed a input validation bug in our recently added disk role management system. Update away!
Hello guys and gals, 3.8.16-15 is now released! We closed 3 issues in this update. @Flyer fixed a UI bug and a backend bug in initrock. I fixed a django update related regression in replication. Also, I’ve updated our docker packages to 1.13.1.
3.8.16-16 is now released! Two issues were fixed. @Flyer updated fontawesome library we use for various icons on the UI. I fixed a bug where rock-ons were being turned off after a software update. Please test away!