Bug 744710

Summary: Deleting a provider does not display any status message.
Product: [Retired] CloudForms Cloud Engine Reporter: Aziza Karol <akarol>
Component: aeolus-conductorAssignee: Jiri Tomasek <jtomasek>
Status: CLOSED ERRATA QA Contact: wes hayutin <whayutin>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, dajohnso, deltacloud-maint, dgao, 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 22:15:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
provider deletion none

Description Aziza Karol 2011-10-10 09:18:08 UTC 
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
I tried deleting a provider vsphere.
The deletion was successful, however there was no status message displayed whether the deletion was successful or not.


Expected results:
Status message should be displayed if provider is  deleted successfully.


Additional info:
[root@dell-pesc430-03 ~]# rpm -qa | grep aeolus
rubygem-aeolus-image-0.1.0-3.20111003170706git8f23238.fc15.noarch
rubygem-aeolus-cli-0.1.0-3.20111003133323git9451323.fc15.noarch
aeolus-conductor-0.5.0-0.20111007200330gite77b251.fc15.noarch
aeolus-conductor-daemons-0.5.0-0.20111007200330gite77b251.fc15.noarch
aeolus-conductor-doc-0.5.0-0.20111007200330gite77b251.fc15.noarch
aeolus-all-0.5.0-0.20111007200330gite77b251.fc15.noarch
aeolus-configure-2.2.0-1.20111007151942git26136f2.fc15.noarch
Comment 2 Jiri Tomasek 2011-10-14 08:39:44 UTC 
Fixed in commit 231bfa35554aabd26deb8f6cf98a30ae664aae4b
Comment 3 Aziza Karol 2011-10-17 06:32:38 UTC 
Provider successfully deleted message is displayed.

see attach screenshot.


verified on:
[root@gs-bl460cg1-01 ~]# rpm -qa | grep aeolus
aeolus-conductor-doc-0.5.0-0.20111014151901git7f70fb5.fc15.noarch
aeolus-all-0.5.0-0.20111014151901git7f70fb5.fc15.noarch
rubygem-aeolus-cli-0.1.0-3.20111003133323git9451323.fc15.noarch
aeolus-configure-2.2.0-1.20111007151942git26136f2.fc15.noarch
aeolus-conductor-0.5.0-0.20111014151901git7f70fb5.fc15.noarch
aeolus-conductor-daemons-0.5.0-0.20111014151901git7f70fb5.fc15.noarch
rubygem-aeolus-image-0.1.0-3.20111003170706git8f23238.fc15.noarch
Comment 4 Aziza Karol 2011-10-17 06:33:12 UTC 
Created attachment 528471 [details]
provider deletion
Comment 6 errata-xmlrpc 2012-05-15 22:15:08 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