| Summary: | [vdsm][storage]refreshStoragePool returns ok though got an exception in the middle | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Moran Goldboim <mgoldboi> | ||||
| Component: | vdsm | Assignee: | Dan Kenigsberg <danken> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | yeylon <yeylon> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.1 | CC: | abaron, bazulay, iheim, smizrahi, srevivo, syeghiay, ykaul | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-04-26 11:20:27 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
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. |
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: