Comment 1 for bug 1511061

1. I agree, the image deletion operation should be atomic.

2. Image data left behind means there is a potential risk of filling up storage quota and resulting into a DoS; be mindful that it's a denial of service but NOT a exploit as it is dependent on the operators' failure scenarios of g-api <-> reg communication.

3. The original description has information related to failure scenarios for only v1. So, a check is needed for the v2 as applicable.