<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Dec 22, 2017 at 12:06 PM, Martin Perina <span dir="ltr"><<a href="mailto:mperina@redhat.com" target="_blank">mperina@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"><div style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_extra"><div class="gmail_quote"><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><br><div><br></div><div>Only problem I registered was the first start of engine on the first upgraded host (that should be step 7 in link above), where I got error on engine (not able to access web admin portal); I see this in server.log </div><div>(see full attach here <a href="https://drive.google.com/file/d/1UQAllZfjueVGkXDsBs09S7THGDFn9YPa/view?usp=sharing" target="_blank">https://drive.google.com/file/<wbr>d/1UQAllZfjueVGkXDsBs09S7THGDF<wbr>n9YPa/view?usp=sharing</a> )</div><div><br></div><div>2017-12-22 00:40:17,674+01 INFO [org.quartz.core.QuartzSchedul<wbr>er] (ServerService Thread Pool -- 63) Scheduler DefaultQuartzScheduler_$_NON_C<wbr>LUSTERED started.</div><div>2017-12-22 00:40:17,682+01 INFO [org.jboss.as.clustering.infin<wbr>ispan] (ServerService Thread Pool -- 63) WFLYCLINF0002: Started timeout-base cache from ovirt-engine container</div><div>2017-12-22 00:44:28,611+01 ERROR [org.jboss.as.controller.manag<wbr>ement-operation] (Controller Boot Thread) WFLYCTL0348: Timeout after [300] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'add' at address '[</div><div> ("core-service" => "management"),</div><div> ("management-interface" => "native-interface")</div><div>]'</div></div></div></div></blockquote><div><br></div><div>Adding Vaclav, maybe something in Wildfly? Martin, any hint on engine side?</div></div></div></div></blockquote><div><br></div></div></div><div>Yeah, I've already seen such error a few times, it usually happens when access to storage is really slow or the host itself is overloaded and WildFly is not able to startup properly until default 300 seconds interval is over.</div><div><br></div><div>If this is going to happen often, we will have to raise that timeout for all installations.</div><span class=""><div><br></div></span></div></div></div>
</blockquote></div><br></div><div class="gmail_extra">Ok, thanks for the confirmation of what I suspected.</div><div class="gmail_extra">Actually this particular environment is based on a single NUC where I have ESXi 6.0U2 and the 3 hosts are actually VMs of this vSphere environment, so that the hosted engine is an L2 VM</div><div class="gmail_extra">And the replica 3 (with arbiter) of the hosts insists at the end on a single physical SSD disk below...</div><div class="gmail_extra">All in all it is already a great success that this kind of infrastructure has been able to update from 4.1 to 4.2... I use it basically as a functional testing and btw on vSphere there is also another CentOS 7 VM running ;-)</div><div class="gmail_extra"> </div><div class="gmail_extra">Thanks,</div><div class="gmail_extra">Gianluca</div></div>