Bug 797304 - after delete outline provider image, image doesn't disappear
Summary: after delete outline provider image, image doesn't disappear
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
Assignee: Matt Wagner
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-24 21:03 UTC by Dave Johnson
Modified: 2014-08-17 22:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-01 16:33:49 UTC

Attachments (Terms of Use)
screenshot (104.35 KB, image/png)
2012-02-24 21:03 UTC, Dave Johnson 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Dave Johnson 2012-02-24 21:03:39 UTC 
Created attachment 565676 [details]
screenshot

Description of problem:
==================================
After pushing a component outline to two providers, I decided to delete one of the provider images through the ui.  I noticed that the provider image is still listed on the page, even after a refresh.


Version-Release number of selected component (if applicable):
================================================================
aeolus-conductor-0.8.0-35.el6.noarch
Comment 1 Matt Wagner 2012-02-28 21:57:26 UTC 
I'm unable to reproduce this... I built and pushed an image to two providers (EC2 and mock), and both were deleted as soon as I pressed the 'X'.

The code is fairly simple -- it finds a provider image with a UUID matching the one shown, and, if it finds it, it calls delete! on it and returns the success flash that was shown.

I'd be interested to see if this is still happening, and if so, if you can help me set up a reproduceable case.
Comment 2 Dave Johnson 2012-03-01 16:33:49 UTC 
I am not seeing this now, dunno, if it re-appears we can reopen this... closing as worksforme.
Note You need to log in before you can comment on or make changes to this bug.