Comment 3 for bug 1933610

I hit this bug too in Rocky release. when using an existing image-created volume to create an instance and some exception occured in nova/virt/libvirt/driver.py `_create_domain_and_network` like libvirt Internal exception(ram not enough) and it rescheduled and hit the bug.
I read the nova code, found that in nova/compute/api.py `_check_attach_and_reserve_volume` create the attachement_id, how about to resotre the code to using old-style volume reserve to solve the problem?