·         Test strategy review (Ian)

·         [brucej] We have not had a passing Sanity for some time. There are numerous issues.  Many thanks to the folks debugging them.  Can we / should we take additional steps to get back to passing Sanity?

§  If a team needs a exception to this short term policy, feel free to raise the issue on the mailing list.  Release team can grant approval.

·         (Ghada) Summary of sanity/critical issues:

§  https://bugs.launchpad.net/starlingx/+bug/1827521

§  https://bugs.launchpad.net/starlingx/+bug/1828899

§  https://bugs.launchpad.net/starlingx/+bug/1828059

§  A ceph upstream fix was identified and merged in starlingx on May 14. PR: https://github.com/starlingx-staging/stx-ceph/pull/30

§  The following two LPs are also suspected to be the same root-cause:  (needs review/retest):

·         https://bugs.launchpad.net/starlingx/+bug/1828729

·         https://bugs.launchpad.net/starlingx/+bug/1828863

§    https://bugs.launchpad.net/starlingx/+bug/1828896

§  Review is in progress. Workaround documented in the LP.

§  controller in degraded state: https://bugs.launchpad.net/starlingx/+bug/1828877

·         Zhipeng is working on fix

§  nodes failing after unlock: https://bugs.launchpad.net/starlingx/+bug/1828903

·         May be an issue with when the stx build was done by the reporter. Reporter needs to retest.

§  A recent commit back-ported to nova stein is causing issues with VM launches

·         nova bug opened by Gerry Kopec: https://bugs.launchpad.net/nova/+bug/1829062

·         The issue was also reported by the test team via: https://bugs.launchpad.net/starlingx/+bug/1829060

o    This stx bug will be used to point the stx docker image builds to the stx nova fork (since it has an older snapshot of the stein branch).

o    The plan is for the stx nova fork to be rebased at a regular cadence (frequency?). The stx.disto.openstack team will need to monitor the nova bug above to ensure a fix is available before the next rebase of the fork.

·         [brucej] The distro.openstack weekly call has not had many participants.  Is there a conflict or some other issue?   Likely due to vacations.