I am also getting hit by this bug, using OSA 18.1.4 Rocky.
With my deployment, I am simply re-running playbooks on a fully working system.
Taking what @Dmitriy Rabotjagov said about need_online_data_migrations Ansible Fact; I attempted to set all of mine to False, and re-running playbook os-cinder-install.yml failed in the same spot. I didn't go as far as to comment out the TASK [Perform online data migrations] - but I suppose that may be another way to bypass this when using OSA.
Unless there is a workaround, we definitely seem to be stuck.
I am also getting hit by this bug, using OSA 18.1.4 Rocky.
With my deployment, I am simply re-running playbooks on a fully working system.
Taking what @Dmitriy Rabotjagov said about need_online_ data_migrations Ansible Fact; I attempted to set all of mine to False, and re-running playbook os-cinder- install. yml failed in the same spot. I didn't go as far as to comment out the TASK [Perform online data migrations] - but I suppose that may be another way to bypass this when using OSA.
Unless there is a workaround, we definitely seem to be stuck.