Comment 5 for bug 1648501

Is there a possible valid scenario for using both imageRef and block_device_mapping_v2 together? I have tested with using boot from volume (block_device_mapping source:volume) and the image metadata is still added to the server. Should the behavior of the API be that imageRef and block_device_mapping_v2 are mutually exclusive? and if so should the behavior be to ignore the value provided in imageRef or to return a 400 bad request as the CLI client?