Thanks for the results, Elio. As discussed in the networking meeting, the expected test results for the failed TCs should be updated to indicate a reboot is expected. So we can consider the pass rate of 100% :) Ghada From: Martinez Monroy, Elio [mailto:elio.martinez.monroy@intel.com] Sent: Wednesday, June 12, 2019 2:42 PM To: Khalil, Ghada; Winnicki, Chris Cc: Peters, Matt; Waheed, Numan; Cabrales, Ada Subject: OVS- Pmon Testing Results Hi guys, Sharing my results regarding OVS-Pmon OVS Pmon Results: * Testing Results STATUS # PASS 7 FAIL 4 BLOCKED 0 TOTAL 11 Overall pass rate: 63.63% [cid:image002.png@01D521CB.DBB7C830] * DISCLAIMER ABOUT FAILURES: This is the intended behavior of the system based on the current PMON configuration. The system cannot tolerate the restart of these processes. This is a limitation of using OVS-DPDK. * Executed test plan https://docs.google.com/document/d/15Pm0oEwE1CQIncu_rCRjewxMrgKHDDrciUF8wRBw... * Execution: OVS PMON integration is required for process state detection, alarming and recovery. The ovs-vswitchd processes need to be Monitored. We need to validate that the OVS PMON works according with the new architecture. The testing was executed on a 2+2 Bare Metal configuration, using 4th June ISO , following instructions from: https://review.opendev.org/#/c/648330/ https://review.opendev.org/#/c/648367/ * Summary o 11 Test cases with no option to restart or stop service (known limitation). The rest of the instructions without problems. o Final results can be reviewed at: https://docs.google.com/spreadsheets/d/15us6HWgcb0dmHHZe2SyOR_UI5BvVpoU8TCST... * Bugs o There is no bug related caused by this testing. * Suggestions: o Feature is healthy enough according with our testing. o This feature doesn't represent any blocker for 2.0 release. [cid:image001.png@01CF8BAC.3B4C5DD0] Martinez Monroy, Elio. QA Engineer.