Thanks, Ryan. I opened https://bugzilla.redhat.com/show_bug.cgi?id=1674265 to track this.
Greg On Sat, Feb 9, 2019 at 5:50 PM Ryan Bullock <[email protected]> wrote: > Got a host activated! > > 1. Update host to 4.3 > 2. rm /var/cache/libvirt/qemu/capabilities/*.xml > 3. systemctl restart libvirtd > 4. Activate host > > Seems like some kind of stuck state going from 4.2 -> 4.3 > > Hope this helps someone else. > > On Sat, Feb 9, 2019 at 1:12 PM Ryan Bullock <[email protected]> wrote: > >> I tried that too, but it still complains about an unsupported CPU in the >> new cluster. Even if I leave the cluster level at 4.2, if I update the host >> to 4.3 it can't activate under a 4.2 cluster. >> Makes me think something changed in how it verifies the CPU support and >> for some reason it is not liking my EPYC systems. >> >> On Sat, Feb 9, 2019 at 10:18 AM Juhani Rautiainen < >> [email protected]> wrote: >> >>> On Sat, Feb 9, 2019 at 7:43 PM Ryan Bullock <[email protected]> wrote: >>> > >>> > So I tried making a new cluster with a 4.2 compatibility level and >>> moving one of my EPYC hosts into it. I then updated the host to 4.3 and >>> switched the cluster version 4.3 + set cluster cpu to the new AMD EPYC IBPD >>> SSBD (also tried plain AMD EPYC). It still fails to make the host >>> operational complaining that 'CPU type is not supported in this cluster >>> compatibility version or is not supported at all'. >>> > >>> When I did this with Epyc I made new cluster wth 4.3 level and Epyc >>> CPU. And then moved the nodes to it. Maybe try that? I also had to >>> move couple of VM's to new cluster because old cluster couldn't >>> upgrade with those. When nodes and couple problem VM's were in new >>> cluster I could upgrade old cluster to new level. >>> >>> -Juhani >>> >> -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> [email protected] IRC: gshereme <https://red.ht/sig>
_______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/XPUPT5JF4WJNPR6MC4PKRDXVYWQZOMRF/
