A new flock build is in progress. ________________________________ From: Khalil, Ghada <Ghada.Khalil@windriver.com> Sent: August 29, 2022 10:29 AM To: Cervi, Thales Elero <ThalesElero.Cervi@windriver.com>; starlingx-discuss@lists.starlingx.io <starlingx-discuss@lists.starlingx.io>; Panech, Davlet <Davlet.Panech@windriver.com>; Cooke, Rob <Rob.Cooke@windriver.com> Subject: RE: Requesting r/stx.7.0 new flock build @Panech, Davlet<mailto:Davlet.Panech@windriver.com> can you please trigger the stx.7.0 build since Scott is away this week? Please respond to this email when the build is ready. Thanks. @Cooke, Rob<mailto:Rob.Cooke@windriver.com> please arrange for stx.7.0 sanity w/ openstack. Thanks, Ghada From: Cervi, Thales Elero <ThalesElero.Cervi@windriver.com> Sent: Monday, August 29, 2022 10:14 AM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] Requesting r/stx.7.0 new flock build Hi StarlingX Community, As part of the release 7.0 sanity efforts, the initial StarlingX + StarlingX Openstack executions reproduced that old bug [1] reported this year that was previously marking the sanity as RED. The team already proposed the fix for it [2] and it was merged into both main and r/stx.7.0 branches. I know we are currently building this branch on-demand, so am kindly requesting a new build (whenever it is possible) to have this fix officially in place for our next Sanity rounds. [1] https://bugs.launchpad.net/starlingx/+bug/1970645<https://urldefense.com/v3/__https:/bugs.launchpad.net/starlingx/*bug/1970645__;Kw!!AjveYdw8EvQ!b0I33Cu-bKyQEk2wJ9ke6Y7Tuw3_OL2f9PPs-DvVV0qLERe3CPlWWxb445Mb_Sp9ONY3TmNONXzpOiOYyOHU8y54bNTKangKGhM$> [2] https://review.opendev.org/q/topic:bug%252F1970645<https://urldefense.com/v3/__https:/review.opendev.org/q/topic:bug*252F1970645__;JQ!!AjveYdw8EvQ!b0I33Cu-bKyQEk2wJ9ke6Y7Tuw3_OL2f9PPs-DvVV0qLERe3CPlWWxb445Mb_Sp9ONY3TmNONXzpOiOYyOHU8y54bNTKN53p55M$> Thanks and best regards. Thales