Red Hat Bugzilla – Bug 1559507
[RFE] Show downstream Gluster version in list of clusters
Last modified: 2018-09-04 03:04:26 EDT
Created attachment 1411798 [details] screenshot of cluster list on RHGS WA 3.3 Description of problem ====================== Gluster version shown in cluster list in WA interface should be *downstream* (RHGS) version, rather than *upstream* (rpm package) version, which is shown in the web interface now. This RFE is based on Sayan's suggestion from 2018-03-21 RHGS WA demo. Version-Release number of selected component ============================================ tendrl-ui-1.5.4-6.el7rhgs.noarch Other WA packages on the server server machine: tendrl-ansible-1.5.4-7.el7rhgs.noarch tendrl-api-1.5.4-4.el7rhgs.noarch tendrl-api-httpd-1.5.4-4.el7rhgs.noarch tendrl-commons-1.5.4-9.el7rhgs.noarch tendrl-grafana-plugins-1.5.4-14.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.5.4-14.el7rhgs.noarch tendrl-node-agent-1.5.4-16.el7rhgs.noarch tendrl-notifier-1.5.4-6.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.5.4-6.el7rhgs.noarch Steps to Reproduce ================== 1. Import RHGS trusted storage pool into RHGS WA 2. Navigate to list of clusters and see gluster version reported there. 3. Check gluster version on one of storage server by running both: * cat /etc/redhat-storage-release * rpm -q glusterfs Actual results ============== The clusters page reports version: "gluster 3.12.2". This matches rpm version of the package: ``` # rpm -q glusterfs glusterfs-3.12.2-5.el7rhgs.x86_64 ``` While the downstream product version is: ``` # cat /etc/redhat-storage-release Red Hat Gluster Storage Server 3.3.1 ``` Expected results ================ The cluster list shows downstream product version: RHGS 3.3.1 Additional info =============== File redhat-storage-release belongs to redhat-storage-server package: ``` # rpm -qf /etc/redhat-storage-release redhat-storage-server-3.3.1.0-1.el7rhgs.noarch ``` and it seems that it's not dependency of any other package, so it could happen that trusted storage pool doesn't have it installed. How should we tackle it? Is it ok to try to install it (eg. during import)? How should we proceed if the only thing which fails is installation of this package? Also note that if we decide to make sure redhat-storage-server package is installed during import, what to do with cluster which has been imported with older version which shows upstream (rpm package) version?
Martin based on https://bugzilla.redhat.com/show_bug.cgi?id=1559507#c2 and further discussion I don't think we are still in conclusion stage to take this. Nishanth, do we need this to take through PMs and see option-2 suggested in https://bugzilla.redhat.com/show_bug.cgi?id=1559507#c3 can actually be adopted (or whatever comes out as suggestion).
I am not in favour of above suggested solution as the version display is not consistent in different scenarios which might be confusing. I will vote for showing the rpm version(upstream) or no display at all on UI @Sayan, Could you please provide your inputs here?
I've tested following successful scenarios: * with glusterfs-3.12.2-10.el7rhgs.x86_64 - shows RHGS 3.4.0 * with glusterfs-3.8.4-54.8.el7rhgs.x86_64 - shows RHGS 3.3.1 * with glusterfs-3.8.4-44.el7rhgs.x86_64 - shows RHGS un-supported Tendrl Server: tendrl-ansible-1.6.3-3.el7rhgs.noarch tendrl-api-1.6.3-3.el7rhgs.noarch tendrl-api-httpd-1.6.3-3.el7rhgs.noarch tendrl-commons-1.6.3-4.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-2.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-2.el7rhgs.noarch tendrl-node-agent-1.6.3-4.el7rhgs.noarch tendrl-notifier-1.6.3-2.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-1.el7rhgs.noarch Gluster Storage Servers: tendrl-collectd-selinux-1.5.4-2.el7rhgs.noarch tendrl-commons-1.6.3-4.el7rhgs.noarch tendrl-node-agent-1.6.3-4.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch >> VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2616