Bug 1064532
| Summary: | [hosted-engine] lack of facilities for VM reinstall | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-hosted-engine-setup | Reporter: | Antoni Segura Puimedon <asegurap> |
| Component: | General | Assignee: | Sandro Bonazzola <sbonazzo> |
| Status: | CLOSED WONTFIX | QA Contact: | Leonid Natapov <lnatapov> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | --- | CC: | asegurap, bazulay, bugs, ecohen, ehildesh, gklein, lsurette, oourfali, rbalakri, sbonazzo, yeylon, ylavi |
| Target Milestone: | --- | Keywords: | UserExperience |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | integration | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-09-29 13:53:08 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
For anybody else that would get stuck, the workaround would be:
On the physical host
virsh -r dumpxml <hosted engine domain number> > hosted.xml
edit the xml so that:
- Remove "<on_reboot>destroy</on_reboot>"
- Move "<boot order='1'/>" to the <interface> element.
virsh create hosted.xml
the ux stakeholders would need to be educated about hosted-engine a little bit more before they can assist. please let us know if you have time/capacity to do such education in the very near future (assuming this needs to meet the 3.5 timeframe), if not - I assume that you can go with any of the suggestions in Comment #0. (In reply to Einav Cohen from comment #2) > the ux stakeholders would need to be educated about hosted-engine a little > bit more before they can assist. > please let us know if you have time/capacity to do such education in the > very near future (assuming this needs to meet the 3.5 timeframe), if not - I > assume that you can go with any of the suggestions in Comment #0. We're too late in the 3.5.0 release process for introducing such change in the UX of the hosted engine setup. Postponing to 3.6.0. About the education for UX, I guess you can start with * https://www.youtube.com/watch?v=bm3jyYAcOzw * http://www.ovirt.org/images/8/88/Hosted_Engine_Deep_Dive.pdf * https://sas.elluminate.com/p.jnlp?psid=2013-09-09.0551.M.BD9E2DF1BD85D7D7863CEF5E0801A4.vcr&sid=819 the UX is a bit changed since above presentations but you can easily figure out the rest by just trying to install it. Let me know if you need any more info from my side. Adding Eldan as needinfo so that he can take a look at the information provided and start thinking about an update from a UX point of view. Thanks, Liz I sat with Eldan. As far as I understand, the requirement here is to provide options to reinstall the environment using the hosted engine cli, so not really GUI related. The term UserExperience was used here, to emphasize that the user experience in the hosted engine setup lacks some features... not sure if it should have been used here. Einav? Should the UserExperience keyword be used also for non-GUI utilities? (In reply to Oved Ourfali from comment #5) > I sat with Eldan. > As far as I understand, the requirement here is to provide options to > reinstall the environment using the hosted engine cli, so not really GUI > related. > > The term UserExperience was used here, to emphasize that the user experience > in the hosted engine setup lacks some features... not sure if it should have > been used here. Einav? Should the UserExperience keyword be used also for > non-GUI utilities? Hi Oved; it can, however need to understand that the UXD stakeholders (including myself) are far-less familiar with the non-GUI tools, so some education for us will be needed here in order for us to help out. If the feature is too small to justify such an education, you can just go with whatever seems right to you. This is an automated message. This Bugzilla report has been opened on a version which is not maintained anymore. Please check if this bug is still relevant in oVirt 3.5.4. If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution) If it's an RFE please update the version to 4.0 if still relevant. This is an automated message. oVirt 3.6.0 RC1 has been released. This bug has no target release and still have target milestone set to 3.6.0-rc. Please review this bug and set target milestone and release to one of the next releases. In oVirt 3.6 we provide oVirt Appliance and default flow is to use it for the VM deployment. Supported procedure for reinstalling the OS is to restart from scratch. |
Description of problem: During the hosted-engine --deploy process a VM is created and the setup program asks for what is the boot source for installation. Once the installation of the OS is done it advances to the step of installing the engine. At this point, if you realize, like it happened to me, that there is a problem with the OS installation and you have to install again. You don't have any easy way to do so because hosted-engine --vm-start doesn't have options. A useful option would be --boot {pxe|cdrom|hd} and another would --no-reboot-destroy. Additionally since there is --vm-start-paused, there should really be --vm-start-resume Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-1.1.0-0.5.beta2.fc19.noarch How reproducible: 100% Steps to Reproduce: 1. hosted-engine --deploy 2. Try to reinstall the OS after the step of installing the OS Actual results: Can't do so as you can't boot to installation medium. Expected results: hosted-engine cli provides options to help with scenarios of OS upgrade and reinstall. Additional info: