Description of problem: see $subject Version-Release number of selected component (if applicable): master 4/4/2016 You are on ovirt-node-ng-007-1.el7+1 How reproducible: always please provide glusterfs pacakages to support adding glusterfs domains.. list of packages on a rhel 7.2 node glusterfs-client-xlators-3.7.1-16.el7.x86_64 glusterfs-rdma-3.7.1-16.el7.x86_64 glusterfs-3.7.1-16.el7.x86_64 glusterfs-api-3.7.1-16.el7.x86_64 glusterfs-api-devel-3.7.1-16.el7.x86_64 glusterfs-debuginfo-3.7.1-16.el7.x86_64 glusterfs-fuse-3.7.1-16.el7.x86_64 glusterfs-libs-3.7.1-16.el7.x86_64 glusterfs-devel-3.7.1-16.el7.x86_64 glusterfs-cli-3.7.1-16.el7.x86_64
Gil, i am not sure if these packages should come by default. Should they?
(In reply to Tareq Alayan from comment #1) > Gil, > i am not sure if these packages should come by default. Should they? If it's exist on the legacy node as you mentioned in comment #0, it mean we must include it in next gen node too. This makes this BZ a regression actually.
Yes, these packages: glusterfs-client-xlators-3.7.1-16.el7.x86_64 glusterfs-cli-3.7.1-16.el7.x86_64 glusterfs-rdma-3.7.1-16.el7.x86_64 glusterfs-3.7.1-16.el7.x86_64 glusterfs-api-3.7.1-16.el7.x86_64 glusterfs-fuse-3.7.1-16.el7.x86_64 glusterfs-devel-3.7.1-16.el7.x86_64 glusterfs-libs-3.7.1-16.el7.x86_64 does exists in Red Hat Enterprise Virtualization Hypervisor release 7.2 (20160330.0.el7ev) However these pacakages doesn't come by default in RHEL node. Thanks
Allon, how do we plan to express gluster dependencies? Should vdsm require them? Or should not explicitly pull them in?
(In reply to Fabian Deutsch from comment #4) > Allon, how do we plan to express gluster dependencies? > > Should vdsm require them? > Or should not explicitly pull them in? The current approach is that VDSM is not allowed to require them, as they are delivered by a separate RHGS channel that not all customers will have, and thus will fail the yum install for those customers. node should explicitly pull them in, unfortunately.
Thanks Allon. I also checked, in legacy Node we also carry the glusterfs client packages: recipe/common-pkgs.ks:glusterfs-devel recipe/common-pkgs.ks:glusterfs-fuse recipe/common-pkgs.ks:glusterfs-rdma recipe/fedora-pkgs.ks:glusterfs-client Douglas, can you please add these packages as dependencies to the host-node release?
should this also be backported to 3.6?
(In reply to Tareq Alayan from comment #7) > should this also be backported to 3.6? Yes.
They now got backported to 3.6and will turn up in the builds next week.
Version ovirt-node-ng-installer-master-2016053104.iso imgbased-0.6-0.201605260814git95d31d4.el7.centos.noarch Steps: 1. Install ovirt-node-ng-installer-master-2016053104.iso on machine 2. Check glusterfs packages # rpm -qa|grep glusterfs Results: glusterfs-libs-3.7.11-1.el7.x86_64 glusterfs-geo-replication-3.7.11-1.el7.x86_64 glusterfs-3.7.11-1.el7.x86_64 glusterfs-client-xlators-3.7.11-1.el7.x86_64 glusterfs-cli-3.7.11-1.el7.x86_64 glusterfs-fuse-3.7.11-1.el7.x86_64 glusterfs-server-3.7.11-1.el7.x86_64 glusterfs-api-3.7.11-1.el7.x86_64 glusterfs-rdma-3.7.11-1.el7.x86_64 According to comment 6, the package "glusterfs-devel" is missing. Does the above list contain enough glusterfs client packages for the ovirt-node-ng?
We do not install glusterfs-devel. Only once we see that it really is needed.
According to comment 10 and comment 11, the bug is verified. I will change the status to VERIFIED.
oVirt 4.0.0 has been released, closing current release.