Bug 1658976
| Summary: | [Backup restore API] restore VM (created from template with thin copy) from OVF data fails - ImportVmFromConfigurationCommand fails with Error during ValidateFailure.: java.lang.NullPointerException | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Avihai <aefrat> | ||||||||
| Component: | BLL.Storage | Assignee: | shani <sleviim> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Avihai <aefrat> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | high | ||||||||||
| Version: | 4.3.0 | CC: | bugs, frolland, mtessun, ratamir, sborella | ||||||||
| Target Milestone: | ovirt-4.3.1 | Keywords: | Automation | ||||||||
| Target Release: | --- | Flags: | rule-engine:
ovirt-4.2+
rule-engine: ovirt-4.3+ rule-engine: blocker+ |
||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | ovirt-engine-4.3.1.1 | Doc Type: | Bug Fix | ||||||||
| Doc Text: |
This bug fix sets the template ID properly to address a null pointer exception during the import of a thin-provisioned VM disk from an Open Virtualization Framework configuration file.
|
Story Points: | --- | ||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2019-03-01 10:17:47 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: |
|
||||||||||
|
Description
Avihai
2018-12-13 10:10:57 UTC
The cause for this issue is that the VM was created from a template with thin copy -> this issue does NOT occur using "clone" AKA deep copy. A simpler scenario which reproduced the issue: 1) Create VM1 from a template with thin copy 2) Create snapshot 3) Get VM1 OVF configuration data from the snapshot. 4) remove VM1 5) Restore VM1 from OVF info Even though this doesn't seem to be a regression, as this is the basic flow of backup restore api, re-targeting to 4.2.8 and proposing as a blocker for it. Created attachment 1515224 [details]
4.2.8-0.1 reproduction logs
Created attachment 1516932 [details]
new art log with latest reproduction REST request and response
The original test case dealt with a VM created from the template as a clone (independent of the template) till recently and changed to thin (dependent of the template) and then started failing. This is not a regression and thus not a blocker. Regarding the test case scenario of importing a thin VM from OVF data: When removing the thin provisioned VM, it removes the VM disks permanently instead of detaching them as they are dependent on the template disks. Verified on ovirt-engine Software Version:4.3.1.1-0.1.el7 This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |