Dev log for 3.9.1

[suman (suman chakravartula)]

Hello everyone!

3.9.0-9 is now available! We’ve fixed two issues, both enhancements in the backend code contributed by @phillxnet. Thanks Phil!

Issue: Non integer threshold value in SMART data blocks reporting

Issue: support ro rw degraded and skip_balance mount options

[tomo_atlacatl (alex)]

no FTP support

[suman (suman chakravartula)]

Happy Sunday my favourite community!

Happy to share with you that 3.9.0-10 is now available! I’ve added support for changing MTU/Jumbo frames. @ganti_priya fixed a frontend bug with Rock-ons. Thanks Priya!

Issue: Support Jumbo frames config in the UI

Issue: Extra button adding storage to a Rock-On

[suman (suman chakravartula)]

Hello everyone,

3.9.0-11 is now available, actually it’s been available for almost two days. I am just late to this announcement. I closed an AFP related issue and a rock-on related one(thanks @ScarabMonkey for reporting it). Enjoy!

Issue: Don't check for Rock-ons metadata when the service is disabled

Issue: AFP export doesn't expand when underneath share (subvolume in btrfs) expands

[suman (suman chakravartula)]

Happy Saturday RockStorians!

3.9.0-12 is now available. We have a nice refactor in the disk management code by @phillxnet in his quest to perfect it. Secondly, @ganti_priya fixed a frontend issue with rock-ons. Thank you Phil and Priya!

Issue: insufficient use of btrfs device scan

Issue: Rock-on bad behaviour when starting with no configuration

[suman (suman chakravartula)]

Happy Sunday Community!

We are on a roll here, trying to ramp up to the stable release. 3.9.0-13 is now released! @dilli contributed config backup cli, which is pretty cool. Thank you Daniel! I’ve refactored the Pool api to use ids instead of pool names, to simplify things and pave way to implementing features like pool renaming. Enjoy the update!

Issue: add cli initiated config backup

Issue: change Pool API to use ids instead of names

[glenngould (Roland)]

@suman nice to see so many new test releases over the last days

I’m currnetly running on 3.9.0-03 and Rockstor is set to auto update for stable releases.
→ I can’t change the setting to testing channel via web due to the error

I’ve tried the following via the terminal

[root@rockstor ~]# yum upgrade rockstor-3.9.0-13
Loaded plugins: changelog, fastestmirror
Existing lock /var/run/yum.pid: another copy is running as pid 461.
Another app is currently holding the yum lock; waiting for it to exit…
The other application is: yum
Memory : 34 M RSS (419 MB VSZ)
Started: Mon Jun 26 10:01:18 2017 - 06:43 ago
State : Sleeping, pid: 461

This all goes hand in hand with the other thread over here

Unknown internal error doing a POST to /api/commands/update-check

[Please complete the below template with details of the problem reported on your Web-UI. Be as detailed as possible. Community members, including developers, shall try and help. Thanks for your time in reporting this issue! We recommend purchasing commercial support for expedited support directly from the developers.] Brief description of the problem After trying to load “https://ip/#version” Detailed step by step instructions to reproduce the problem [write here] Web-UI screenshot [image…

Any idea how to solve this?

Or is it out of your hands like @Flox indicated some possible EPEL problems

Unknown internal error doing a POST to /api/commands/update-check

Same here, but it seems to be a problem on the repository side. Should be fixed soon, however, according to this: https://www.centos.org/forums/viewtopic.php?t=63018 Postby avij » 2017/06/21 17:44:44 This is an EPEL problem, and EPEL is not managed by CentOS. That said, there has indeed been a problem in EPEL today and fixed EPEL repository files are currently being synced to mirrors. It may take a while. yum clean all may help, and yum update may also work.

Thanks!

[suman (suman chakravartula)]

hi @glenngould,

I would kill all existing yum processes and then try a yum update. If there are errors and depending on what they are, you may have to clean local state with yum clean all and try again. I believe the epel problem no longer exists, at least I don’t see it on our machines here.

[Flyer (Mirko Arena)]

Hi all @glenngould & @suman ,
my 2 cents: with our new Rockstor yum updates over WebUI feature sometimes you can get that yum lock because of a current running yum process (ex.: blinking icon on WebUI telling you about available yum updates means Rockstor had a check over yum for new packages/upgrades)

This usually takes some mins to solve
Mirko

[suman (suman chakravartula)]

Hello Community!

3.9.0-14 is now available! @phillxnet fixed a few issues and made the disk management side of things much better. @ganti_priya made a nice UI enhancement to report user/input errors and backend errors differently. Enjoy the update!

Issue: detached disks used in mount command

add condition to handle user error differently

[glenngould (Roland)]

@Flyer I’m running on 3.9.0-03 which does not have the new yum updates WebUI - even after days there is no change

See my latest reply in the dedicated threat

Unknown internal error doing a POST to /api/commands/update-check

Hi @suman and @Flyer , with reference to your reply in the 3.9.1 development log thread, I post here my reply as it seems to fit better here. https://forum.rockstor.com/t/dev-log-for-3-9-1/3030/34?u=glenngould I’ve used ps -A | grep yum and kill to close all ongoing yum processes. Then I was running yum clean all and after that yum update Now I get the following error, no change over time > [root@rockstor ~]# yum update Loaded plugins: changelog, fastestmirror http://a8c08601-fdad2a03-a3…

[suman (suman chakravartula)]

[root@rockstor ~]# yum update
Loaded plugins: changelog, fastestmirror
http://a8c08601-fdad2a03-a3ac-4680-9b9f-c2ad1f437264:51AMIU2vgQZfkX5KhnRvpA==@updates.rockstor.com:8999/rockstor-stable/repodata/repomd.xml: [Errno 12] Timeout on http://a8c08601-fdad2a03-a3ac-4680-9b9f-c2ad1f437264:51AMIU2vgQZfkX5KhnRvpA==@updates.rockstor.com:8999/rockstor-stable/repodata/repomd.xml: (28, ‘Connection timed out after 30001 milliseconds’)
Trying other mirror.

Are you behind a firewall? I’d check that the box can get out to the internet. and updates.rockstor.com should resolve to 192.195.81.161

[suman (suman chakravartula)]

Happy Canada Day everyone!

3.9.0-15 is now available! I’ve closed two issues in this update. One is a disk api refactor(thanks @phillxnet for testing and reporting issues) and the other is a change to user api to report user actionable errors better. Enjoy!

Issue: change disk api to use ids instead of names

Issue: propagate user errors properly in user management

[glenngould (Roland)]

@suman
I’m behind a simple router firewall, no changes made since months

I’ve tried to ping updates.rockstor.com which showed 192.195.81.208 with 100% loss

Having said this, maybe this additional piece of information is worth to know…that since a while I’m also facing problems that the Rockstor forum is from time to time not available via my internet (LAN) like just now…I’ve to use LTE via my mobile

EDIT / SOLVED:
Looked at my router which was running for more than a year without reboot - initiated a reboot and finally all issues on my Rockstor server regarding updates disappeared - updated immediatly to Rockstor 3.9.1

[Fredrik]

I hope next dev cycle contains the new linux kernel. Alot of exiting stuff in there for BTRFS.

[glenngould (Roland)]

Who dares?
http://elrepo.org/linux/kernel/el7/x86_64/RPMS/