Volume attachment API shouldn't be used to attach a volume into a server in our tests, unless we want to test the volume attach API specifically.
The reason is that we should be using the compute API to attach volumes and the volume attachment API was designed for debug purposes:
This command will only create a volume attachment in the Volume service. It will not invoke the
necessary Compute service actions to actually attach the volume to the server at the hypervisor level. As a result, it should typically
only be used for troubleshooting issues with an existing server in combination with other tooling. For all other use cases, the 'server
volume add' command should be preferred.
Volume attachment API shouldn't be used to attach a volume into a server in our tests, unless we want to test the volume attach API specifically.
The reason is that we should be using the compute API to attach volumes and the volume attachment API was designed for debug purposes: