[Xen-devel] [libvirt test] 109759: regressions - FAIL

[osstest service owner <osstest-admin@xxxxxxxxxxxxxx>]

flight 109759 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/109759/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-arm64-arm64-libvirt      5 xen-install              fail REGR. vs. 109736

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-libvirt     13 saverestore-support-check    fail  like 109736
 test-armhf-armhf-libvirt-xsm 13 saverestore-support-check    fail  like 109736
 test-armhf-armhf-libvirt-raw 12 saverestore-support-check    fail  like 109736
 test-amd64-i386-libvirt      12 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt-xsm 12 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt-xsm  12 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt     12 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check 
fail never pass
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check 
fail never pass
 test-arm64-arm64-libvirt-xsm 12 migrate-support-check        fail   never pass
 test-arm64-arm64-libvirt-xsm 13 saverestore-support-check    fail   never pass
 test-amd64-amd64-libvirt-vhd 11 migrate-support-check        fail   never pass
 test-arm64-arm64-libvirt-qcow2 11 migrate-support-check        fail never pass
 test-arm64-arm64-libvirt-qcow2 12 saverestore-support-check    fail never pass
 test-armhf-armhf-libvirt     12 migrate-support-check        fail   never pass
 test-armhf-armhf-libvirt-xsm 12 migrate-support-check        fail   never pass
 test-armhf-armhf-libvirt-raw 11 migrate-support-check        fail   never pass

version targeted for testing:
 libvirt              2453501fc82d3b247affb6c9054dc65bf2f669b3
baseline version:
 libvirt              a495e3f9eabcfcea3d80c5c04effa371e751541c

Last test of basis   109736  2017-05-25 04:20:08 Z    1 days
Testing same since   109759  2017-05-26 04:25:53 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Claudio André <claudioandre.br@xxxxxxxxx>
  John Ferlan <jferlan@xxxxxxxxxx>
  Michal Privoznik <mprivozn@xxxxxxxxxx>
  Peter Krempa <pkrempa@xxxxxxxxxx>

jobs:
 build-amd64-xsm                                              pass    
 build-arm64-xsm                                              pass    
 build-armhf-xsm                                              pass    
 build-i386-xsm                                               pass    
 build-amd64                                                  pass    
 build-arm64                                                  pass    
 build-armhf                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-arm64-libvirt                                          pass    
 build-armhf-libvirt                                          pass    
 build-i386-libvirt                                           pass    
 build-amd64-pvops                                            pass    
 build-arm64-pvops                                            pass    
 build-armhf-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm           pass    
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm            pass    
 test-amd64-amd64-libvirt-xsm                                 pass    
 test-arm64-arm64-libvirt-xsm                                 pass    
 test-armhf-armhf-libvirt-xsm                                 pass    
 test-amd64-i386-libvirt-xsm                                  pass    
 test-amd64-amd64-libvirt                                     pass    
 test-arm64-arm64-libvirt                                     fail    
 test-armhf-armhf-libvirt                                     pass    
 test-amd64-i386-libvirt                                      pass    
 test-amd64-amd64-libvirt-pair                                pass    
 test-amd64-i386-libvirt-pair                                 pass    
 test-arm64-arm64-libvirt-qcow2                               pass    
 test-armhf-armhf-libvirt-raw                                 pass    
 test-amd64-amd64-libvirt-vhd                                 pass    


------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images

Logs, config files, etc. are available at
    http://logs.test-lab.xenproject.org/osstest/logs

Explanation of these reports, and of osstest in general, is at
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master

Test harness code can be found at
    http://xenbits.xen.org/gitweb?p=osstest.git;a=summary


Not pushing.

------------------------------------------------------------
commit 2453501fc82d3b247affb6c9054dc65bf2f669b3
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Thu May 11 09:17:09 2017 -0400

    virsh: Track when create pkttyagent
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1374126
    
    Due to how the processing for authentication using polkit works, the
    virshConnect code must first "attempt" an virConnectOpenAuth and then
    check for a "special" return error code VIR_ERR_AUTH_UNAVAILABLE in
    order to attempt to "retry" the authentication after performing a creation
    of a pkttyagent to handle the challenge/response for the client.
    
    However, if pkttyagent creation is not possible for the authentication
    being attempted (such as perhaps a "qemu+ssh://someuser@localhost/system"),
    then the same failure pattern would be returned and another attempt to
    create a pkttyagent would be done. This would continue "forever" until
    someone forced quit (e.g. ctrl-c) from virsh as the 'authfail' was not
    incremented when creating the pkttyagent.
    
    So add a 'agentCreated' boolean to track if we've attempted to create the
    agent at least once and force a failure if that creation returned the same
    error pattern.
    
    This resolves a possible never ending loop and will generate an error:
    
    error: failed to connect to the hypervisor
    error: authentication unavailable: no polkit agent available to 
authenticate action 'org.libvirt.unix.manage'
    
    NB: If the authentication was for a sufficiently privileged client, such as
    qemu+ssh://root@localhost/system, then the remoteDispatchAuthList "allows"
    the authentication to use libvirt since @callerUid would be 0.

commit 0d3aff58e7ed190c97b40ee92f58cb0180cef6fe
Author: Peter Krempa <pkrempa@xxxxxxxxxx>
Date:   Thu May 25 13:09:36 2017 +0200

    qemu: Use correct variable in qemuDomainSetBlockIoTune
    
    'param' contains the correct element from 'params'.
    
    If the group name would not be the first parameter libvirtd would crash.
    
    Introduced in c53bd25b13.
    
    Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1455510

commit 1e988b23563a3a3d21d551b4f4d667f6e3d738f4
Author: Claudio André <claudioandre.br@xxxxxxxxx>
Date:   Thu May 25 02:19:45 2017 -0300

    CI: show the log in case of failure
    
    Disclose the content of the 'test-suite.log' file (if available) in
    case of failures inside Travis-CI. This is needed to understand what
    happened and to provide hints about the proper fix (if applicable).

commit 411713d440b695958a4fde177915055ad1519fc7
Author: Michal Privoznik <mprivozn@xxxxxxxxxx>
Date:   Thu May 18 09:58:32 2017 +0200

    virDomainDefCheckABIStabilityFlags: move memtune checks into a separate 
function
    
    The checks are scattered all over the place. Move them into a
    single function.
    
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel