Bug 1646992
| Summary: | [downstream clone - 4.2.8] Move Disk dialog keeps spinning - API method works | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | RHV bug bot <rhv-bugzilla-bot> |
| Component: | ovirt-engine | Assignee: | shani <sleviim> |
| Status: | CLOSED ERRATA | QA Contact: | Yosi Ben Shimon <ybenshim> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.2.5 | CC: | jcoscia, ratamir, Rhev-m-bugs, sborella, sleviim, tnisan |
| Target Milestone: | ovirt-4.2.8 | Keywords: | ZStream |
| Target Release: | --- | Flags: | lsvaty:
testing_plan_complete-
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ovirt-engine-4.2.8.1 | Doc Type: | Bug Fix |
| Doc Text: |
This fix addresses the attempt to move a disk with a damaged ancestor (e.g., the ancestor doesn't have an entry in the 'images' table), which leads to an NPE and an error. If the error persists, a possible workaround is to use the API to move the disk between storage domains. The fix documents the error in the Red Hat Virtualization Manager log.
|
Story Points: | --- |
| Clone Of: | 1635405 | Environment: | |
| Last Closed: | 2019-01-22 12:44:50 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Storage | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1635405 | ||
| Bug Blocks: | |||
|
Description
RHV bug bot
2018-11-06 13:25:59 UTC
Tested using : ovirt-engine-4.2.8-0.1.el7ev.noarch I didn't manage to reproduce it eighter. No errors found in logs (engine & VDSM) and browser developer console. Moving to VERIFIED. 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. https://access.redhat.com/errata/RHBA-2019:0121 sync2jira sync2jira |