In a setup where the glance-api node handles nova/service interactions and end-user requests, if show_multiple_locations=false (the default) and show_direct_url=false (the default) and the set_image_location policy is admin only (default since Newton); then glance will be able to interact with the vmware datastore correctly, both for snapshots and regular end-user image stuff, and the store is not exposed to this bug.
For the non-default configuration case, I looked at the patch from Mike and IIUC, it verifies that the location URL being added contains the image_id of the image being updated. This patch will work for the VMware driver and no special handling needs to be done as in the case of RBD driver.
Just to be clear, let me rephrase my update :-
In a setup where the glance-api node handles nova/service interactions and end-user requests, if show_multiple_ locations= false (the default) and show_direct_ url=false (the default) and the set_image_location policy is admin only (default since Newton); then glance will be able to interact with the vmware datastore correctly, both for snapshots and regular end-user image stuff, and the store is not exposed to this bug.
For the non-default configuration case, I looked at the patch from Mike and IIUC, it verifies that the location URL being added contains the image_id of the image being updated. This patch will work for the VMware driver and no special handling needs to be done as in the case of RBD driver.