Hide Forgot
Created attachment 484413 [details] vdsm log Description of problem: though refreshStoragePool fails on: Thread-220::ERROR::2011-03-10 08:59:30,627::sp::1059::Storage.StoragePool::(__rebuild) Unexpected error Traceback (most recent call last): File "/usr/share/vdsm/storage/sp.py", line 1054, in __rebuild self.refreshDomain(d, msdUUID, linkName) File "/usr/share/vdsm/storage/sp.py", line 994, in refreshDomain self.log.debug("check path %s " % (os.stat(linkName))) it returns: Thread-220::INFO::2011-03-10 08:59:45,384::dispatcher::100::Storage.Dispatcher.Protect::(run) Run and protect: refreshStoragePool, Return response: {'status': {'message': 'OK', 'code': 0 }} happened while attaching storage domains (large scale SD -35sds with 3 luns each) Version-Release number of selected component (if applicable): vdsm-4.9-53.el6.x86_64 How reproducible: happened once Steps to Reproduce: 1.attach several storage domains on a setup with ~30 sds 2. 3. Actual results: Expected results: Additional info:
Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
That's OK, it works as designed. refreshStoragePool makes sure that the caches is flushed. If something broke, repoStats\getStoragePoolInfo will tell you that. But the caches was invalidated. It just failed to update it.