)]}'
{"api-ref/source/v2/volumes-v2-volumes-actions.inc":[{"author":{"_account_id":9555,"name":"Matthew Booth","email":"mbooth@redhat.com","username":"MatthewBooth"},"change_message_id":"152f39a4e74fb95a9d370907d029a765271ece22","unresolved":false,"context_lines":[{"line_number":340,"context_line":"Change the volume type of existing volume, Cinder may migrate the volume to"},{"line_number":341,"context_line":"proper volume host according to the new volume type."},{"line_number":342,"context_line":""},{"line_number":343,"context_line":"Retyping an *in-use* volume from a multiattach-capable type to a"},{"line_number":344,"context_line":"non-multiattach-capable type, or vice-versa, is not supported. It is generally"},{"line_number":345,"context_line":"not recommended to retype an *in-use* multiattach volume if that volume has"},{"line_number":346,"context_line":"more than one active read/write attachment."},{"line_number":347,"context_line":""}],"source_content_type":"text/x-c++src","patch_set":1,"id":"5f93b717_02bb11e2","line":344,"range":{"start_line":343,"start_character":0,"end_line":344,"end_character":61},"updated":"2018-01-26 09:25:16.000000000","message":"I wondered about this. From the POV of Nova\u0027s libvirt driver, the only issue is if the source has multiple attachments. Incidentally this is regardless of their permissions, although multiple read-write attachments will also result in data corruption.\n\nSo if we\u0027re going multi-capable to non-multi-capable, that\u0027s fine as long as there is only one connection. If the retype operation locks the volume to prevent further attachments *before* calling Nova we\u0027re good.\n\nGoing non-multi-capable to multi-capable is presumably fine, as I assume we can\u0027t have multiple attachments until after the retype completes anyway.","commit_id":"2e1d31a44aee148fbfbcf14ccb8994a85ac3a952"},{"author":{"_account_id":9555,"name":"Matthew Booth","email":"mbooth@redhat.com","username":"MatthewBooth"},"change_message_id":"152f39a4e74fb95a9d370907d029a765271ece22","unresolved":false,"context_lines":[{"line_number":341,"context_line":"proper volume host according to the new volume type."},{"line_number":342,"context_line":""},{"line_number":343,"context_line":"Retyping an *in-use* volume from a multiattach-capable type to a"},{"line_number":344,"context_line":"non-multiattach-capable type, or vice-versa, is not supported. It is generally"},{"line_number":345,"context_line":"not recommended to retype an *in-use* multiattach volume if that volume has"},{"line_number":346,"context_line":"more than one active read/write attachment."},{"line_number":347,"context_line":""},{"line_number":348,"context_line":"Policy defaults enable only users with the administrative role or the owner of"}],"source_content_type":"text/x-c++src","patch_set":1,"id":"5f93b717_625455cb","line":345,"range":{"start_line":344,"start_character":63,"end_line":345,"end_character":15},"updated":"2018-01-26 09:25:16.000000000","message":"I might have gone stronger here: if the attachments are Nova/libvirt it definitely will not work.","commit_id":"2e1d31a44aee148fbfbcf14ccb8994a85ac3a952"}]}