Based on the ML message, waiting for a volume to transit into 'in-use' state does not guarantee the volume can actually be detached immediately ("..Which means that the detach_volume is called before attach_volume functions actually ends and potentially update the connection_info field in the database....").
While this is a valid issue with unclear reporting of a volume state by Nova, this is not a blocker for us in 6.1 as this is only triggered by 'synthetic' tests.
Based on the ML message, waiting for a volume to transit into 'in-use' state does not guarantee the volume can actually be detached immediately ("..Which means that the detach_volume is called before attach_volume functions actually ends and potentially update the connection_info field in the database....").
While this is a valid issue with unclear reporting of a volume state by Nova, this is not a blocker for us in 6.1 as this is only triggered by 'synthetic' tests.