)]}'
{"cinder/volume/manager.py":[{"author":{"_account_id":9535,"name":"Gorka Eguileor","email":"geguileo@redhat.com","username":"Gorka"},"change_message_id":"05729ec70c2a81dd698a8393274a2a25be52aa33","unresolved":false,"context_lines":[{"line_number":173,"context_line":""},{"line_number":174,"context_line":"    RPC_API_VERSION \u003d volume_rpcapi.VolumeAPI.RPC_API_VERSION"},{"line_number":175,"context_line":""},{"line_number":176,"context_line":"    target \u003d messaging.Target(version\u003d\u00273.0\u0027)"},{"line_number":177,"context_line":""},{"line_number":178,"context_line":"    # On cloning a volume, we shouldn\u0027t copy volume_type, consistencygroup"},{"line_number":179,"context_line":"    # and volume_attachment, because the db sets that according to [field]_id,"}],"source_content_type":"text/x-python","patch_set":4,"id":"1a95cdbc_7994e336","line":176,"updated":"2016-10-05 08:44:44.000000000","message":"-1: This is wrong, and has created problems for me in my A/A patches.  It should be match the RPC version, which in this case is 3.1, and moreover, we don\u0027t want to change this manually every time we change the RPC, so it should be:\n\n target \u003d messaging.Target(version\u003dRPC_API_VERSION)","commit_id":"0b241554fe0a6430708867036ca79b6c377e4032"}]}
