The problem was not seen on runs for 9.2 snapshots #771 and #776 so far.
And the only reasonable way to implement solution with 'no-kvmapf' option seems to be to add reconfiguration actions on the environment right after the deployment. That can be done within CI that runs tempest suites.
The problem was not seen on runs for 9.2 snapshots #771 and #776 so far.
And the only reasonable way to implement solution with 'no-kvmapf' option seems to be to add reconfiguration actions on the environment right after the deployment. That can be done within CI that runs tempest suites.