Bug 1425890
Summary: | [downstream clone - 4.0.7] Restore HE backup will fail if the HE host has running non-HE VM's | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ |
Component: | ovirt-engine | Assignee: | Simone Tiraboschi <stirabos> |
Status: | CLOSED ERRATA | QA Contact: | Artyom <alukiano> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | alukiano, bugs, gklein, lsurette, mavital, nsednev, rbalakri, Rhev-m-bugs, srevivo, stirabos, trichard, ykaul, ylavi |
Target Milestone: | ovirt-4.0.7 | Keywords: | Triaged, ZStream |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | integration | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously, restoring a self-hosted engine backup failed if the self-hosted engine host had running non-self-hosted engine VMs. This has now been fixed.
|
Story Points: | --- |
Clone Of: | 1416466 | Environment: | |
Last Closed: | 2017-03-16 15:34:16 UTC | Type: | --- |
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: | 1416466 | ||
Bug Blocks: | 1416111 |
Description
rhev-integ
2017-02-22 17:05:01 UTC
Verified on: rhevm-4.0.7.3-0.1.el7ev.noarch # rpm -qa | grep hosted ovirt-hosted-engine-setup-2.0.4.3-2.el7ev.noarch ovirt-hosted-engine-ha-2.0.7-2.el7ev.noarch 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. Create additional VM and start it on the HE host 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-dwh-db --provision-db 13. Run engine setup: # engine-setup --offline 14. Finish HE deployment process Engine UP and have HE SD and HE VM in the active state 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://rhn.redhat.com/errata/RHBA-2017-0542.html |