Hi everyone,
Please find below the minutes from this week’s StarlingX Test Status Call:
Minutes for 01/30/2024
o
None
§
Sanity in STX. Since Intel stopped doing the sanity in STX, Wind River picked up this responsibility. At the time, Wind River was not able to replicate the Intel environments to execute the Sanity suite.
§
In order to keep sanity moving, the decision was made to execute the Wind River sanity suite against an internal server running the latest version of STX. We have been doing this for a while now
o
Sanity on STX 9.0 for SX and DX.
§
Sanity not executed this week due to lab availability
§
Last sanity email sent on January 16: https://lists.starlingx.io/archives/list/starlingx-discuss@lists.starlingx.io/thread/PVAG4OFFRZNB2FZHOG3G7W7OOTWENCNQ/
·
Status: Green for SX Red for DX
·
Launchpad exists for the DX failure, https://bugs.launchpad.net/starlingx/+bug/2043506 - AIO-DX: After host-swact, standby oam-services are in disabled-failed status
- FIXED
o
Sanity on STX 9.0 plus Openstack
§
Sanity was executed this week and as of the writing of these minutes the results are being analyzed, email to be sent once analysis is complete.
·
Status: Red
o
Tests failed due to:
§
https://bugs.launchpad.net/starlingx/+bug/2030883 - DX VM evacuation failed after reboot active controller
§
https://bugs.launchpad.net/starlingx/+bug/2043506 - AIO-DX: After host-swact, standby oam-services are in disabled-failed status
o
Feature testing is tracked in the following google sheet:
Thanks,
Rob