Description of problem: $subject, this is an odd little corner case but if an admin resets the state of an attached volume to available there are no checks within n-api stopping a user from attaching the volume to another instance, regardless of the original bdm record. Version-Release number of selected component (if applicable): OSP 17 How reproducible: Always Steps to Reproduce: 1. Attach a volume to an instance. 2. Reset the state of the volume to available. 3. Attach the volume to another instance. Actual results: The volume is attached to both instances in Nova but a single instance in Cinder. Expected results: The second request to attach a volume should be rejected by Nova until the attachment is removed. Additional info:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2022:6543