Yes, vdsm is not able to resolve 'engine' which is used in engine's
29 kwi 2017 00:37 "Nadav Goldin" <ngoldin(a)redhat.com> napisał(a):
Can you clarify what you noticed is not resolvable - the 'engine' FQDN
On Fri, Apr 28, 2017 at 4:15 PM, Piotr Kliczewski <pkliczew(a)redhat.com>
I started to investigate the issue  and it seems like there is an
in Lago setup we use.
During handshake we have a step to verify whether client certificate was
issued for a specific host (no such functionality in m2crytpo code base).
It works fine when using either ip addresses or fqdns but in this
setup we use mixed.
When added logging I see that in engine certificate we use 'engine' name
which is not resolvable on the host side and the check fails.
I posted a patch  which fixes IPv4 mapped addresses issue but we need
fix the setup issue.
On Thu, Apr 27, 2017 at 3:39 PM, Piotr Kliczewski <pkliczew(a)redhat.com>
> On Thu, Apr 27, 2017 at 3:13 PM, Evgheni Dereveanchin
> <ederevea(a)redhat.com> wrote:
>> Test failed: 002_bootstrap/add_hosts
>> Link to suspected patches:
- ssl: change default library
>> Link to job:
>> VDSM log:
>> Error snippet from VDSM log, this repeats on each connection attempt
>> Engine side:
>> 2017-04-27 06:39:27,768-0400 INFO (Reactor thread)
>> [ProtocolDetector.AcceptorImpl] Accepted connection from
>> ::ffff:192.168.201.3:49530 (protocoldetector:74)
>> 2017-04-27 06:39:27,898-0400 ERROR (Reactor thread) [vds.dispatcher]
>> uncaptured python exception, closing channel
>> <yajsonrpc.betterAsyncore.Dispatcher connected
>> 49530, 0, 0) at 0x1cc3b00> (<class 'socket.error'>:Address
>> supported by protocol [/usr/lib64/python2.7/asyncore.py|readwrite|110]
> This means that what we have in the certificate do not match the source
> address we get. I suspect that we issue the certificate for 192.168.201.3
> but when we get ::ffff:192.168.201.3.
> The change was verified in the env when ipv4 is used. I pushed a revert
>  for now so we can work on fixing the issue.
>  https://gerrit.ovirt.org/#/c/76160
>> Evgheni Dereveanchin
Devel mailing list