On 29 Nov 2018, at 06:04, Michal Skrivanek <michal.skrivanek@redhat.com> wrote:On 28 Nov 2018, at 11:05, Nir Soffer <nsoffer@redhat.com> wrote:On Wed, Nov 28, 2018 at 5:53 PM Martin Perina <mperina@redhat.com> 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 <nsoffer@redhat.com> wrote:If you want to add host running Fedora 28, you need to do few manual steps:1. Add hosts fail to configure the firewallDo not check the "Configure filewall" checkboxAdding host will fail because engine cannot communicate with vdsm.Fix - disable the firewall on the host.$ iptables -FThere 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 Could you please retry with updated engine?I'll test this, thanks.2. Engine fail in Host.getCapabiltiesLibvirt changed the location and format of this file. This will cause Host.getCapabiltiesto 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
Thanks,michal_____________________________________________________________________________________________________________________________________________Fix - install old cpu_map.xml$ wget https://raw.githubusercontent.com/libvirt/libvirt/18cab54c3a0bc72390f29300684396690a7ecf51/src/cpu/cpu_map.xml -O /usr/share/libvirt/cpu_map.xmlEngine should retry and succeed after that.3. Sanlock fail to write to its pid file, connecting to storage failFix - set selinux to permissive mode$ setenforce 0To make this persistent edit /etc/selinux/configSELINUX=permissiveWe have a bug for this.After that you should have a working system.Nir
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-leave@ovirt.org
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/devel@ovirt.org/message/RTKM4Y2OSPZO4CEWZVRBUALNGMGHIQ4L/
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-leave@ovirt.org
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/devel@ovirt.org/message/FIFOWMUL3XXPTTEDKOIT6VLO3GJ5R33H/
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-leave@ovirt.org
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/devel@ovirt.org/message/ETVT56EYWTPDLSFXTEN5OLLKGDC34Y34/