Bug 1502619
| Summary: | Memory disks (memory and metadata) status is unassigned after VM registered from data storage domain | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Eyal Shenitzky <eshenitz> | ||||
| Component: | BLL.Storage | Assignee: | Eyal Shenitzky <eshenitz> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Raz Tamir <ratamir> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.2.0 | CC: | amureini, bugs, ratamir, tnisan | ||||
| Target Milestone: | ovirt-4.2.0 | Flags: | rule-engine:
ovirt-4.2+
|
||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-12-20 11:39:56 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: |
|
||||||
*** Bug 1503212 has been marked as a duplicate of this bug. *** Verified on ovirt-engine-4.2.0-0.0.master.20171027213842.gitded437c.el7.centos Registered VM's memory disks are with status ok This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |
Created attachment 1339163 [details] engine and vdsm logs Description of problem: When having un-registered VM with disk and live snapshot with memory. After registering the VM to the environment the memory disks (memory and metadata) status is 'unassigned' on the UI and '0' on the DB. Also, disk the disks alias doesn't appear under disks tab. Version-Release number of selected component (if applicable): 4.2.0_master from commit - 4c7f086a319d5c523e4baffc3a1042afd154b0d0 How reproducible: 100% Steps to Reproduce: 1. Create a VM with disk 2. Run the VM 3. Create live snapshot with memory 4. Deactivate and detach the storage domain that contains the VM disk 5. Attach the storage domain from step 5 6. register the VM from step 1 Actual results: Memory disks status is 'unassigned', disk alias does not under disks tab Expected results: Memory disks status should be 'OK', disk alias should appear under disks tab Additional info: Engine and VDSM logs attached