Rockstor version in webUI discrepancy

Flox · January 5, 2018, 1:03pm

Hi,

The Rockstor version displayed in the webUI does not fit the one reported by the system.

I haven’t paid attention to this part of the webUI in a little bit so I don’t know whether this is known or not (I apologize if this is a duplicate).

My webUI reports version 3.9.2-10:

But on the cli, I have 3.9.2-1 (which is indeed what I am expecting as I haven’t updated yet).

[root@rockstor ~]# yum info rockstor
Loaded plugins: changelog, fastestmirror
Existing lock /var/run/yum.pid: another copy is running as pid 10406.
Another app is currently holding the yum lock; waiting for it to exit...
  The other application is: yum
    Memory :  40 M RSS (1.4 GB VSZ)
    Started: Fri Jan  5 07:56:09 2018 - 00:02 ago
    State  : Sleeping, pid: 10406
Loading mirror speeds from cached hostfile
 * base: repos.dfw.quadranet.com
 * epel: reflector.westga.edu
 * extras: centos.mirrors.tds.net
 * updates: centost5.centos.org
Installed Packages
Name        : rockstor
Arch        : x86_64
Version     : 3.9.2
Release     : 1
Size        : 85 M
Repo        : installed
From repo   : Rockstor-Stable
Summary     : RockStor -- Store Smartly
License     : GPL
Description : RockStor -- Store Smartly

Available Packages
Name        : rockstor
Arch        : x86_64
Version     : 3.9.2
Release     : 10
Size        : 15 M
Repo        : Rockstor-Stable
Summary     : RockStor -- Store Smartly
License     : GPL
Description : RockStor -- Store Smartly

Nothing damaging but I simply wanted to report this if it is indeed a bug.

FYI, I am on Stable updates, but without automatic updates.

phillxnet · January 5, 2018, 1:23pm

@Flox Hello again. Yes this was a bit of a chicken and egg one and is now sorted but only once you update via command line. Bit of a pain but we can look to a GUI manual override going forward because ‘as is’ when this went wrong it didn’t give an option to update in the UI: hence the chicken and egg. The issue and associated pr were as follows:

https://github.com/rockstor/rockstor-core/issues/1870

and it’s associated pull request / fix was:

github.com/rockstor/rockstor-core

version and date incorrectly reported re update info. Fixes #1870

rockstor:master ← phillxnet:1870_version_and_date_incorrectly_reported_re_update_info

opened 06:24PM - 10 Dec 17 UTC

phillxnet

+7 -6

A recent move to yum from rpm inadvertently caused a miss reporting of installed… version for that of available version. This was due to the differing outputs and the inclusion of both installed and available in the newer yum format. The command switch set was revised to output only the installed version and to include the previously missing and required build date/time info. Consequent parsing adjustments were made to accommodate for the now changed date format. Time info was excluded as it is not used. @schakrava Ready for review. Fixes #1870 Please see issue text for stable package test / validation procedure. As there are currently existing anomalies in package change log dates and contents re recently added minor version numbers this must be resolved in future package releases for the intended function of the "List of changes in this update" to correctly populate. See issue text for details. Currently it will be blank for the more recent stable package releases but should work as intended when the date anomalies are resolved in future package releases (ie when package changelogs indicate the time of release). Also tested by applying to a fresh 3.9.1-0 install pre and post testing channel subscription and thereafter then updating via command line to 3.9.1-15. In all instances installed and available were displayed correctly. An update from 3.9.1-15 to 3.9.1-16 was then successfully completed via the command line.

If you were to update to an interim version you should see that it now correctly reports a newer available update (this is how I re-tested it after it was release); or just update straight to latest and await the next update to test.

Pretty sure the fix was released in 3.9.2-6.

Hope that helps and thanks for the report: far better a duplicate than we miss something entirely. And I am currently working on reviving some unit tests so hopefully, in time, we should have more safe guards against this sort of failure.

Thanks for helping to support Rockstor development.

Flox · January 5, 2018, 1:57pm

Thanks for the detailed info, and sorry I missed these.