Dear colleagues, I have recently moved my environment over to openstack-ansible 16.0.8 and when I run tempest testing as the last step of the deployment it is failing with the following errors logged in daemon.log on the compute server.
Before I use up more time looking into the details of libvirt, does anyone have a quick answer to why this might be happening? (Please note that the self same environment was working with Ocata.) Mar 22 16:41:07 compute1 libvirtd[2954]: 2018-03-22 16:41:07.897+0000: 3094: error : virProcessKillPainfully:401 : Failed to terminate process 3798 with SIGKILL: Device or resource busy Mar 22 16:41:22 compute1 libvirtd[2954]: 2018-03-22 16:41:22.930+0000: 3095: error : virProcessKillPainfully:401 : Failed to terminate process 3798 with SIGKILL: Device or resource busy Mar 22 16:41:37 compute1 libvirtd[2954]: 2018-03-22 16:41:37.964+0000: 3092: error : virProcessKillPainfully:401 : Failed to terminate process 3798 with SIGKILL: Device or resource busy Mar 22 16:41:37 compute1 libvirtd[2954]: 2018-03-22 16:41:37.980+0000: 3101: warning : qemuGetProcessInfo:1436 : cannot parse process status data Mar 22 16:41:37 compute1 libvirtd[2954]: 2018-03-22 16:41:37.980+0000: 3101: error : virProcessGetAffinity:506 : cannot get CPU affinity of process 3828: No such process Mar 22 16:42:37 compute1 libvirtd[2954]: 2018-03-22 16:42:37.528+0000: 3093: warning : qemuGetProcessInfo:1436 : cannot parse process status data Mar 22 16:42:37 compute1 libvirtd[2954]: 2018-03-22 16:42:37.528+0000: 3093: error : virProcessGetAffinity:506 : cannot get CPU affinity of process 3828: No such process Mar 22 16:43:38 compute1 libvirtd[2954]: 2018-03-22 16:43:38.744+0000: 3094: warning : qemuGetProcessInfo:1436 : cannot parse process status data Mar 22 16:43:38 compute1 libvirtd[2954]: 2018-03-22 16:43:38.744+0000: 3094: error : virProcessGetAffinity:506 : cannot get CPU affinity of process 3828: No such process Mar 22 16:44:38 compute1 libvirtd[2954]: 2018-03-22 16:44:38.281+0000: 3092: warning : qemuGetProcessInfo:1436 : cannot parse process status data Mar 22 16:44:38 compute1 libvirtd[2954]: 2018-03-22 16:44:38.281+0000: 3092: error : virProcessGetAffinity:506 : cannot get CPU affinity of process 3828: No such process Mar 22 16:45:38 compute1 libvirtd[2954]: 2018-03-22 16:45:38.243+0000: 3100: warning : qemuGetProcessInfo:1436 : cannot parse process status data Mar 22 16:45:38 compute1 libvirtd[2954]: 2018-03-22 16:45:38.243+0000: 3100: error : virProcessGetAffinity:506 : cannot get CPU affinity of process 3828: No such process Mar 22 16:46:39 compute1 libvirtd[2954]: 2018-03-22 16:46:39.221+0000: 3095: warning : qemuGetProcessInfo:1436 : cannot parse process status data Mar 22 16:46:39 compute1 libvirtd[2954]: 2018-03-22 16:46:39.221+0000: 3095: error : virProcessGetAffinity:506 : cannot get CPU affinity of process 3828: No such process Mar 22 16:46:57 compute1 libvirtd[2954]: 2018-03-22 16:46:57.604+0000: 3096: error : virProcessKillPainfully:401 : Failed to terminate process 3798 with SIGKILL: Device or resource busy Mar 22 16:47:12 compute1 libvirtd[2954]: 2018-03-22 16:47:12.648+0000: 3093: error : virProcessKillPainfully:401 : Failed to terminate process 3798 with SIGKILL: Device or resource busy Kind regards, Lawrence __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
