Comment 5 for bug 1501851

I saw that too, but I still can't reproduce:

$ nova boot --image 62b38431-b89c-404f-9ece-f4d7eb2a0aa4 --block-device source=image,dest=local,id=62b38431-b89c-404f-9ece-f4d7eb2a0aa4 --flavor m1.tiny foo
ERROR (BadRequest): Block Device Mapping is Invalid: Mapping image to local is not supported. (HTTP 400) (Request-ID: req-2f29d8e4-8be5-4f4f-8f7d-6cc94c2c437b)

$ nova boot --image 62b38431-b89c-404f-9ece-f4d7eb2a0aa4 --block-device source=image,dest=local,id=62b38431-b89c-404f-9ece-f4d7eb2a0aa4,bootindex=0 --flavor m1.tiny foo
ERROR (BadRequest): Block Device Mapping is Invalid: Boot sequence for the instance and image/block device mapping combination is not valid. (HTTP 400) (Request-ID: req-6b9712e9-07a6-4b10-9ff8-ddcbb46897a8)

I think you're saying that you saw a bdm of source=image,dest=local, and inferred the root cause? I might take a look and see if I can come up with another way this might have arisen.