Bug 761177

Summary: disabled providers still allow a new image to be built/push
Product: [Retired] CloudForms Cloud Engine Reporter: Dave Johnson <dajohnso>
Component: aeolus-conductorAssignee: Jan Provaznik <jprovazn>
Status: CLOSED ERRATA QA Contact: wes hayutin <whayutin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, deltacloud-maint, jprovazn, ssachdev
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-15 21:22:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Dave Johnson 2011-12-07 20:18:51 UTC 
Description of problem:
==============================
I noticed that when a provider does not have a provider account and you create a image through the web ui, only providers that have accounts are displayed with the capability of being built/pushed.

Later in the day however, I noticed that when I disabled a provider account and then proceeded to create a new image, the disabled provider still has the ability to build/push images.  

Just like when there was not a provider account, disabled providers should probably? not be displayed with the capability to build/push.
Comment 1 wes hayutin 2012-01-10 17:09:58 UTC 
adding to ce-sprint-next
Comment 2 wes hayutin 2012-01-10 17:12:05 UTC 
adding to ce-sprint-next
Comment 3 Jan Provaznik 2012-01-11 14:35:12 UTC 
This was fixed together with https://bugzilla.redhat.com/show_bug.cgi?id=769635
Comment 4 Dave Johnson 2012-01-11 22:24:07 UTC 
good to go with:

[root@qeblade29 ~]# rpm -qa | egrep 'aeolus|deltacloud' | sort
aeolus-all-0.8.0-5.el6.noarch
aeolus-conductor-0.8.0-5.el6.noarch
aeolus-conductor-daemons-0.8.0-5.el6.noarch
aeolus-conductor-doc-0.8.0-5.el6.noarch
aeolus-configure-2.5.0-3.el6.noarch
deltacloud-core-0.5.0-0.rc1.el6.noarch
deltacloud-core-ec2-0.5.0-0.rc1.el6.noarch
deltacloud-core-rhevm-0.5.0-0.rc1.el6.noarch
deltacloud-core-vsphere-0.5.0-0.rc1.el6.noarch
rubygem-aeolus-cli-0.3.0-3.el6.noarch
rubygem-aeolus-image-0.3.0-2.el6.noarch
rubygem-deltacloud-client-0.4.0-3.el6.noarch
Comment 5 wes hayutin 2012-01-12 16:27:01 UTC 
removing verified on-qa from tracker
Comment 7 errata-xmlrpc 2012-05-15 21:22:38 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2012-0583.html