2:08 p.m.
On 29 Nov 2018, at 06:04, Michal Skrivanek
<michal.skrivanek(a)redhat.com> wrote:
> On 28 Nov 2018, at 11:05, Nir Soffer <nsoffer(a)redhat.com
<mailto:nsoffer@redhat.com>> wrote:
>
> On Wed, Nov 28, 2018 at 5:53 PM Martin Perina <mperina(a)redhat.com
<mailto:mperina@redhat.com>> wrote:
>
>
> On Wed, 28 Nov 2018, 16:29 Yuval Turgeman <yturgema(a)redhat.com
<mailto:yturgema@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(a)redhat.com
<mailto: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 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?
Thanks,
michal
[1]
https://libvirt.org/git/?p=libvirt.git;a=commit;h=3ecbac95cd2a02ba5e2f98c...
<https://libvirt.org/git/?p=libvirt.git;a=commit;h=3ecbac95cd2a02ba5e2f98c...
>
> Fix - install old cpu_map.xml
> $ wget
https://raw.githubusercontent.com/libvirt/libvirt/18cab54c3a0bc72390f2930...
<https://raw.githubusercontent.com/libvirt/libvirt/18cab54c3a0bc72390f2930...
-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 -- devel(a)ovirt.org <mailto:devel@ovirt.org>
> To unsubscribe send an email to devel-leave(a)ovirt.org
<mailto:devel-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/devel@ovirt.org/message/RTKM4Y2OSPZ...
<https://lists.ovirt.org/archives/list/devel@ovirt.org/message/RTKM4Y2OSPZ...
> _______________________________________________
> Devel mailing list -- devel(a)ovirt.org <mailto:devel@ovirt.org>
> To unsubscribe send an email to devel-leave(a)ovirt.org
<mailto:devel-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/devel@ovirt.org/message/FIFOWMUL3XX...
<https://lists.ovirt.org/archives/list/devel@ovirt.org/message/FIFOWMUL3XX...
> _______________________________________________
> Devel mailing list -- devel(a)ovirt.org <mailto:devel@ovirt.org>
> To unsubscribe send an email to devel-leave(a)ovirt.org
<mailto:devel-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/devel@ovirt.org/message/ETVT56EYWTP...
<https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ETVT56EYWTP...