Ubuntu
libvirt package

  1. Bug #1641615
  2. Comment #3

Comment 3 for bug 1641615

Revision history for this message
Christian Ehrhardt  (paelzer) wrote : Re: FTBFS of libvirt 2.1 in zesty

The part of "libvirt: XML-RPC error : authentication failed: Failed to verify peer's certificate" should not confuse too much - that seems to be rather a warning but goes on ok.

E.g. in the working autopkgtest zesty env I can get this when setting verbose and running the test:
$ VIR_TEST_VERBOSE=1 ./virnettlssessiontest
TEST: virnettlssessiontest
 1) TLS Session servercertreq.filename + clientcertreq.filename ... OK
 2) TLS Session servercertreq.filename + clientcertaltreq.filename ... libvirt: XML-RPC error : authentication failed: Failed to verify peer's certificate
OK
 3) TLS Session servercertalt1req.filename + clientcertreq.filename ... OK
 4) TLS Session servercertalt1req.filename + clientcertreq.filename ... OK
 5) TLS Session servercertalt1req.filename + clientcertreq.filename ... libvirt: XML-RPC error : authentication failed: Failed to verify peer's certificate
OK
 6) TLS Session servercertalt2req.filename + clientcertreq.filename ... libvirt: XML-RPC error : authentication failed: Failed to verify peer's certificate
OK
 7) TLS Session servercertalt2req.filename + clientcertreq.filename ... OK
 8) TLS Session servercertalt2req.filename + clientcertreq.filename ... OK
 9) TLS Session servercertreq.filename + clientcertreq.filename ... libvirt: XML-RPC error : authentication failed: Failed to verify peer's certificate
OK
10) TLS Session servercertreq.filename + clientcertreq.filename ... OK
11) TLS Session servercertreq.filename + clientcertreq.filename ... OK
12) TLS Session servercertreq.filename + clientcertreq.filename ... libvirt: XML-RPC error : authentication failed: Failed to verify peer's certificate
OK
13) TLS Session servercertreq.filename + clientcertreq.filename ... OK
14) TLS Session servercertreq.filename + clientcertreq.filename ... OK
15) TLS Session servercertlevel3areq.filename + clientcertlevel2breq.filename ... OK

Although it is less of these than on the LP buildlog

So the real issues are:
10) TLS Session servercertreq.filename + clientcertreq.filename ... FAILED
11) TLS Session servercertreq.filename + clientcertreq.filename ... FAILED
13) TLS Session servercertreq.filename + clientcertreq.filename ... FAILED
14) TLS Session servercertreq.filename + clientcertreq.filename ... FAILED

Unfortunately is isn't very verbose even with verbose and debug enabled and the lack of local reproducibility doesn't help either.