Michal Skrivanek <[email protected]> writes: >> On 29 Nov 2018, at 06:04, Michal Skrivanek <[email protected]> >> wrote: >> >> >> >>> On 28 Nov 2018, at 11:05, Nir Soffer <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> On Wed, Nov 28, 2018 at 5:53 PM Martin Perina <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> >>> On Wed, 28 Nov 2018, 16:29 Yuval Turgeman <[email protected] >>> <mailto:[email protected]> wrote: >>> Adding Gal, I think he fixed some of those issues (around add host) >>> >>> On Wed, Nov 28, 2018 at 5:05 PM Nir Soffer <[email protected] >>> <mailto:[email protected]>> wrote: >>> If you want to add host running Fedora 28, you need to do few manual steps: >>> >>> 1. Add hosts fail to configure the firewall >>> >>> Do not check the "Configure filewall" checkbox >>> >>> Adding host will fail because engine cannot communicate with vdsm. >>> >>> Fix - disable the firewall on the host. >>> $ iptables -F >>> >>> There is probably a better way, but I did not find it yet :-) >>> >>> Sandro, do we have an update about this? >>> >>> AFAIK this has been fixed more than 2 weeks ago in >>> https://gerrit.ovirt.org/95286 <https://gerrit.ovirt.org/95286> >>> Could you please retry with updated engine? >>> >>> I'll test this, thanks. >>> >>> >>> >>> 2. Engine fail in Host.getCapabilties >>> >>> Libvirt changed the location and format of this file. This will cause >>> Host.getCapabilties >>> to fai, and the host will become "Unassigned" >>> >>> This is a new issue revealed by updating our virt-preview repo this week. >> >> yeah, apparently a change in libvirt 4.7[1]. More changes are about >> to follow and we will need to change the logic how we get CPUs from >> libvirt eventually. >> For now a simple check for both locations should do > > Bleh, sorry, no it won’t > So, Milan, the right way would be to query the capabilities which is > not a trivial change…but it is the only way how to stop reading > libvirt internal configs. > Is that what you’re planning to do?
Not initially, but indeed it looks like the right way. I'll do it. >> Thanks, >> michal >> >> [1] >> https://libvirt.org/git/?p=libvirt.git;a=commit;h=3ecbac95cd2a02ba5e2f98c625386ec12c8bbdac >> <https://libvirt.org/git/?p=libvirt.git;a=commit;h=3ecbac95cd2a02ba5e2f98c625386ec12c8bbdac> >> >>> >>> Fix - install old cpu_map.xml >>> $ wget >>> https://raw.githubusercontent.com/libvirt/libvirt/18cab54c3a0bc72390f29300684396690a7ecf51/src/cpu/cpu_map.xml >>> <https://raw.githubusercontent.com/libvirt/libvirt/18cab54c3a0bc72390f29300684396690a7ecf51/src/cpu/cpu_map.xml> >>> -O /usr/share/libvirt/cpu_map.xml >>> >>> Engine should retry and succeed after that. >>> >>> 3. Sanlock fail to write to its pid file, connecting to storage fail >>> >>> Fix - set selinux to permissive mode >>> $ setenforce 0 >>> >>> To make this persistent edit /etc/selinux/config >>> SELINUX=permissive >>> >>> We have a bug for this. >>> >>> After that you should have a working system. >>> >>> Nir >>> >>> _______________________________________________ >>> Devel mailing list -- [email protected] <mailto:[email protected]> >>> To unsubscribe send an email to [email protected] >>> <mailto:[email protected]> >>> 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/[email protected]/message/RTKM4Y2OSPZO4CEWZVRBUALNGMGHIQ4L/ >>> <https://lists.ovirt.org/archives/list/[email protected]/message/RTKM4Y2OSPZO4CEWZVRBUALNGMGHIQ4L/> >>> _______________________________________________ >>> Devel mailing list -- [email protected] <mailto:[email protected]> >>> To unsubscribe send an email to [email protected] >>> <mailto:[email protected]> >>> 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/[email protected]/message/FIFOWMUL3XXPTTEDKOIT6VLO3GJ5R33H/ >>> <https://lists.ovirt.org/archives/list/[email protected]/message/FIFOWMUL3XXPTTEDKOIT6VLO3GJ5R33H/> >>> _______________________________________________ >>> Devel mailing list -- [email protected] <mailto:[email protected]> >>> To unsubscribe send an email to [email protected] >>> <mailto:[email protected]> >>> 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/[email protected]/message/ETVT56EYWTPDLSFXTEN5OLLKGDC34Y34/ >>> <https://lists.ovirt.org/archives/list/[email protected]/message/ETVT56EYWTPDLSFXTEN5OLLKGDC34Y34/> _______________________________________________ Devel 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/BP3ZHQU3NGQ2K2TNBQOIX6MKE2U5J4DC/
