Hello Frank, The issue is similar because application-apply fails. The following pods are not running on duplex and simplex environments : 13:41:23 [2019-04-22T18:41:23.912Z] Kube System Services :: Check pods status and kube-system services... | FAIL | 13:41:23 [2019-04-22T18:41:23.912Z] 'openstack libvirt-libvirt-default-fwx24 0/1 Init:0/1 0 4m58s 10.10.53.3 controller-0 <none> <none> 13:41:23 [2019-04-22T18:41:23.912Z] openstack libvirt-libvirt-default-j5bxk 0/1 Init:0/1 0 4m58s 10.10.53.4 controller-1 <none> <none> 13:41:23 [2019-04-22T18:41:23.912Z] openstack neutron-db-init-pmmg8 0/1 Init:0/1 0 4m42s <none> controller-0 <none> <none> 13:41:23 [2019-04-22T18:41:23.912Z] openstack neutron-db-sync-zc97h 0/1 Init:0/1 0 4m42s <none> controller-0 <none> <none> 13:41:23 [2019-04-22T18:41:23.912Z] openstack neutron-dhcp-agent-controller-0-a762cb46-wjk52 0/1 Init:0/1 0 4m43s 10.10.53.3 controller-0 <none> <none> 13:41:23 [2019-04-22T18:41:23.912Z] openstack neutron-dhcp-agent-controller-1-347ae4cb-2pmkx 0/1 Init:0/1 0 4m44s 10.10.53.4 controller-1 <none> <none> 13:41:23 [2019-04-22T18:41:23.912Z] openstack neutron-ks-endpoints-wcc74 0/3 Init:0/1 0 4m42s As you mentioned the root cause is not the same because we are not using bond interfaces, we are double checking to discard temporal issues with our network, if the issue happens again we will create a bug. Regards Maria G. From: Miller, Frank [mailto:Frank.Miller@windriver.com] Sent: Tuesday, April 23, 2019 8:12 AM To: Perez Ibarra, Maria G <maria.g.perez.ibarra@intel.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190421 Maria: For the AIO-Simplex and AIO-Duplex results you indicate the application-apply failure is due to 1825045 but that LP is associated with switch ports being down. Can you share why you think the failures seen in sanity here are equivalent to this LP? I'd like to know if this is a duplicate or we have a different failure that looks similar. Frank From: Perez Ibarra, Maria G [mailto:maria.g.perez.ibarra@intel.com] Sent: Monday, April 22, 2019 6:20 PM To: starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] [Containers] Sanity Test - ISO 20190421 Status of the Sanity Test for last CENGN ISO: bootimage.iso from 2019-APRIL-21 (link<http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190421T233001Z/http:/mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190421T233001Z/>) Status: YELLOW =========================================== Sanity Test is executed in a Containers - Bare Metal Environment AIO - Simplex Setup Manual [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 49 TCs [FAIL] Sanity Platform 07 TCs [FAIL] TOTAL: 57 TCS [Fail : 57] AIO - Duplex Setup Manual [PASS] Provisioning 01 TCs [FAIL] Sanity OpenStack 52 TCs [FAIL] Sanity Platform 05 TCs [FAIL] TOTAL: 58 TCS [Fail : 58 TCs] Standard - Local Storage (2+2) Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 05 TCs [PASS] TOTAL: 57 TCS Standard - Dedicated Storage (2+2+2) Setup Manual [PASS] Provisioning 01 TCs [PASS] Sanity OpenStack 52 TCs [PASS] Sanity Platform 05 TCs [PASS] TOTAL: 57 TCS - application-apply stx-openstack failed due to neutron pods failure - high ovs-dpdk cpu usage : https://bugs.launchpad.net/starlingx/+bug/1825045 - About virtual results we don't have results yet due to we working on integrate ceph suite For more detail of the tests: https://wiki.openstack.org/wiki/StarlingX/Test/SanityTests#Sanity-OpenStack Regards Maria G.