Comment 12 for bug 1970645

Hi Alexandru, thanks for providing the information here.
I was testing the master build 20220518 on an AIO-SX virtual environment and unfortunately could not reproduce the issue anymore :(

Tried several lock/unlock operations followed by stx-openstack application manual applies. During my tests all the apply operations worked and the only issue I faced was the one I reported here: https://bugs.launchpad.net/starlingx/+bug/1974221
That's just a corner case error message issue though.

Not sure if we should wait for a sanity run after https://bugs.launchpad.net/starlingx/+bug/1973888 is fixed to re-check if the stx-openstack is still reproducible.
Or maybe you could please provide me more information about your test scenario on the virtual environment. I saw you were using a DX and had at least one instance running that was probably migrated during the lock/unlock (it was rebooting). My virtual environment is shorter in processor resources so I did not bring any instance up before locking/unlocking...