Unable to check update due to a system error

[kupan787 (Ben)]

Here you go:

@phillxnet

yum info rockstor

[root@rocknas ~]# yum info rockstor
Loaded plugins: changelog, fastestmirror, priorities
Loading mirror speeds from cached hostfile
 * base: mirror.fileplanet.com
 * elrepo: repos.lax-noc.com
 * epel: mirror.sfo12.us.leaseweb.net
 * extras: mirror.fileplanet.com
 * ius: mirrors.kernel.org
 * updates: mirror.fileplanet.com
Installed Packages
Name        : rockstor
Arch        : x86_64
Version     : 3.9.1
Release     : 16
Size        : 85 M
Repo        : installed
From repo   : Rockstor-Testing
Summary     : RockStor -- Store Smartly
License     : GPL
Description : RockStor -- Store Smartly

@phillxnet

yum info installed -v rockstor

[root@rocknas ~]# yum info installed -v rockstor
Loading "changelog" plugin
Loading "fastestmirror" plugin
Loading "priorities" plugin
Config time: 0.026
Yum version: 3.4.3
rpmdb time: 0.000
Installed Packages
Name        : rockstor
Arch        : x86_64
Version     : 3.9.1
Release     : 16
Size        : 85 M
Repo        : installed
From repo   : Rockstor-Testing
Committer   : Suman Chakravartula <suman@rockstor.com>
Committime  : Sun Jul  2 05:00:00 2017
Buildtime   : Sun Oct 22 12:36:36 2017
Install time: Mon Oct 23 04:11:46 2017
Installed by: System <unset>
Changed by  : root <root>
Summary     : RockStor -- Store Smartly
License     : GPL
Description : RockStor -- Store Smartly

@phillxnet

I did test the indicated patch as applied to the then testing channel version and it did function as intended so it may be that whatever is causing you problem on your system will be fixed by the changes indicated in that pull request. I suspect that is your fix, but I’m not clear on why I don’t see the same issue here.

Is there a way to manually apply this? Or would I be best to just wait for the new method that @suman is working on to update testing users?

@phillxnet

Sorry I can’t look into this any further as I’m pretty involved in a couple of pending pr’s that I need to ‘bring home’ but let us know how you get on with this one and as always thanks for reporting your findings.

Not a problem. This isn’t a huge issue at this time, as there aren’t updates to apply. I only happened to stumble on to it because I was clicking around in the UI.