Hello, For reasons unknown during oVirt 4.2 -> 4.3 my CPU type was Broadwell IBRS and because of this I can’t upgrade the datacenter to 4.3. The problem was that on 4.3 theres only Broadwell IBRS SSBD and Broadwell. So the only way to up the cluster to 4.3 was to downgrade to plain Broadwell. Now I can’t upgrade it Broadwell IBRS SSBD. So, how can I upgrade it back?

On 9 Feb 2019, at 08:42, Greg Sheremeta <gshereme(a)redhat.com&gt; wrote: On Fri, Feb 8, 2019 at 11:55 PM Juhani Rautiainen <juhani.rautiainen(a)gmail.com <mailto:juhani.rautiainen@gmail.com>> wrote: On Sat, Feb 9, 2019 at 1:05 AM Vinícius Ferrão <ferrao(a)versatushpc.com.br <mailto:ferrao@versatushpc.com.br>> wrote: > > Hello, > > For reasons unknown during oVirt 4.2 -> 4.3 my CPU type was Broadwell IBRS and because of this I can’t upgrade the datacenter to 4.3. The problem was that on 4.3 theres only Broadwell IBRS SSBD and Broadwell. > > So the only way to up the cluster to 4.3 was to downgrade to plain Broadwell. > > Now I can’t upgrade it Broadwell IBRS SSBD. Broadwell IBRS SSBD should be a supported CPU, though. Why can't you set it to that? Are you getting an error, or does it not show in the UI? https://bugzilla.redhat.com/show_bug.cgi?id=1540921#c5 <https://bugzilla.redhat.com/show_bug.cgi?id=1540921#c5>

> > So, how can I upgrade it back? There has been lot's of discussion about that this week. I had same problem with Opteron G3->Epyc conversion. There steps were suggested to me and they worked and you problem is similar: +1, thanks - set HE global maintenance mode - set one of the hosted-engine hosts into maintenance mode - move it to a different cluster - shutdown the engine VM - manually restart the engine VM on the host on the custom cluster directly executing on that host: hosted-engine --vm-start - connect again to the engine - set all the hosts of the initial cluster into maintenance mode - upgrade the cluster - shut down again the engine VM - manually restart the engine VM on one of the hosts of the initial cluster - move back the host that got into a temporary cluster to its initial cluster As first step I would add that you create new cluster which already has 4.3 level and CPU Type you want so already can check if cluster accepts nodes. -Juhani _______________________________________________ Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ <https://www.ovirt.org/site/privacy-policy/> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VFWTYTLXCLN... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/VFWTYTLXCLN... -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com <mailto:gshereme@redhat.com> IRC: gshereme <https://red.ht/sig>

On 9 Feb 2019, at 11:42, Vinícius Ferrão <ferrao(a)versatushpc.com.br&gt; wrote: > On 9 Feb 2019, at 11:29, Vinícius Ferrão <ferrao(a)versatushpc.com.br <mailto:ferrao@versatushpc.com.br>> wrote: > > Hi Greg, > >> On 9 Feb 2019, at 08:42, Greg Sheremeta <gshereme(a)redhat.com <mailto:gshereme@redhat.com>> wrote: >> >> >> On Fri, Feb 8, 2019 at 11:55 PM Juhani Rautiainen <juhani.rautiainen(a)gmail.com <mailto:juhani.rautiainen@gmail.com>> wrote: >> On Sat, Feb 9, 2019 at 1:05 AM Vinícius Ferrão >> <ferrao(a)versatushpc.com.br <mailto:ferrao@versatushpc.com.br>> wrote: >> > >> > Hello, >> > >> > For reasons unknown during oVirt 4.2 -> 4.3 my CPU type was Broadwell IBRS and because of this I can’t upgrade the datacenter to 4.3. The problem was that on 4.3 theres only Broadwell IBRS SSBD and Broadwell. >> > >> > So the only way to up the cluster to 4.3 was to downgrade to plain Broadwell. >> > >> > Now I can’t upgrade it Broadwell IBRS SSBD. >> >> Broadwell IBRS SSBD should be a supported CPU, though. Why can't you set it to that? Are you getting an error, or does it not show in the UI? >> https://bugzilla.redhat.com/show_bug.cgi?id=1540921#c5 <https://bugzilla.redhat.com/show_bug.cgi?id=1540921#c5> > Hi Greg, I don’t know what’s happening. On 4.2 I was using Broadwell IBRS (only), and now I’ve got an error message when selecting Broadwell IBRS SSBD: > > <attachment.png>Host CPU type is not compatible with Cluster Properties. > > I checked the flags and yes, I can’t find SSBD: > > Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb cat_l3 cdp_l3 intel_ppin intel_pt ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm rdt_a rdseed adx smap xsaveopt cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts spec_ctrl intel_stibp > > I don’t know whats happening but I was thinking that my CPU supports this flag: > > Model name: Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz Answering my own question: I think I need a BIOS update. Let me check this…

> > >> >> > >> > So, how can I upgrade it back? >> >> There has been lot's of discussion about that this week. I had same >> problem with Opteron G3->Epyc conversion. There steps were suggested >> to me and they worked and you problem is similar: >> >> +1, thanks >> >> >> - set HE global maintenance mode >> - set one of the hosted-engine hosts into maintenance mode >> - move it to a different cluster >> - shutdown the engine VM >> - manually restart the engine VM on the host on the custom cluster >> directly executing on that host: hosted-engine --vm-start >> - connect again to the engine >> - set all the hosts of the initial cluster into maintenance mode >> - upgrade the cluster >> - shut down again the engine VM >> - manually restart the engine VM on one of the hosts of the initial cluster >> - move back the host that got into a temporary cluster to its initial cluster >> >> As first step I would add that you create new cluster which already >> has 4.3 level and CPU Type you want so already can check if cluster >> accepts nodes. >> >> -Juhani >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org <mailto:users@ovirt.org> >> To unsubscribe send an email to users-leave(a)ovirt.org <mailto:users-leave@ovirt.org> >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ <https://www.ovirt.org/site/privacy-policy/> >> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ <https://www.ovirt.org/community/about/community-guidelines/> >> List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/VFWTYTLXCLN... <https://lists.ovirt.org/archives/list/users@ovirt.org/message/VFWTYTLXCLN... >> >> >> -- >> GREG SHEREMETA >> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX >> Red Hat NA >> >> <https://www.redhat.com/> >> gshereme(a)redhat.com <mailto:gshereme@redhat.com> IRC: gshereme >>

On 9 Feb 2019, at 02:53, Juhani Rautiainen <juhani.rautiainen(a)gmail.com&gt; wrote: On Sat, Feb 9, 2019 at 1:05 AM Vinícius Ferrão <ferrao(a)versatushpc.com.br&gt; wrote: > > Hello, > > For reasons unknown during oVirt 4.2 -> 4.3 my CPU type was Broadwell IBRS and because of this I can’t upgrade the datacenter to 4.3. The problem was that on 4.3 theres only Broadwell IBRS SSBD and Broadwell. > > So the only way to up the cluster to 4.3 was to downgrade to plain Broadwell. > > Now I can’t upgrade it Broadwell IBRS SSBD. > > So, how can I upgrade it back? There has been lot's of discussion about that this week. I had same problem with Opteron G3->Epyc conversion. There steps were suggested to me and they worked and you problem is similar:

- set HE global maintenance mode - set one of the hosted-engine hosts into maintenance mode - move it to a different cluster - shutdown the engine VM - manually restart the engine VM on the host on the custom cluster directly executing on that host: hosted-engine --vm-start - connect again to the engine - set all the hosts of the initial cluster into maintenance mode - upgrade the cluster - shut down again the engine VM - manually restart the engine VM on one of the hosts of the initial cluster - move back the host that got into a temporary cluster to its initial cluster

As first step I would add that you create new cluster which already has 4.3 level and CPU Type you want so already can check if cluster accepts nodes. -Juhani