Hi, thanks for your support so far.
I disabled the ipv6 auto config and have chosen “ipv6 link local only” in nmtui network
manager. I discovered that there is only one ipv4 dns entry in /etc/resolv.conf then
(because the ipv6 dhcp-server is no longer asked). This setting solves my issue and
everything worked just fine.
Here is your requested supervdsm snippet:
https://jan-home.de/public/ovirt/supervdsm.log
Greetings from Germany,
Jan
Von: Dominik Holler <dholler(a)redhat.com>
Gesendet: Montag, 14. September 2020 10:23
An: jan.kleefeld(a)jan-home.de
Cc: users <users(a)ovirt.org>; Ales Musil <amusil(a)redhat.com>; Yedidyah Bar
David <didi(a)redhat.com>
Betreff: Re: [ovirt-users] Probably dns problem: Internal JSON-RPC error
On Sun, Sep 13, 2020 at 11:35 AM Yedidyah Bar David <didi(a)redhat.com
<mailto:didi@redhat.com> > wrote:
On Sun, Sep 13, 2020 at 11:27 AM <jan.kleefeld(a)jan-home.de
<mailto:jan.kleefeld@jan-home.de> > wrote:
I have a clean installed CentOS 8.2 2004 on my server. The self hosted engine deploy
(ovirt-4.4) aborts with the following message:
[ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "msg":
"The host has been set in non_operational status, deployment errors: code 505: Host
red.colors.ovirt.local installation failed. Failed to configure management network on the
host., code 1120: Failed to configure management network on host red.colors.ovirt.local
due to setup networks failure., code 9000: Failed to verify Power Management configuration
for Host red.colors.ovirt.local., code 10802: VDSM red.colors.ovirt.local command
HostSetupNetworksVDS failed: Internal JSON-RPC error:
{'reason': '
desired
=======
---
dns-resolver:
search: []
server:
- 192.168.2.150
- fe80::1%eno1
current
=======
---
dns-resolver:
search: []
server:
- 192.168.2.150
difference
==========
--- desired
+++ current
@@ -3,4 +3,3 @@
search: []
server:
- 192.168.2.150
- - fe80::1%eno1
'}, fix accordingly and re-deploy."}
~# cat /etc/resolv.conf
# Generated by NetworkManager
search colors.ovirt.local
nameserver 192.168.2.150
nameserver fe80::1%eno1
I am confused, because the probalby missing line is present. Is there maybe another
config file, where this last line could be missing?
Maybe I can force somehow the installer, to reload the resolv conf, so it can fetch ne
new line?
Can you please check/share other relevant logs (and perhaps other
parts of this one)? Perhaps upload somewhere and share a link, or open
a bug in bugzilla and attach there.
Adding Dominik.
Perhaps we fail to parse the line 'nameserver fe80::1%eno1'?
Yes, IPv6 link local nameserver might not work for static IP addresses, but might work for
dynamic.
Also mixing IPv4 and IPv6 nameservers might confuse lower layers.
Can you share at least the line containing
"call setupNetworks with "
and
"desired state"
of supervdsm.log?
Thanks and best regards,
--
Didi