Bug 797130

Description of problem:
Aeolus CLI allows to push images multiple times for the same provider account.  Aeolus should allow image push only once for a provider account and should not allow to push second time onwards.

However creates new AMI id for the consecutive pushes

Version-Release number of selected component (if applicable):
[root@bigisis ~]# rpm -qa | grep aeolus
aeolus-conductor-0.8.0-35.el6.noarch
rubygem-aeolus-cli-0.3.0-10.el6.noarch
aeolus-conductor-doc-0.8.0-35.el6.noarch
rubygem-aeolus-image-0.3.0-9.el6.noarch
aeolus-all-0.8.0-35.el6.noarch
aeolus-conductor-daemons-0.8.0-35.el6.noarch
aeolus-configure-2.5.0-15.el6.noarch
[root@bigisis ~]# 


How reproducible:


Steps to Reproduce:
1. Add a provider a/c in any region for EC2 (say us-east-1) from conductor
2. Build a template and push the template to above created provider a/c
3. Now once the image push is successful, try to push the same image to the same provider a/c again
  
Actual results:
Push is successful for multiple times and creates a new AMI id in EC2 for each push

Expected results:
Conductor should allow one push per provider a/c and should validate for the consecutive pushes

Additional info: