Actually, the operation fails only when one tries to manage a volume by its volume-name, e.g.:
cinder manage --id-type volume-name lucios-sandbox@sf#sf UUID-24df321d-8bfa-495e-bcd8-dc517e8ae528
The same happens when omitting --id-type parameter, as its default value is volume-name.
If source-id is specified instead, the manage operation succeeds, e.g.:
cinder manage --id-type source-id lucios-sancbox@sf#sf 168
Actually, the operation fails only when one tries to manage a volume by its volume-name, e.g.:
cinder manage --id-type volume-name lucios- sandbox@ sf#sf UUID-24df321d- 8bfa-495e- bcd8-dc517e8ae5 28
The same happens when omitting --id-type parameter, as its default value is volume-name.
If source-id is specified instead, the manage operation succeeds, e.g.:
cinder manage --id-type source-id lucios- sancbox@ sf#sf 168