<div dir="ltr"><span style="color:rgb(33,33,33);font-size:13px">Hi,</span><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px"><br class="gmail_msg"></div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px">I am finally planning to start our oVirt hosted engine upgrade. I am not sure how stable my hosted engine storage is ( it shows wrong status in web GUI ) So I arranged a new shared storage and plan to do a fresh install ( altough I noticed there is also an option to upgrade <span class="gmail_msg" style="color:inherit;font-size:inherit;background-color:transparent">"</span><span class="gmail_msg" style="color:inherit;font-size:inherit;background-color:transparent;font-family:menlo,monaco,consolas,"courier new",monospace;white-space:pre-wrap">hosted-engine --upgrade-appliance</span>" ).</div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px"><br class="gmail_msg"></div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px">After I installed the oVirt 4 hosted engine on a host node I want to move all my running VMs to the new environment. With VMs at first running on the current data storage domain. My storage domain is FC based.</div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px"><br class="gmail_msg"></div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px">My idea is to:</div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px"><br class="gmail_msg"></div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px">1. stop all VMs</div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px">2. detach Storage domain on old ovirt 3.6 environment ( and keep data ).</div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px">3. import and activate the storage domain on the new ovirt 4 environment.</div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px"><br class="gmail_msg"></div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px">To prevent any data loss or copy too much data I have the follwoing questions: </div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px"><br class="gmail_msg"></div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px">1. Is this storage domain import from 3.6 to 4.0 available?</div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px">2. I read I should import all VMs, this means I need to copy all data or is it just a matter of importing a config, so all VM data /image remains on the imported storage domain?<br class="gmail_msg"></div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px">3. When for some reason I want to roll back when I have imported the storage domain without having any VM imported, can I just detach and re-attach the storage domain to the previous 3.6 environment?</div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px"><br class="gmail_msg"></div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px">If there might be a better path to get my VMs to a clean oVirt 4.0 environment I am glad to hear.</div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px"><br class="gmail_msg"></div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px">Thanks in advance!</div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px">Kind regards,</div><div class="gmail_msg" style="color:rgb(33,33,33);font-size:13px">Paul</div><br><div class="gmail_quote"><div dir="ltr">Op do 30 jun. 2016 om 23:04 schreef Paul Groeneweg | Pazion <<a href="mailto:paul@pazion.nl">paul@pazion.nl</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="gmail_msg"><div class="gmail_quote gmail_msg"><div class="m_-8768991825503312413GmSign gmail_msg"><br class="gmail_msg"></div><div dir="ltr" class="gmail_msg">Op do 30 jun. 2016 om 21:55 schreef Yedidyah Bar David <<a href="mailto:didi@redhat.com" class="gmail_msg" target="_blank">didi@redhat.com</a>>:<br class="gmail_msg"></div></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, Jun 30, 2016 at 10:43 PM, Paul Groeneweg | Pazion<br class="gmail_msg">
<<a href="mailto:paul@pazion.nl" class="gmail_msg" target="_blank">paul@pazion.nl</a>> wrote:<br class="gmail_msg">
><br class="gmail_msg">
><br class="gmail_msg">
> Op do 30 jun. 2016 om 21:17 schreef Yedidyah Bar David <<a href="mailto:didi@redhat.com" class="gmail_msg" target="_blank">didi@redhat.com</a>>:<br class="gmail_msg">
>><br class="gmail_msg">
>> On Thu, Jun 30, 2016 at 9:46 PM, Paul Groeneweg | Pazion <<a href="mailto:paul@pazion.nl" class="gmail_msg" target="_blank">paul@pazion.nl</a>><br class="gmail_msg">
>> wrote:<br class="gmail_msg">
>> > Things are getting more clear to me, thanks!<br class="gmail_msg">
>> > And this whole upgrade is something I should prepare well and not try to<br class="gmail_msg">
>> > do<br class="gmail_msg">
>> > in a few hours at night :)<br class="gmail_msg">
>> ><br class="gmail_msg">
>> > Resuming, there are multiple solutions:<br class="gmail_msg">
>> ><br class="gmail_msg">
>> > 1. upgrade el6 to el7<br class="gmail_msg">
>> > no go => I need to upgrade postgresql and redhat warns about upgrading<br class="gmail_msg">
>> > 6.6<br class="gmail_msg">
>> > to 7 because of newer packages<br class="gmail_msg">
>> > 2. install a new HE on new Host new storage domain<br class="gmail_msg">
>> > a lot of work => I have to turn off VMs, import storage domain into new<br class="gmail_msg">
>> > setup and reinstall hosts.<br class="gmail_msg">
>> > 3. install a new HE on new Host existing storage domain<br class="gmail_msg">
>> > possibly not without issues => I have to manually update references to<br class="gmail_msg">
>> > the<br class="gmail_msg">
>> > hosted storage or better wait till there is an upgrade tool.<br class="gmail_msg">
>> > 4. (re)install HE in current VMS container.<br class="gmail_msg">
>> > => I can keep my Hosts and reference to the storage domain.<br class="gmail_msg">
>> ><br class="gmail_msg">
>> > So I guess my best bet is to go for option 4.<br class="gmail_msg">
>> ><br class="gmail_msg">
>> > The flow I am planning to follow would be:<br class="gmail_msg">
>> ><br class="gmail_msg">
>> > 1. Move to global maintenance ( keep VMs running )<br class="gmail_msg">
>> > 2. backup ( I have also a complete disk install of old hosted-engine )<br class="gmail_msg">
>> > 3. reboot with different conf, to boot from cd<br class="gmail_msg">
>> > 4. acces console and run install + import the backup in the engine vm<br class="gmail_msg">
>> > ? 5. run engine-setup to configure new install with engine restore data<br class="gmail_msg">
>> > 6. reboot hosted-engine<br class="gmail_msg">
>> > 7. Remove from global maintenance<br class="gmail_msg">
>> > 8. launch web gui and I should be able to manage all still running VMs<br class="gmail_msg">
>> > again.<br class="gmail_msg">
>> ><br class="gmail_msg">
>> > Would above be working or am I missing something and I doubt step 5. Is<br class="gmail_msg">
>> > this needed?<br class="gmail_msg">
>><br class="gmail_msg">
>> Yes.<br class="gmail_msg">
>><br class="gmail_msg">
>> In a normal backup/restore flow, it's less important, although officially<br class="gmail_msg">
>> it's mandatory. But in above flow, it's not just backup/restore, but also<br class="gmail_msg">
>> upgrade from 3.6 to 4.0.<br class="gmail_msg">
>><br class="gmail_msg">
>> In principle you can also do all of the above with 3.6, at least inside<br class="gmail_msg">
>> the engine, verify that all seems good, then upgrade to 4.0 later. See<br class="gmail_msg">
>> also:<br class="gmail_msg">
>><br class="gmail_msg">
>> <a href="https://bugzilla.redhat.com/1332463" rel="noreferrer" class="gmail_msg" target="_blank">https://bugzilla.redhat.com/1332463</a><br class="gmail_msg">
>><br class="gmail_msg">
>> But I do not remember reports from people trying it.<br class="gmail_msg">
>><br class="gmail_msg">
> Good point, I planned to first get 3.6 running on el7 and from there upgrade<br class="gmail_msg">
> hosted-engine to 4.0 ( between step 6 and 7 ). Altough this way I keep old<br class="gmail_msg">
> 3.6 files on my fresh installl...what would you advice? directly install 4.0<br class="gmail_msg">
> on new el7 host? ( I am running 3.6.7, so above bug is probably fixed ).<br class="gmail_msg">
<br class="gmail_msg">
If you look at the bug page you see it's fixed in 3.6.6. And even if you had<br class="gmail_msg">
something earlier you should have been fine, as the fix works also for earlier<br class="gmail_msg">
3.6 upgraded to 3.6.6 (or later).<br class="gmail_msg">
<br class="gmail_msg">
The question whether to first migrate from el6/3.6 to el7/3.6 and later to 4.0<br class="gmail_msg">
or do this in a single jump is a matter of your motivation and your style.<br class="gmail_msg">
<br class="gmail_msg">
Do you prefer to do large changes at once, or gradually?<br class="gmail_msg">
<br class="gmail_msg"></blockquote></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_quote gmail_msg"><div class="gmail_msg">I want to be able do a roll back when thing don't work, so I think I start with upgrade to el7 with 3.6.</div><div class="gmail_msg">Not sure if it would happen, but this way I don't change anything version related stuff on the storage side where the VMs reside.</div></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_quote gmail_msg"><br class="m_-8768991825503312413inbox-inbox-Apple-interchange-newline gmail_msg"><div class="gmail_msg"> </div><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Do you have some specific new features you want in 4.0?<br class="gmail_msg">
<br class="gmail_msg"></blockquote><div class="gmail_msg"><br class="gmail_msg"></div></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_quote gmail_msg"><div class="gmail_msg">Currently I have some issues where my OVF image files of the hosted engine storage is not updated ( timestamp on hosts folders/ files stay the same )</div><div class="gmail_msg">I am hoping this broken thing is fixed once I have upgraded.</div><div class="gmail_msg">There are further no specific issues I want to upgrade, just to stay current.</div><div class="gmail_msg">I am running oVirt since 3.4 and it took ( and still takes ) time to learn about the different components, but overall I love how stable it functions ov.<br class="gmail_msg"></div></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_quote gmail_msg"><div class="gmail_msg"><span style="line-height:1.5" class="gmail_msg"> </span><br class="gmail_msg"></div><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
><br class="gmail_msg">
><br class="gmail_msg">
><br class="gmail_msg">
>><br class="gmail_msg">
>> One very important thing you did not mention: Try this on a test system,<br class="gmail_msg">
>> including rollback to your backup, after you finished everything and<br class="gmail_msg">
>> (supposedly) found out something broken. Better safe than sorry :-)<br class="gmail_msg">
><br class="gmail_msg">
><br class="gmail_msg">
> A test setup might provide a good practice. But requires extra spare<br class="gmail_msg">
> hosts...<br class="gmail_msg">
<br class="gmail_msg">
You can test using nested-kvm.<br class="gmail_msg">
<br class="gmail_msg"></blockquote></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_quote gmail_msg"><div class="gmail_msg">That might be a good idea, will certainly review!</div></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_quote gmail_msg"><div class="gmail_msg"> </div><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
>I do have a bare metal restore option. So I am able ( with cd boot<br class="gmail_msg">
> and console mode) to restore hosted engine within an hour to previous state<br class="gmail_msg">
> :-)<br class="gmail_msg">
<br class="gmail_msg">
Including the shared storage? Just mentioning. With decent shared storage<br class="gmail_msg">
you probably just revert to a snapshot.<br class="gmail_msg">
<br class="gmail_msg"></blockquote></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_quote gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">My Hostedengine storage is mounted as NFS, so backingup/<span style="line-height:1.5" class="gmail_msg">restoring nfs folder on server might be even</span><span class="m_-8768991825503312413inbox-inbox-inbox-inbox-Apple-converted-space gmail_msg" style="line-height:1.5"> </span><span style="line-height:1.5" class="gmail_msg">easier :)</span></div><br class="m_-8768991825503312413inbox-inbox-Apple-interchange-newline gmail_msg"></div></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hey, these are you own systems, you know how much you trust your tools etc.<br class="gmail_msg">
Just pointing out. Also, mainly, for other potential readers of this thread...<br class="gmail_msg">
<br class="gmail_msg"></blockquote></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_quote gmail_msg"><div class="gmail_msg">Thanks!</div></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_quote gmail_msg"><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg"> </div><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
><br class="gmail_msg">
> Thanks a lot for all info!<br class="gmail_msg">
><br class="gmail_msg">
>><br class="gmail_msg">
>> Best,<br class="gmail_msg">
>><br class="gmail_msg">
>> ><br class="gmail_msg">
>> > Best Regards,<br class="gmail_msg">
>> > Paul<br class="gmail_msg">
>> ><br class="gmail_msg">
>> ><br class="gmail_msg">
>> ><br class="gmail_msg">
>> > Op do 30 jun. 2016 om 14:44 schreef Simone Tiraboschi<br class="gmail_msg">
>> > <<a href="mailto:stirabos@redhat.com" class="gmail_msg" target="_blank">stirabos@redhat.com</a>>:<br class="gmail_msg">
>> >><br class="gmail_msg">
>> >> On Thu, Jun 30, 2016 at 8:34 AM, Paul Groeneweg | Pazion<br class="gmail_msg">
>> >> <<a href="mailto:paul@pazion.nl" class="gmail_msg" target="_blank">paul@pazion.nl</a>><br class="gmail_msg">
>> >> wrote:<br class="gmail_msg">
>> >> > Hi Yedidyah,<br class="gmail_msg">
>> >> ><br class="gmail_msg">
>> >> > Thank you for the comprehensive answers.<br class="gmail_msg">
>> >> ><br class="gmail_msg">
>> >> > I think I go for a complete reinstall ( read also OS upgrade tool is<br class="gmail_msg">
>> >> > not<br class="gmail_msg">
>> >> > adviced on 6.6 or higher as there might be newer packages as on 7 ).<br class="gmail_msg">
>> >> > No<br class="gmail_msg">
>> >> > doubting to re-use current VM or setup from scratch ( fresh host with<br class="gmail_msg">
>> >> > new<br class="gmail_msg">
>> >> > hosted-engine and existing storage domein ).<br class="gmail_msg">
>> >><br class="gmail_msg">
>> >> If you are planning to redeploy hosted-engien from scratch and<br class="gmail_msg">
>> >> restoring on the new engine DB a backup of the previous one, please<br class="gmail_msg">
>> >> carefully consider this:<br class="gmail_msg">
>> >> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1240466#c21" rel="noreferrer" class="gmail_msg" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1240466#c21</a><br class="gmail_msg">
>> >><br class="gmail_msg">
>> >> So, if you choose that path you'll have also to manually remove any<br class="gmail_msg">
>> >> reference to the previous hosted-engine from the restored DB.<br class="gmail_msg">
>> >> I'd strongly suggest you to wait for the upgrade tool to be fixed<br class="gmail_msg">
>> >> since manually doing this upgrade can be really error prone.<br class="gmail_msg">
>> >><br class="gmail_msg">
>> >> > You explain the steps ( 1 to 6 ), but then don't talk about storage<br class="gmail_msg">
>> >> > domain<br class="gmail_msg">
>> >> > import.<br class="gmail_msg">
>> >> > Does it mean, when I reinstall the hosted-engine in the current he VM<br class="gmail_msg">
>> >> > and<br class="gmail_msg">
>> >> > restore an engine-backup ( step 5 ) I am able to start vm from Host<br class="gmail_msg">
>> >> > and<br class="gmail_msg">
>> >> > it<br class="gmail_msg">
>> >> > is still connected to the master storage ( so no need for storage<br class="gmail_msg">
>> >> > import) ?<br class="gmail_msg">
>> >> ><br class="gmail_msg">
>> >> > Best Regards,<br class="gmail_msg">
>> >> > Paul Groeneweg<br class="gmail_msg">
>> >> ><br class="gmail_msg">
>> >> ><br class="gmail_msg">
>> >> > Op do 30 jun. 2016 om 08:00 schreef Yedidyah Bar David<br class="gmail_msg">
>> >> > <<a href="mailto:didi@redhat.com" class="gmail_msg" target="_blank">didi@redhat.com</a>>:<br class="gmail_msg">
>> >> >><br class="gmail_msg">
>> >> >> On Wed, Jun 29, 2016 at 10:07 PM, Paul Groeneweg | Pazion<br class="gmail_msg">
>> >> >> <<a href="mailto:paul@pazion.nl" class="gmail_msg" target="_blank">paul@pazion.nl</a>> wrote:<br class="gmail_msg">
>> >> >> ><br class="gmail_msg">
>> >> >> > I am looking for a way to get my hosted-engine running on el7 so I<br class="gmail_msg">
>> >> >> > can<br class="gmail_msg">
>> >> >> > upgrade to oVirt 4.0. Currently my hosts already run el7, but my<br class="gmail_msg">
>> >> >> > hosted-engine is still el6.<br class="gmail_msg">
>> >> >> ><br class="gmail_msg">
>> >> >> > I read<br class="gmail_msg">
>> >> >> ><br class="gmail_msg">
>> >> >> ><br class="gmail_msg">
>> >> >> ><br class="gmail_msg">
>> >> >> > <a href="https://www.ovirt.org/documentation/how-to/hosted-engine-host-OS-upgrade/" rel="noreferrer" class="gmail_msg" target="_blank">https://www.ovirt.org/documentation/how-to/hosted-engine-host-OS-upgrade/</a><br class="gmail_msg">
>> >> >> > but this is only about the hosts.<br class="gmail_msg">
>> >> >> ><br class="gmail_msg">
>> >> >> > I read <a href="https://www.ovirt.org/documentation/how-to/hosted-engine/" rel="noreferrer" class="gmail_msg" target="_blank">https://www.ovirt.org/documentation/how-to/hosted-engine/</a>,<br class="gmail_msg">
>> >> >> > but<br class="gmail_msg">
>> >> >> > it<br class="gmail_msg">
>> >> >> > only mentions upgrade of the hosted-engine software, not the OS.<br class="gmail_msg">
>> >> >> ><br class="gmail_msg">
>> >> >> > I understood I can do a fresh hosted-engine install, and then<br class="gmail_msg">
>> >> >> > import<br class="gmail_msg">
>> >> >> > my<br class="gmail_msg">
>> >> >> > storage domain to the new hosted engine, but:<br class="gmail_msg">
>> >> >> ><br class="gmail_msg">
>> >> >> > - Do I need to restore my hosted engine database? ( like described<br class="gmail_msg">
>> >> >> > here:<br class="gmail_msg">
>> >> >> ><br class="gmail_msg">
>> >> >> ><br class="gmail_msg">
>> >> >> ><br class="gmail_msg">
>> >> >> > <a href="http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine/" rel="noreferrer" class="gmail_msg" target="_blank">http://www.ovirt.org/develop/developer-guide/engine/migrate-to-hosted-engine/</a><br class="gmail_msg">
>> >> >> > )<br class="gmail_msg">
>> >> >><br class="gmail_msg">
>> >> >> You might not have to, if you only care about the imported VMs from<br class="gmail_msg">
>> >> >> your<br class="gmail_msg">
>> >> >> storage. This will not keep other configuration, such as<br class="gmail_msg">
>> >> >> users/roles/permissions<br class="gmail_msg">
>> >> >> etc.<br class="gmail_msg">
>> >> >><br class="gmail_msg">
>> >> >> > - Can I directly install hosted-engine 4.0 and then import the<br class="gmail_msg">
>> >> >> > storage<br class="gmail_msg">
>> >> >> > domain? Or should I install same hosted-engine version?<br class="gmail_msg">
>> >> >><br class="gmail_msg">
>> >> >> AFAIK 4.0 engine can import 3.6 storage domains without problem.<br class="gmail_msg">
>> >> >><br class="gmail_msg">
>> >> >> > - Do I first need another master storage domain or can I directly<br class="gmail_msg">
>> >> >> > import<br class="gmail_msg">
>> >> >> > my<br class="gmail_msg">
>> >> >> > old master storage domain?<br class="gmail_msg">
>> >> >><br class="gmail_msg">
>> >> >> No idea. Even if you do, you can create a small empty one and later<br class="gmail_msg">
>> >> >> remove<br class="gmail_msg">
>> >> >> it.<br class="gmail_msg">
>> >> >><br class="gmail_msg">
>> >> >> > - When importing the storage domain what is the risk it fails ( I<br class="gmail_msg">
>> >> >> > have<br class="gmail_msg">
>> >> >> > backups, but it would cost a day to restore all )<br class="gmail_msg">
>> >> >><br class="gmail_msg">
>> >> >> No idea, but IIRC we got many successful reports and at most few<br class="gmail_msg">
>> >> >> failures<br class="gmail_msg">
>> >> >> for this.<br class="gmail_msg">
>> >> >><br class="gmail_msg">
>> >> >> > - How long would import take? few minutes or hours? ( I want to<br class="gmail_msg">
>> >> >> > keep<br class="gmail_msg">
>> >> >> > down<br class="gmail_msg">
>> >> >> > time as low as possible ).<br class="gmail_msg">
>> >> >><br class="gmail_msg">
>> >> >> Again no idea. Perhaps do some test?<br class="gmail_msg">
>> >> >><br class="gmail_msg">
>> >> >> ><br class="gmail_msg">
>> >> >> > Another option would be upgrade the OS ( with redhat-upgrade-tool<br class="gmail_msg">
>> >> >> > )<br class="gmail_msg">
>> >> >> > or<br class="gmail_msg">
>> >> >> > is<br class="gmail_msg">
>> >> >> > this a path for disaster?<br class="gmail_msg">
>> >> >><br class="gmail_msg">
>> >> >> Didn't work for us well, so we decided to not support it. If you<br class="gmail_msg">
>> >> >> decide<br class="gmail_msg">
>> >> >> to<br class="gmail_msg">
>> >> >> try,<br class="gmail_msg">
>> >> >> make sure you test carefully beforehand. From ovirt's POV:<br class="gmail_msg">
>> >> >> 1. You'll need to handle postgresql upgrade.<br class="gmail_msg">
>> >> >> 2. Right after OS upgrade, you'll still have (I think) el6 packages<br class="gmail_msg">
>> >> >> of the engine. It will hopefully be in a good-enough state for<br class="gmail_msg">
>> >> >> upgrade<br class="gmail_msg">
>> >> >> to 4.0, but we didn't test this.<br class="gmail_msg">
>> >> >> 3. Specifically, if upgrade fails, rollback will most likely not<br class="gmail_msg">
>> >> >> work,<br class="gmail_msg">
>> >> >> so you'll have to manually handle this - take a full vm backup and<br class="gmail_msg">
>> >> >> make<br class="gmail_msg">
>> >> >> sure you can restore it.<br class="gmail_msg">
>> >> >><br class="gmail_msg">
>> >> >> ><br class="gmail_msg">
>> >> >> > I hope someone can tell me how I can smoothly upgrade my<br class="gmail_msg">
>> >> >> > hosted-engine<br class="gmail_msg">
>> >> >> > up to<br class="gmail_msg">
>> >> >> > el7 and run oVirt 4.<br class="gmail_msg">
>> >> >><br class="gmail_msg">
>> >> >> We are working on a tool/wizard to help with this process. It used<br class="gmail_msg">
>> >> >> to<br class="gmail_msg">
>> >> >> work,<br class="gmail_msg">
>> >> >> but at some point it was decided that one of the actions it does is<br class="gmail_msg">
>> >> >> risky<br class="gmail_msg">
>> >> >> and was blocked, thus the tool is broken currently.<br class="gmail_msg">
>> >> >><br class="gmail_msg">
>> >> >> You can invoke the tool by running: 'hosted-engine<br class="gmail_msg">
>> >> >> --upgrade-appliance'.<br class="gmail_msg">
>> >> >> As noted above, this is currently broken.<br class="gmail_msg">
>> >> >><br class="gmail_msg">
>> >> >> There are several open bugs about it, e.g.:<br class="gmail_msg">
>> >> >><br class="gmail_msg">
>> >> >> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1319457" rel="noreferrer" class="gmail_msg" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1319457</a><br class="gmail_msg">
>> >> >> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1343425" rel="noreferrer" class="gmail_msg" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1343425</a><br class="gmail_msg">
>> >> >> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1343593" rel="noreferrer" class="gmail_msg" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1343593</a> (closed, this is<br class="gmail_msg">
>> >> >> what broke the tool)<br class="gmail_msg">
>> >> >><br class="gmail_msg">
>> >> >> Basically, you can manually do what the tool is supposed to do:<br class="gmail_msg">
>> >> >> 1. Make sure state is clean and stable (no running/pending storage<br class="gmail_msg">
>> >> >> actions,<br class="gmail_msg">
>> >> >> no VMs in the middle of migration etc), all clusters are compat<br class="gmail_msg">
>> >> >> level<br class="gmail_msg">
>> >> >> 3.6,<br class="gmail_msg">
>> >> >> etc.<br class="gmail_msg">
>> >> >> 2. Move to global maintenance<br class="gmail_msg">
>> >> >> 3. backup the engine using engine-backup and keep the backup<br class="gmail_msg">
>> >> >> elsewhere<br class="gmail_msg">
>> >> >> 4. Reinstall engine vm with el7 and 4.0 engine (the tool will use<br class="gmail_msg">
>> >> >> the<br class="gmail_msg">
>> >> >> engine<br class="gmail_msg">
>> >> >> appliance, you might too but not sure how exactly).<br class="gmail_msg">
>> >> >> 5. Restore the backup and run engine-setup.<br class="gmail_msg">
>> >> >> 6. If all looks ok, leave global maintenance.<br class="gmail_msg">
>> >> >><br class="gmail_msg">
>> >> >> If you manually keep a full backup of the engine vm before step 4,<br class="gmail_msg">
>> >> >> you might be able to restore this backup if there are problems.<br class="gmail_msg">
>> >> >> Doing this in the provided tool is currently the main blocking issue<br class="gmail_msg">
>> >> >> for it. Hopefully will be provided in 4.0.1.<br class="gmail_msg">
>> >> >><br class="gmail_msg">
>> >> >> Best,<br class="gmail_msg">
>> >> >> --<br class="gmail_msg">
>> >> >> Didi<br class="gmail_msg">
>> >> ><br class="gmail_msg">
>> >> ><br class="gmail_msg">
>> >> > _______________________________________________<br class="gmail_msg">
>> >> > Users mailing list<br class="gmail_msg">
>> >> > <a href="mailto:Users@ovirt.org" class="gmail_msg" target="_blank">Users@ovirt.org</a><br class="gmail_msg">
>> >> > <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br class="gmail_msg">
>> >> ><br class="gmail_msg">
>><br class="gmail_msg">
>><br class="gmail_msg">
>><br class="gmail_msg">
>> --<br class="gmail_msg">
>> Didi<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
--<br class="gmail_msg">
Didi<br class="gmail_msg">
</blockquote></div></div></blockquote></div></div>