Bug 1416459
| Summary: | Restore HE backup will fail if the HE SD has disks of non-HE VM's | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Artyom <alukiano> | ||||
| Component: | Backup-Restore.Engine | Assignee: | Simone Tiraboschi <stirabos> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Artyom <alukiano> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.1.0 | CC: | bugs, nsednev, ylavi | ||||
| Target Milestone: | ovirt-4.1.1 | Keywords: | Triaged, ZStream | ||||
| Target Release: | 4.1.1.3 | Flags: | rule-engine:
ovirt-4.1+
ylavi: exception+ nsednev: testing_plan_complete? |
||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Restoring HE backup was failing if the HE storage domain contained disks associated to VMs different from the hested-engine one. Fixing it.
|
Story Points: | --- | ||||
| Clone Of: | |||||||
| : | 1425893 (view as bug list) | Environment: | |||||
| Last Closed: | 2017-04-21 09:44:01 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Integration | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1235200, 1425893 | ||||||
| Attachments: |
|
||||||
Let's remove the other disks from the SD during restore and prompt that we have done so for this use case. This because its not the same physical device. Verified on rhevm-4.1.1.6-0.1.el7.noarch |
Created attachment 1244274 [details] restore log Description of problem: Restore HE backup will fail if the HE SD has disks of non-HE VM's Version-Release number of selected component (if applicable): rhevm-4.1.0.2-0.2.el7.noarch How reproducible: Always Steps to Reproduce: 1. Deploy HE environment 2. Add the storage domain to the engine(to start auto-import process) 3. Wait until the engine will have HE VM 4. Add non-HE VM with the disk on the HE SD 5. Set global maintenance 6. Backup the engine: # engine-backup --mode=backup --file=engine.backup --log=engine-backup.log 7. Copy the backup file from the HE VM to the host 8. Clean host from HE deploy(reprovisioning) 9. Run the HE deployment again 10. Answer No on the question "Automatically execute engine-setup on the engine appliance on first boot (Yes, No)[Yes]? " 11. Enter to the HE VM and copy the backup file from the host to the HE VM 12. Run restore command: # engine-backup --mode=restore --scope=all --file=engine.backup --log=engine-restore.log --he-remove-storage-vm --he-remove-hosts --restore-permissions --provision-all-databases Actual results: Restore operation failed with the error: SELECT DeleteHostedEngineStorageVM(); ERROR: The hosted-engine storage domain contains more than one vm. FATAL: Cannot execute sql command: --command=SELECT DeleteHostedEngineStorageVM(); 2017-01-25 09:25:05 9460: FATAL: Failed cleaning hosted-engine Expected results: Restore operation succeeds. I do not sure what the correct way to fix this problem(maybe we just need to prevent adding non-HE VM disks on the HE SD) Additional info: