[Starlingx-discuss] [ Test ] meeting notes - 03/31/2020
Liu, Yang (YOW)
yang.liu at windriver.com
Tue Mar 31 16:09:12 UTC 2020
Agenda/meeting notes are posted here:
https://etherpad.openstack.org/p/stx-test
Agenda for 03/31/2020
Attendees: Yang, Mihail, Nicolae, George, Cosmin, Sharath, Claudiu, Bruce, ChrisW, Wendy
1. Sanity Status:
· Sanity issues reported by WR:
* 1855474 - OpenStack pods were not recovered after force reboot active controller
* 1859645 - platform-integ-apps fail to apply initially due to could not find the requested resource (get configmaps)
* https://bugs.launchpad.net/starlingx/+bug/1863795 - "helm list" failed by network is unreachable after host-unlock
* https://bugs.launchpad.net/starlingx/+bug/1868567 - CMD application-delete failed by Timeout while waiting on RPC response
* https://bugs.launchpad.net/starlingx/+bug/1869739 - 250.001 controller Configuration is out-of-date alarm not cleared after system installation
· Sanity issues reported by Intel:
* Green
* Private registry used by Intel: some container images changed and not picked up in private registry - now resolved
* May look into adding ipv6 configs for the long term
2. stx4.0 testing
· Release plan:
* https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpbrEc17_yg/edit#gid=0
* Kata: intend to start early. target test complete by 05/08
* Rook: intend to start early. target test complete by 05/22
* Fault containerization: target test complete by 05/29
* Centos8: no server with TPM, mellanox cards; integrity may not be testable
* TSN support in kata container: target test complete by 05/29
* OpenStack clients and platform services: eng build will be available in a week. testing: 04-13 - 05-04
* OpenStack upversion:
§ automated and manual test update needed, may be time consuming
§ target 06-05
* Layered build is tested daily with issues being found and resolved
§ image did not build - fixed
§ 03-31 build still failed, but went further
· Targeted feature completion date: 06-08
* Risk: OpenStack upversion to Ussuris coming in late, and requires large amount of testing
· Targeted regression completion date: 06-15 (pushing out 1 week)
* Propose no openstack regression between 06-08 to 06-15
3. Unified santiy
* Intel will bring in robot sanity as is into pytest framework
* For feature test cases porting from robot framework in future, should look into organizing/porting by feature, and porting only the missing ones
* Need to look into external traffic to/from openstack vm via neutron router in future to enable neutron testing in Intel environment
4. Opens
· Servers/test environment setup within Nic's team:
* In progress - cabling, configuring ports, etc
* Will know more by end of week.
* Risk reduced compared to last week.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20200331/00c80c0e/attachment-0001.html>
More information about the Starlingx-discuss
mailing list