| Summary: | vmHotplugDisk failed with "VolumeError: Bad volume specification" | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Nir Soffer <nsoffer> | ||||
| Component: | vdsm | Assignee: | Nir Soffer <nsoffer> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Aharon Canan <acanan> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.3.0 | CC: | amureini, bazulay, ebenahar, eedri, iheim, kjachim, lpeer, nsoffer, obasan, sbonazzo, scohen, sgrinber, yeylon, ykaul, zdover | ||||
| Target Milestone: | --- | Keywords: | ZStream | ||||
| Target Release: | 3.4.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | storage | ||||||
| Fixed In Version: | ovirt-3.4.0-beta2 | Doc Type: | Bug Fix | ||||
| Doc Text: |
Previously, attaching an iSCSI disk to a running virtual machine failed with the following error: "VolumeError: Bad volume specification". The logs reported that the LUN existed on the storage server adn the storage server was connected.
vmHotplugDisk now adds a hot-plugged iSCSI disk successfully.
|
Story Points: | --- | ||||
| Clone Of: | 923773 | ||||||
| : | 1066413 (view as bug list) | Environment: | |||||
| Last Closed: | 2014-06-09 13:27:02 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Bug Depends On: | 923773 | ||||||
| Bug Blocks: | 1066413, 1078909, 1142926 | ||||||
| Attachments: |
|
||||||
|
Comment 9
Eyal Edri
2014-02-10 10:15:58 UTC
Confirm it worked in ovirt-engine-3.4.0-0.7.beta2 (vdsm version is vdsm-4.14.1-3.) Attached vdsm log where vmHotplugDisk successes. Created attachment 864563 [details]
verifying vdsm log.
vmHotplugDisk adds hot plug disk successfully
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-2014-0504.html |