Description of problem: Customer has an issue where symlinks for one of the glusterSD is not getting creates and VMs with disks on that domain report "No such file or directory" error and fail to start. Setup has two glusterSDs one of which is master and symlink for that is getting created properly , but for other glusterSD which should be scanned during fileSD.scanDomains() is not getting detected for some reason. Version-Release number of selected component (if applicable): vdsm-4.14.7-3.el6ev How reproducible: Always on customer setup Steps to Reproduce: 1. Create two glusterSDs 2. Connect host to pool 3. Symlink for one glusterSD is never created Actual results: Symlink only for one glusterSD ( which is master ) Expected results: All glusterSD should have symlinks Additional info: ~~~ //Successfully mounted the glusterSD with UUID '24b11ab1-4438-47be-8221-043efb7e7ecc' Thread-13::DEBUG::2014-09-01 03:03:45,818::mount::202::Storage.Misc.excCmd::(_runcmd) '/usr/bin/sudo -n /bin/mount -t glusterfs rhstorage-01.storage.stage.eng.rdu2.redhat.com:vms /rhev/data-center/mnt/glusterSD/rhstorage-01.storage.stage.eng.rdu2.redhat.com:vms' (cwd None) Thread-13::DEBUG::2014-09-01 03:03:46,205::hsm::2341::Storage.HSM::(__prefetchDomains) glusterDomPath: glusterSD/* Thread-13::DEBUG::2014-09-01 03:03:46,541::hsm::2353::Storage.HSM::(__prefetchDomains) Found SD uuids: ('24b11ab1-4438-47be-8221-043efb7e7ecc',) Thread-13::DEBUG::2014-09-01 03:03:46,542::hsm::2409::Storage.HSM::(connectStorageServer) knownSDs: {9b431b4b-e161-4471-aa58-604a3d362d39: storage.nfsSD.findDomain, c447ec05-4315-4a2a-9c61-65d5674e8b39: storage.nfsSD.findDomain, 24b11ab1-4438-47be-8221-043efb7e7ecc: storage.glusterSD.findDomain} . . //Skipped glusterSD with UUID '24b11ab1-4438-47be-8221-043efb7e7ecc' during symlink Thread-13::DEBUG::2014-09-01 03:03:49,122::lvm::415::OperationMutex::(_reloadvgs) Operation 'lvm reload operation' released the operation mutex Thread-13::INFO::2014-09-01 03:03:49,185::sp::1113::Storage.StoragePool::(_linkStorageDomain) Linking /rhev/data-center/mnt/rhstorage-01.infra.stage.eng.rdu2.redhat.com:_isos/9b431b4b-e161-4471-aa58-604a3d362d39 to /rhev/data-center/95371f2b-8281-4715-807f-2feb69f88cb5/9b431b4b-e161-4471-aa58-604a3d362d39 Thread-13::INFO::2014-09-01 03:03:49,196::sp::1113::Storage.StoragePool::(_linkStorageDomain) Linking /rhev/data-center/mnt/rhstorage-01.infra.stage.eng.rdu2.redhat.com:_exports/c447ec05-4315-4a2a-9c61-65d5674e8b39 to /rhev/data-center/95371f2b-8281-4715-807f-2feb69f88cb5/c447ec05-4315-4a2a-9c61-65d5674e8b39 Thread-13::INFO::2014-09-01 03:03:49,209::sp::1113::Storage.StoragePool::(_linkStorageDomain) Linking /rhev/data-center/mnt/glusterSD/rhstorage-01.storage.stage.eng.rdu2.redhat.com:databases/44087a47-5d1e-4669-be08-922d43aa3281 to /rhev/data-center/95371f2b-8281-4715-807f-2feb69f88cb5/44087a47-5d1e-4669-be08-922d43aa3281 Thread-13::INFO::2014-09-01 03:03:49,223::sp::1113::Storage.StoragePool::(_linkStorageDomain) Linking /rhev/data-center/mnt/glusterSD/rhstorage-01.storage.stage.eng.rdu2.redhat.com:databases/44087a47-5d1e-4669-be08-922d43aa3281 to /rhev/data-center/95371f2b-8281-4715-807f-2feb69f88cb5/mastersd ~~~
This seems to be a duplicate of bug 1116585 The fix was not ported to 3.4 yet. http://gerrit.ovirt.org/#/c/31158 Aval, can verify that this patch solve your issue?
Assuming Aval can confirm this patch really fixes the issue, let's get it backported to 3.4.z. Thanks!
Hi Nir, The patch is good to be backported. Regards, Aval
(In reply to Aval from comment #5) > The patch is good to be backported. Aval, can you be more specific, how did you test this patch?
this bug wasn't included in the rhev 3.4.3 tracker bug and missed the build date of the build, hence moving to 3.4.4
*** Bug 1146401 has been marked as a duplicate of this bug. ***
Symlink for a Gluster domain are created for activating host and activating the domain. Tested that disks can be created after those actions. Thread-18::INFO::2014-11-18 09:21:59,410::sp::1113::Storage.StoragePool::(_linkStorageDomain) Linking /rhev/data-center/mnt/glusterSD/10.35.160.202:_elad/178b36ca-b2a4-4654-be51-cbe58f912e7d to /rhev/data-center/0 0000002-0002-0002-0002-000000000316/178b36ca-b2a4-4654-be51-cbe58f912e7d Veirified using rhev 3.4.4 av13.1
Hi Allon, If this bug requires doc text for errata release, please provide draft text in the doc text field in the following format: Cause: Consequence: Fix: Result: The documentation team will review, edit, and approve the text. If this bug does not require doc text, please set the 'requires_doc_text' flag to -. Many thanks, Julie
If flagged it with requires-doctext-, there's nothing intelligent to say about it. Thanks!
(In reply to Allon Mureinik from comment #13) > If flagged it with requires-doctext-, there's nothing intelligent to say > about it. > Thanks! Many thanks, Julie
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/RHBA-2014-1946.html