Bug 1569479
Summary: | Snapshot with memory when not all disks are included | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Milan Zamazal <mzamazal> |
Component: | Backend.Core | Assignee: | Nobody <nobody> |
Status: | CLOSED WONTFIX | QA Contact: | meital avital <mavital> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.3.0 | CC: | bugs, michal.skrivanek, rbarry |
Target Milestone: | --- | Flags: | rule-engine:
ovirt-4.3+
|
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: | 2018-11-21 00:19:10 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Milan Zamazal
2018-04-19 11:18:45 UTC
Severity? it can be avoided by following the warning and including all disks. When it is configured like that you can get easily to a state when the snapshot cannot start or starts in a wrong way - potentially corrupting the resumed state (say, in-flight I/O to a disk which is not included in the restore, unexpected HW configuration change) But since this is a existing behavior for a long time it's not that common. Closing due to capacity. It's an unusual workflow which hasn't generated an additional bug report in years (despite being an actual bug) |