Bug 891053
| Summary: | 3.1.z Error deleting VM disk | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Ayal Baron <abaron> |
| Component: | vdsm | Assignee: | Yeela Kaplan <ykaplan> |
| Status: | CLOSED ERRATA | QA Contact: | Haim <hateya> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.3 | CC: | abaron, bazulay, dron, dyasny, ewarszaw, hateya, iheim, ilvovsky, ipilcher, lpeer, mlipchuk, oourfali, Rhev-m-bugs, sgordon, sgrinber, tjelinek, yeylon, ykaplan, ykaul |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | 6.3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | storage | ||
| Fixed In Version: | vdsm-4.9.6-44.3 | Doc Type: | Bug Fix |
| Doc Text: |
A typographical mistake in the rmDCImgDir function of blockSD.py meant that when an OSError exception was encountered it was not logged correctly. The mistake has been corrected and the function now logs errors correctly.
|
Story Points: | --- |
| Clone Of: | 885489 | Environment: | |
| Last Closed: | 2013-01-15 14:52:56 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 885489, 891054 | ||
| Bug Blocks: | 891052 | ||
|
Comment 1
Ayal Baron
2013-01-01 12:50:57 UTC
verified on vdsm4.9.6-44.3 installed on QE production environment.
managed to delete a VM (disk) where the image was missing, instead of exception I got valid error message of:
Thread-491::ERROR::2013-01-06 14:09:30,662::dispatcher::66::Storage.Dispatcher.Protect::(run) {'status': {'message': "Image does not exist in domain: 'image=0def7577-eec8-48e0-
8100-1e492752fc47, domain=d5d0dfe6-c2b9-429e-96c2-c1cd247ac828'", 'code': 268}}
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. http://rhn.redhat.com/errata/RHBA-2013-0159.html |