Description of problem: ----------------------- HC requires RHV-H to be used as a node. The limited availability version of HC made use of RHEL 7.2 as a platform. RHV-H looks to be ask from the field, and to achieve that, we need to ship RHGS server packages with RHV-H Version-Release number of selected component (if applicable): -------------------------------------------------------------- Not applicable How reproducible: ----------------- Not applicable Steps to Reproduce: ------------------- Not applicable Actual results: --------------- RHV-H base image doesn't include RHGS server packages Expected results: ------------------ RHV-H base image should include RHGS server packages too
Please specify the exact list of packages to be included.
(In reply to Fabian Deutsch from comment #1) > Please specify the exact list of packages to be included. Exact list of packages include : Core-packages of RHGS server includes the following: ---------------------------------------------------- glusterfs-server-3.8.4-x.el7rhgs.x86_64.rpm glusterfs-cli-3.8.4-x.el7rhgs.x86_64.rpm glusterfs-client-xlators-3.8.4-x.el7rhgs.x86_64.rpm glusterfs-api-3.8.4-x.el7rhgs.x86_64.rpm glusterfs-fuse-3.8.4-x.el7rhgs.x86_64.rpm glusterfs-libs-3.8.4-x.el7rhgs.x86_64.rpm glusterfs-3.8.4-x.el7rhgs.x86_64.rpm glusterfs-geo-replication-3.8.4-x.el7rhgs.x86_64.rpm glusterfs-events-3.8.4-x.el7rhgs.x86_64.rpm Major dependency packages required for installing the gluster server packages include : lvm2 nfs-utils psmisc pyxattr rpcbind liburcu-bp.so.1()(64bit)( userspace-rcu ) liburcu-cds.so.1()(64bit) python-prettytable python-requests python-ctypes rsync Note: the above mentioned dependency package list is just few major ones. @Sahina, Is there any packages that I missed in the above list ?
Is there a metapackage for these? Have you thought about one? That list is probably not unreasonable, but it's a surprisingly large number if packages
Installing vdsm-gluster pulls in all the dependency packages - will that do?
That's certainly much nicer than trying to keep track of 9 dependencies (and maybe more in the future) in multiple places. +1 from me for now. I'll what else vdsm-gluster requires.
(In reply to Sahina Bose from comment #5) > Installing vdsm-gluster pulls in all the dependency packages - will that do? Sahina, glusterfs-events package is a new one that comes up with RHGS 3.2.0 for gluster eventing mechanism. Current version of vdsm-gluster doesn't pull glusterfs-events package as dependency. $ rpm -qpR vdsm-gluster-4.18.15.1-1.el7ev.noarch.rpm glusterfs-api >= 3.7.1 glusterfs-geo-replication >= 3.7.1 glusterfs-server >= 3.7.1 python-blivet python-magic rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 vdsm = 4.18.15.1-1.el7ev xfsprogs rpmlib(PayloadIsXz) <= 5.2-1 For RHGS server packages in RHV-H, we need to pull glusterfs-events package separately or should make vdsm-gluster package dependency changes. What do you think ?
We will need the glusterfs-events package only when we use the eventing functionality in oVirt, and will change the vdsm-gluster dependency to require glusterfs-events at that time.
If we aren't using this in vdsm-gluster, do we need it on RHVH?
Note: It would be beneficial if we had a single rpm (like vdsm-gluster) which would pull in all dependencies and which can be used the same way on RHEL and RHVH.
Yes - we will provide all required dependencies as part of vdsm-gluster. (My response regarding glusterfs-events meant that we will add this is a dependency to vdsm-gluster when we start consuming it - till then glusterfs-events is not needed in RHV-H either)
Had verified on rhvh-4.1-0.20170104.0 Below is the package info: [root@dhcp-8-140 ~]# imgbase w [INFO] You are on rhvh-4.1-0.20170104.0+1 [root@dhcp-8-140 ~]# rpm -qa vdsm-gluster vdsm-gluster-4.19.1-1.el7ev.noarch [root@dhcp-8-140 ~]# rpm -qa|grep glusterfs glusterfs-server-3.7.9-12.el7rhgs.x86_64 glusterfs-geo-replication-3.7.9-12.el7rhgs.x86_64 glusterfs-client-xlators-3.7.9-12.el7rhgs.x86_64 glusterfs-3.7.9-12.el7rhgs.x86_64 glusterfs-api-3.7.9-12.el7rhgs.x86_64 glusterfs-cli-3.7.9-12.el7rhgs.x86_64 glusterfs-rdma-3.7.9-12.el7rhgs.x86_64 glusterfs-libs-3.7.9-12.el7rhgs.x86_64 glusterfs-fuse-3.7.9-12.el7rhgs.x86_64 [root@dhcp-8-140 ~]# service glusterd status Redirecting to /bin/systemctl status glusterd.service ● glusterd.service - GlusterFS, a clustered file-system server Loaded: loaded (/usr/lib/systemd/system/glusterd.service; enabled; vendor preset: disabled) Active: active (running) since Mon 2017-01-09 13:52:16 CST; 3 days ago Main PID: 1308 (glusterd) CGroup: /system.slice/glusterd.service └─1308 /usr/sbin/glusterd -p /var/run/glusterd.pid --log-level INFO Jan 09 13:52:05 dhcp-8-140.nay.redhat.com systemd[1]: Starting GlusterFS, a clustered file-system server... Jan 09 13:52:16 dhcp-8-140.nay.redhat.com systemd[1]: Started GlusterFS, a clustered file-system server.
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/RHEA-2017:1114