<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.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-9) [] Command 'GetCapabilitiesVDSCommand(HostName = hosted_engine_2, VdsIdAndVdsVDSCommandParametersBase:{hostId='7d2b3f49-0fbb-493b-8f3c-5283566e830d', vds='Host[hosted_engine_2,7d2b3f49-0fbb-493b-8f3c-5283566e830d]'})' 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/<wbr>drive/folders/<wbr>1tZHLIMV0ctGyeDPcGMlJa6evk6fkr<wbr>Cz8?usp=sharing</a><br></div><div><br></div><div>Thanks for your support</div><div><br></div><div>Carl</div><div><br></div><div> </div></div><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 class=""><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="HOEnZb"><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>