<div dir="ltr">Hi all,<div><br></div><div>So i got a bit futher on getting everithing back on. After removing the ca.epem certificate and redoing engine-setup on the hosted-engine vm i was able to remove/reinstall one of my 2 hosts. Now i am facing a other problem. I need this new host to be able to run the hosted engine vm. But if re-install the host and in the hosted engine tab set to DEPLOY the host is add successfully and can run vms but it seem that the DEPLOY did not work..</div><div><br></div><div>If i am not able to make this host run the engine vm i cant fix(re-install) the second host.</div><div><br></div><div>Any insight would be appreciated. </div><div><br></div><div>Thanks.</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jan 6, 2018 at 12:40 PM, carl langlois <span dir="ltr"><<a href="mailto:crl.langlois@gmail.com" target="_blank">crl.langlois@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Yes i have try removing it and re-adding it and i have the problem with certifcate enrollement..<div><br></div><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jan 6, 2018 at 12:08 PM, Donny Davis <span dir="ltr"><<a href="mailto:donny@fortnebula.com" target="_blank">donny@fortnebula.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Have you tried to remove that host and readd it?<div><br></div><div>Also there is a bug that throws the same error, not sure if its related. Did you have your hosts in maintenance prior to upgrading? </div><div><br></div><div><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1258589" target="_blank">https://bugzilla.redhat.com/sh<wbr>ow_bug.cgi?id=1258589</a><br></div></div><div class="m_2240167022784991107HOEnZb"><div class="m_2240167022784991107h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jan 6, 2018 at 10:52 AM, carl langlois <span dir="ltr"><<a href="mailto:crl.langlois@gmail.com" target="_blank">crl.langlois@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi <div>I have put the new engine_enrolfail.log that conain the error when re-installing .</div><div><br></div><div><br></div><div><a href="https://drive.google.com/drive/folders/1tZHLIMV0ctGyeDPcGMlJa6evk6fkrCz8?usp=sharing" target="_blank">https://drive.google.com/drive<wbr>/folders/1tZHLIMV0ctGyeDPcGMlJ<wbr>a6evk6fkrCz8?usp=sharing</a><br></div><div><br></div><div><br></div><div>Thanks</div></div><div class="m_2240167022784991107m_-8665715087415631844HOEnZb"><div class="m_2240167022784991107m_-8665715087415631844h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jan 6, 2018 at 10:18 AM, Benny Zlotnik <span dir="ltr"><<a href="mailto:bzlotnik@redhat.com" target="_blank">bzlotnik@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Can you please provide the log with the error?<br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="m_2240167022784991107m_-8665715087415631844m_4036988907743105176h5">On Sat, Jan 6, 2018 at 5:09 PM, carl langlois <span dir="ltr"><<a href="mailto:crl.langlois@gmail.com" target="_blank">crl.langlois@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_2240167022784991107m_-8665715087415631844m_4036988907743105176h5"><div dir="ltr">Hi again,<div><br></div><div>I manage to go a little bit further.. I was not able to set one host to maintenance because they had running vm.. so i force it to mark it as reboot and flush any vm and now i can try to reinstall the host.. but now i am getting error when the installation try to enroll certificate..</div><div><br></div><div>Any idea?</div><div><br></div><div>Thanks</div><span class="m_2240167022784991107m_-8665715087415631844m_4036988907743105176m_2574870489785537959HOEnZb"><font color="#888888"><div>Carl</div><div><br></div></font></span></div><div class="m_2240167022784991107m_-8665715087415631844m_4036988907743105176m_2574870489785537959HOEnZb"><div class="m_2240167022784991107m_-8665715087415631844m_4036988907743105176m_2574870489785537959h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jan 6, 2018 at 9:41 AM, carl langlois <span dir="ltr"><<a href="mailto:crl.langlois@gmail.com" target="_blank">crl.langlois@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>Thanks for the quick reply.</div><div><br></div><div>Version before the update was the latest 4.1. </div><div>The storage is NFS.</div><div>The host are plain 7.4 Centos.i keep them up to date</div><div>if i remenber the initail deploy of the engine vm was full OS</div><div><br></div><div>The step to upgrade was:</div><div><br></div><div>SSH to hosted engine vm , </div><div>yum install 4.2 release</div><div>run engine-setup.</div><div>this where i think something when wrong.</div><div>the engine setup was not able to update some certificate.. a quick search on the internet and found that moving the ca.pem from the /etc/pki/ovrit-engine made the engine-setup work..</div><div><br></div><div>from that point the hosted_engine seem to work fine but all hosts and data center are not operational.</div><div><br></div><div>One of my main concern is losing all the template and users vm.. </div><div><br></div><div><br></div><div><br></div><div>Engine and vdsm log of one host are here..</div><div><br></div><div>In the engine log there is a lot of this error..</div><div><br></div><div>2018-01-06 08:31:40,459-05 ERROR [org.ovirt.engine.core.vdsbrok<wbr>er.vdsbroker.GetCapabilitiesVD<wbr>SCommand] (EE-ManagedThreadFactory-engin<wbr>eScheduled-Thread-9) [] Command 'GetCapabilitiesVDSCommand(Hos<wbr>tName = hosted_engine_2, VdsIdAndVdsVDSCommandParameter<wbr>sBase:{hostId='7d2b3f49-0fbb-4<wbr>93b-8f3c-5283566e830d', vds='Host[hosted_engine_2,7d2b<wbr>3f49-0fbb-493b-8f3c-5283566e83<wbr>0d]'})' execution failed: VDSGenericException: VDSNetworkException: General SSLEngine problem.</div><div><br></div><div><a href="https://drive.google.com/drive/folders/1tZHLIMV0ctGyeDPcGMlJa6evk6fkrCz8?usp=sharing" target="_blank">https://drive.google.com/drive<wbr>/folders/1tZHLIMV0ctGyeDPcGMlJ<wbr>a6evk6fkrCz8?usp=sharing</a><br></div><div><br></div><div>Thanks for your support</div><span class="m_2240167022784991107m_-8665715087415631844m_4036988907743105176m_2574870489785537959m_-4784498533870586193HOEnZb"><font color="#888888"><div><br></div><div>Carl</div><div><br></div><div> </div></font></span></div><div class="m_2240167022784991107m_-8665715087415631844m_4036988907743105176m_2574870489785537959m_-4784498533870586193HOEnZb"><div class="m_2240167022784991107m_-8665715087415631844m_4036988907743105176m_2574870489785537959m_-4784498533870586193h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jan 6, 2018 at 8:50 AM, Gianluca Cecchi <span dir="ltr"><<a href="mailto:gianluca.cecchi@gmail.com" target="_blank">gianluca.cecchi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span><div class="gmail_extra"><div class="gmail_quote">On Sat, Jan 6, 2018 at 2:42 PM, carl langlois <span dir="ltr"><<a href="mailto:crl.langlois@gmail.com" target="_blank">crl.langlois@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi again all,<div><br></div><div>I really need your input on recovering my failed upgrade to 4.2.</div><div><br></div><div><br></div></div></blockquote></div><br></div></span><div class="gmail_extra">First two things to do to get appropriate help would be, in my opinion:</div><div class="gmail_extra"><br></div><div class="gmail_extra">1) provide a detailed description of your environment</div><div class="gmail_extra">exact version before the update; kind of storage (Gluster, NFS, iSCSI, FC), kind of hosts (plain OS and which version or node-ng and which version before and after), kind of deploy executed for hosted engine VM at initial install time (appliance, full OS).</div><div class="gmail_extra">Describe steps used for upgrading.</div><div class="gmail_extra"><br></div><div class="gmail_extra">2) upload to a shared file services all the possible logs:</div><div class="gmail_extra">engine logs before and after the upgrade and logs of engine-setup run during update</div><div class="gmail_extra">vdsm logs before and after the upgrade</div><span class="m_2240167022784991107m_-8665715087415631844m_4036988907743105176m_2574870489785537959m_-4784498533870586193m_-2002902374154472268HOEnZb"><font color="#888888"><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Gianluca</div><div class="gmail_extra"><br></div></font></span></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div><br></div></div>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>