Red Hat Bugzilla – Bug 1375059
[RHEL-6] Include vdsm and related dependency packages at RHGS 3.2.0 ISO
Last modified: 2017-03-23 01:10:24 EDT
Hi Ramesh, Does this mean, vdsm package need to be removed from RHGS-3.2.0-RHEL-6 ISO as well as from "Requires" for redhat-storage-server package?
(In reply to Sreenath G from comment #2) > Hi Ramesh, > > Does this mean, vdsm package need to be removed from RHGS-3.2.0-RHEL-6 > ISO as well as from "Requires" for redhat-storage-server package? Yes. I thought removing the 'Requires' from redhat-storage-server will remove this package from ISO.
RHEL-6 build is available at http://brewweb.devel.redhat.com/brew/taskinfo?taskID=12078568 Moving to MODIFIED
Found that RHEL6.8 RHGS 3.2 ISO is having vdsm packages, not removed as per the bug title from the ISO. ~]# rpm -qa |grep vdsm vdsm-jsonrpc-4.16.30-1.5.el6rhs.noarch vdsm-reg-4.16.30-1.5.el6rhs.noarch vdsm-python-zombiereaper-4.16.30-1.5.el6rhs.noarch vdsm-xmlrpc-4.16.30-1.5.el6rhs.noarch vdsm-cli-4.16.30-1.5.el6rhs.noarch vdsm-yajsonrpc-4.16.30-1.5.el6rhs.noarch vdsm-gluster-4.16.30-1.5.el6rhs.noarch vdsm-python-4.16.30-1.5.el6rhs.noarch vdsm-4.16.30-1.5.el6rhs.x86_64 ~]# cat /etc/redhat-release Red Hat Enterprise Linux Client release 6.8 (Santiago) ~]# cat /etc/redhat-storage-release Red Hat Gluster Storage Server 3.2.0 Moving to assigned state to remove vdsm packages.
Based on decision to support management of rhgs 3.2 nodes via RHGS-C, changing this bug to include vdsm packages in RHGS ISO
I am seeing below vdsm packages in the latest available rhgs3.2 rhel6 iso. [root@ ~]# rpm -qa |grep vdsm vdsm-jsonrpc-4.16.30-1.5.el6rhs.noarch vdsm-reg-4.16.30-1.5.el6rhs.noarch vdsm-python-zombiereaper-4.16.30-1.5.el6rhs.noarch vdsm-xmlrpc-4.16.30-1.5.el6rhs.noarch vdsm-cli-4.16.30-1.5.el6rhs.noarch vdsm-yajsonrpc-4.16.30-1.5.el6rhs.noarch vdsm-gluster-4.16.30-1.5.el6rhs.noarch vdsm-python-4.16.30-1.5.el6rhs.noarch vdsm-4.16.30-1.5.el6rhs.x86_64 [root@ ~]# Moving to verified state with above details.
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://rhn.redhat.com/errata/RHSA-2017-0484.html