Description of problem: ======================= seems to be a case of build to build regression. I am observing errors while deploying gluster through colonizer. attached is the screenshot of error Version-Release number of selected component (if applicable): ==================== colonizer-1.0.4-1 see screenshot for all package versions How reproducible: ----------------- always Steps to Reproduce: 1.trigger a nas deployment 2.while the deployment proceeds , we will see attached errors
Created attachment 1402959 [details] errors
Created attachment 1402960 [details] version
This is a known problem that was already resolved upstream and included in the latest downstream RPMs. Upstream merge commit: https://github.com/gluster/gluster-zeroconf/commit/b14763ebc6302cdcc0b87c5f5695bab2f0abd1b9 Latest upstream release: https://github.com/gluster/gluster-zeroconf/releases/tag/v0.1.3
I spoke too soon. This is a different traceback and seems to be related to Ramky's upstream commit https://github.com/gluster/gluster-zeroconf/commit/589344edddf8bf60b8d9c59f0b54c2b20d540870
on_qa validation: I reran media+nfs-ganesha deployment, where i had previously seen the errors. I don't see the trackback errors anymore. Hence moving to verified [root@g1-1 ~]# gluster-discovery probe discovered host: 172.18.178.85 discovered host: 172.18.178.91 discovered host: 172.18.178.90 discovered host: 172.18.178.65 discovered host: 172.18.178.93 discovered host: 172.18.178.86 connected peer: g1-2 connected peer: g1-3 connected peer: g1-4 connected peer: g1-5 connected peer: g1-6 glusterfs-ganesha-3.8.4-52.el7rhgs.x86_64 libvirt-daemon-driver-storage-gluster-3.2.0-14.el7_4.5.x86_64 avahi-0.6.31-17.el7.x86_64 glusterfs-cli-3.8.4-52.el7rhgs.x86_64 glusterfs-api-3.8.4-52.el7rhgs.x86_64 glusterfs-rdma-3.8.4-52.el7rhgs.x86_64 nfs-ganesha-gluster-2.4.4-17.el7rhgs.x86_64 gluster-zeroconf-avahi-0.1.3-2.el7rhgs.noarch glusterfs-3.8.4-52.el7rhgs.x86_64 avahi-libs-0.6.31-17.el7.x86_64 glusterfs-libs-3.8.4-52.el7rhgs.x86_64 gluster-nagios-addons-0.2.10-2.el7rhgs.x86_64 glusterfs-server-3.8.4-52.el7rhgs.x86_64 python2-zeroconf-0.18.0-3.el7rhgs.noarch gluster-colonizer-1.0.4-2.el7rhgs.noarch glusterfs-geo-replication-3.8.4-52.el7rhgs.x86_64 vdsm-gluster-4.17.33-1.2.el7rhgs.noarch python-gluster-3.8.4-52.el7rhgs.noarch samba-vfs-glusterfs-4.6.3-9.el7rhgs.x86_64 glusterfs-client-xlators-3.8.4-52.el7rhgs.x86_64 gluster-nagios-common-0.2.4-1.el7rhgs.noarch glusterfs-fuse-3.8.4-52.el7rhgs.x86_64 python-gluster-zeroconf-0.1.3-2.el7rhgs.noarch [root@g1-1 ~]# ls /rhs_one-1.0.4-2_rpms avahi-0.6.31-17.el7.x86_64.rpm gluster-zeroconf-avahi-0.1.3-2.el7rhgs.noarch.rpm python-xmltodict-0.10.2-3.el7rhgs.noarch.rpm fio-2.2.10-2.el7ost.x86_64.rpm python2-zeroconf-0.18.0-3.el7rhgs.noarch.rpm gluster-colonizer-1.0.4-2.el7rhgs.noarch.rpm python-gluster-zeroconf-0.1.3-2.el7rhgs.noarch.rpm (this was because of missing out "import subprocess" in the file which was throwing these errors
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-2018:0477