Bug 1142781
| Summary: | When scanning a non-block disk, the error message doesn't note the specific disk name | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Gilad Lazarovich <glazarov> | ||||
| Component: | ovirt-engine | Assignee: | Idan Shaby <ishaby> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Kevin Alon Goldblatt <kgoldbla> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3.5.0 | CC: | acanan, amureini, gklein, lsurette, rbalakri, Rhev-m-bugs, tnisan, yeylon, ykaul | ||||
| Target Milestone: | ovirt-3.6.0-rc | ||||||
| Target Release: | 3.6.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-03-10 10:35:12 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: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
ovirt-3.6.0-3 release Verified using Version:
-----------------------------------
vdsm-4.17.0-1054.git562e711.el7.noarchrpm -qa
ovirt-engine-3.6.0-0.0.master.20150627185750.git6f063c1.el6.noarch
Verified using the following scenario:
-----------------------------------
Steps to Reproduce:
1. Create a VM with a disk based on a LUN from an iSCSI Storage domain, then remove the VM leaving the disk behind
2. Create a VM with an NFS based disk
3. Under the Disks tab, click on both disks and then right click and choose Scan Alignment
The Correct error is displayed as follows:
Error while executing action:
Action 1:
Cannot scan alignment Virtual Machine Disk vm7_Disk1. Alignment scan is only supported for disks located on block storage domains.
Action 2:
Cannot scan alignment Virtual Machine Disk. The following disk(s) are not attached to any VM: Direct23.
Moving to VERIFIED!
RHEV 3.6.0 has been released, setting status to CLOSED CURRENTRELEASE RHEV 3.6.0 has been released, setting status to CLOSED CURRENTRELEASE RHEV 3.6.0 has been released, setting status to CLOSED CURRENTRELEASE RHEV 3.6.0 has been released, setting status to CLOSED CURRENTRELEASE |
Created attachment 938445 [details] Alignment check error with NFS based disk not noting disk name Description of problem: When scanning a non-block disk, the error message doesn't note the specific disk name Version-Release number of selected component (if applicable): 3.5 vt3.1 How reproducible: 100% Steps to Reproduce: 1. Create a VM with a disk based on a LUN from an iSCSI Storage domain, then remove the VM leaving the disk behind 2. Create a VM with an NFS based disk 3. Under the Disks tab, click on both disks and then right click and choose Scan Alignment Actual results: An error dialog comes up which lists the 2 issues: 1. The LUN based disk isn't attached to any VM, disk name is listed 2. The NFS disk cannot be scanned as alignment only works with block storage domains, the disk name isn't mentioned Expected results: The NFS based disk name should be listed for consistency and usability.