Created attachment 958639 [details] /var/log from both hosts +++ This bug was initially created as a clone of Bug #1165215 +++ Description of problem: I tried to add a new RHEL7 host to a DC where I already had a host with RHEL6.6 OS installed. In the DC I had a gluster domain which was created using the RHEL6.6 host. The host wasn't able to connect to the storage pool due to a mount failure to the gluster domain. Version-Release number of selected component (if applicable): rhev 3.4.4 av13.1 On the RHEL7 host: vdsm-4.14.18-2.el7ev.x86_64 libvirt-1.1.1-29.el7_0.3.x86_64 samba-vfs-glusterfs-4.1.1-37.el7_0.x86_64 glusterfs-debuginfo-3.4.0.65rhs-1.el7_0.x86_64 glusterfs-libs-3.4.0.65rhs-1.el7_0.x86_64 glusterfs-3.4.0.65rhs-1.el7_0.x86_64 glusterfs-fuse-3.4.0.65rhs-1.el7_0.x86_64 glusterfs-api-devel-3.4.0.65rhs-1.el7_0.x86_64 glusterfs-devel-3.4.0.65rhs-1.el7_0.x86_64 glusterfs-api-3.4.0.65rhs-1.el7_0.x86_64 glusterfs-rdma-3.4.0.65rhs-1.el7_0.x86_64 qemu-kvm-rhev-1.5.3-60.el7_0.10.x86_64 sanlock-3.1.0-2.el7.x86_64 On the RHEL6.6 host: vdsm-4.14.18-2.el6ev.x86_64 libvirt-0.10.2-46.el6_6.1.x86_64 sanlock-2.8-1.el6.x86_64 qemu-kvm-rhev-0.12.1.2-2.448.el6.x86_64 glusterfs-api-devel-3.6.0.28-2.el6.x86_64 glusterfs-cli-3.6.0.28-2.el6.x86_64 glusterfs-libs-3.6.0.28-2.el6.x86_64 glusterfs-api-3.6.0.28-2.el6.x86_64 glusterfs-devel-3.6.0.28-2.el6.x86_64 samba-glusterfs-3.6.23-12.el6.x86_64 glusterfs-rdma-3.6.0.28-2.el6.x86_64 glusterfs-debuginfo-3.4.0.57rhs-1.el6_5.x86_64 glusterfs-3.6.0.28-2.el6.x86_64 glusterfs-fuse-3.6.0.28-2.el6.x86_64 How reproducible: Always Steps to Reproduce: Have 2 hosts: one with RHEL6.6 and one with RHEL7. Install all gluster packages mentioned above 1. Create a gluster domain using a RHEL6.6 host Thread-13::DEBUG::2014-11-18 09:25:58,924::mount::202::Storage.Misc.excCmd::(_runcmd) '/usr/bin/sudo -n /bin/mount -t glusterfs 10.35.160.202:/elad /rhev/data-center/mnt/glusterSD/10.35.160.202:_elad' (cwd None) 2. Add a new cluster to the DC and add a RHEL7 host to it 3. Actual results: Host is unable to connect to the storage pool: vdsm.log: Thread-14::INFO::2014-11-18 15:02:17,746::logUtils::44::dispatcher::(wrapper) Run and protect: connectStorageServer(domType=7, spUUID='00000002-0002-0002-0002-000000000316', conList=[{'port': '', 'connection': '10 .35.160.202:/elad', 'iqn': '', 'user': '', 'tpgt': '1', 'vfs_type': 'glusterfs', 'password': '******', 'id': 'f26f92dd-6cf5-4353-b516-1c0b31e44605'}], options=None) Thread-14::DEBUG::2014-11-18 15:02:17,772::mount::202::Storage.Misc.excCmd::(_runcmd) '/usr/bin/sudo -n /usr/bin/mount -t glusterfs 10.35.160.202:/elad /rhev/data-center/mnt/glusterSD/10.35.160.202:_elad' (cwd Non e) Thread-14::ERROR::2014-11-18 15:02:17,811::storageServer::209::StorageServer.MountConnection::(connect) Mount failed: (32, ";mount: unknown filesystem type 'glusterfs'\n") Traceback (most recent call last): File "/usr/share/vdsm/storage/storageServer.py", line 207, in connect self._mount.mount(self.options, self._vfsType) File "/usr/share/vdsm/storage/mount.py", line 198, in mount return self._runcmd(cmd, timeout) File "/usr/share/vdsm/storage/mount.py", line 214, in _runcmd raise MountError(rc, ";".join((out, err))) MountError: (32, ";mount: unknown filesystem type 'glusterfs'\n") Thread-14::ERROR::2014-11-18 15:02:17,812::hsm::2389::Storage.HSM::(connectStorageServer) Could not connect to storageServer Traceback (most recent call last): File "/usr/share/vdsm/storage/hsm.py", line 2386, in connectStorageServer conObj.connect() File "/usr/share/vdsm/storage/storageServer.py", line 215, in connect raise e MountError: (32, ";mount: unknown filesystem type 'glusterfs'\n") engine.log: 2014-11-18 16:15:02,499 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-8) [659b4d39] Correlation ID: null, Call Stack: null, Custom Event ID: -1, Messag e: The error message for connection 10.35.160.202:/elad returned by VDSM was: Problem while trying to mount target 2014-11-18 16:15:02,500 ERROR [org.ovirt.engine.core.bll.storage.GLUSTERFSStorageHelper] (DefaultQuartzScheduler_Worker-8) [659b4d39] The connection with details 10.35.160.202:/elad failed because of error code 47 7 and error message is: problem while trying to mount target The problem occurs only on RHEL7 hosts. Mounting the gluster voume manually from the host succeeds: Expected results: Connecting a RHEL7 host to a gluster domain should succeed if it was created by a RHEL6 host Additional info: /var/log from both hosts engine.log
We need to follow proper cloning process. I'm closing this one and leaving bug 1165215 for the investigation. If it indeed requires backporting, that one should be cloned properly. *** This bug has been marked as a duplicate of bug 1165215 ***