<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Oct 31, 2014 at 12:54 PM, Daniel Helgenberger <span dir="ltr"><<a href="mailto:daniel.helgenberger@m-box.de" target="_blank">daniel.helgenberger@m-box.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br></span><span class=""><br>
> Afterwards I clean hypervisor hosts one by one and clean/reinstall it into<br>
> the cluster?<br>
</span>This what I have done; remember you need to add the 3.5 repos otherwise<br>
VDSM will be (re)installed from the latest 3.4 repos and not upgraded to<br>
the '3.5' version. Also, this process went like a charm without any<br>
issues (let alone loosing guest)<br>
></blockquote><div><br></div><div>One question related to host reinstall vs "yum update vdsm*" comes into my mind now..</div><div><br></div><div>On one of my all-in-one environments, which started from 3.0 days and now is at 3.5 through progressive updates, I recently noticed some *.rpmnew packages related to both engine and vdsm components.</div><div>I always updated the host part through "yum update" on this all-in-one server.</div><div>This situation forced me to compare running .conf file vs .rpmnew ones and to clean then the situation.</div><div><br></div><div>The question is: in general when you run "reinstall host" from engine gui, does this process run a "yum update" and so you should care about possible change in .conf files format, or does it go through uninstall/install?</div><div><br></div><div>Thanks</div><div>Gianluca</div></div></div></div>