[ovirt-users] Re: Issues deploying 4.4 with HE on new EPYC hosts

On Thu, May 28, 2020 at 11:56 PM Gianluca Cecchi < gianluca.cecchi(a)gmail.com&gt; wrote: > On Thu, May 28, 2020 at 3:09 PM Gianluca Cecchi < > gianluca.cecchi(a)gmail.com&gt; wrote: > > [snip] > >> >> >> for the cluster type in the mean time I was able to change it to "Intel >> Cascadelake Server Family" from web admin gui and now I have to try >> these steps and see if engine starts automatically without manual operations >> >> 1) set global maintenance >> 2) shutdown engine >> 3) exit maintenance >> 4) see if the engine vm starts without the cpu flag.... >> >> > I confirm that point 4) was successful and engine vm was able to > autostart, after changing cluster type. > As expected, in my opinion now the point is just about understanding why the engine detected your host with the wrong CPU features set. To be fully honest, as you can see in https://github.com/oVirt/ovirt-ansible-hosted-engine-setup/blob/master/RE... , we already have a variable (he_cluster_cpu_type) to force a cluster CPU type from the ansible role but I don't think is exposed in the interactive installer.

That one is just a leftover from the install process. It's normally automatically cleaned up as one of the latest actions in the ansible role used for the deployment. I suspect that, due to the wrongly detected CPU type, in your case something failed really close to the end of the deployment and so the leftover: you can safely manually delete it. Yes, the deploy failed because it was not anle to detected final engine as