Bug 1293135
| Summary: | starting on 3.6 a vm snapshot taken with 3.5 fails | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Yedidyah Bar David <didi> |
| Component: | General | Assignee: | Arik <ahadas> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.6.1 | CC: | acanan, bugs, didi, gklein, kgoldbla, michal.skrivanek, nsednev |
| Target Milestone: | ovirt-3.6.3 | Flags: | michal.skrivanek:
ovirt-3.6.z?
rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack? |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | virt | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-01-07 13:50:46 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1285700 | ||
|
Description
Yedidyah Bar David
2015-12-20 14:52:02 UTC
vdsm was not upgraded, vdsm-4.16.27-1 Aharon, did your team reproduce this? We didn't test upgrade, Maybe Nikolai will be able to answer this question better. in general this needs to be blocked when everythin is upgraded to 3.6, see bug 1292398 but in this case of 3.5 cluster this should work just fine engine.log is missing teh VM creation. Please attach correct log (In reply to Michal Skrivanek from comment #6) > engine.log is missing teh VM creation. Please attach correct log Sorry, attaching. 1)I've tried to perform the live snapshot with memory for the 3.6 VM running on our RHEV3 and failed, RHEV3 is running on Red Hat Enterprise Virtualization Manager Version: 3.5.6.2-0.1.el6ev. 2)Personally I did not tested this scenario, need to ask Kevin as snapshots are part of the storage sanity, we'll retest if not covered and provide more info later in this bug. Now tried restoring the snapshot without memory, and it still fails with same error. Attaching engine log. Guessing based on the error message, I tried editing the VM and change console type from spice to vnc. Tried both with and without restoring memory, both worked. Attaching log again. Did another test - restored with memory, edited console from spice to vnc, then edited again from vnc to spice, started - worked. Attaching logs. (In reply to Nikolai Sednev from comment #9) > 1)I've tried to perform the live snapshot with memory for the 3.6 VM running > on our RHEV3 and failed, RHEV3 is running on Red Hat Enterprise > Virtualization Manager Version: 3.5.6.2-0.1.el6ev. > 2)Personally I did not tested this scenario, need to ask Kevin as snapshots > are part of the storage sanity, we'll retest if not covered and provide more > info later in this bug. As discussed in my mail, I did not check this scenario. It is not part of the sanity test plan that we do. I can add it and test it in the next upgrade. The end result of this bug is different than this of bz 1293299 - here the VM is not created while in bz 1293299 the VM is created but the user cannot connect to it with a console. The reason for that is probably the VDSM version - VDSM 4.16.27 fails to run VM when not specifying 'display' and newer VDSM versions manage to run it. The addition of default graphics device when reading OVF is supposed to fix the problem of not setting 'display' when restoring a snapshot from a version lower than 3.6. *** This bug has been marked as a duplicate of bug 1293299 *** |