Bug 677350 - Delete Pool Warning message is same as Delete User Warning message
Summary: Delete Pool Warning message is same as Delete User Warning message
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 0.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: alpha
Assignee: Tomas Sedovic
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks: ce-beta
TreeView+ depends on / blocked
 
Reported: 2011-02-14 13:11 UTC by Shveta
Modified: 2012-01-26 12:27 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)
delete_pool (117.15 KB, image/png)
2011-02-14 13:11 UTC, Shveta 		no flags Details
View All

Description Shveta 2011-02-14 13:11:26 UTC 
Created attachment 478622 [details]
delete_pool

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.Login 
2. Create a pool
3. delete Pool , 

Warning message says :"Are you sure you want to delete this user?"
  
Actual results:


Expected results:


Additional info: Screen shot attached.
Comment 1 wes hayutin 2011-03-11 16:59:10 UTC 
adding to the ce-beta blocking tracker
Comment 2 Tomas Sedovic 2011-03-11 17:15:46 UTC 
Posted a fix to the mailing list:

https://fedorahosted.org/pipermail/aeolus-devel/2011-March/000591.html
Comment 3 Tomas Sedovic 2011-04-04 13:56:14 UTC 
Fixed in next. Commit: 0bdb95d9e077308c3adbefb24de7a9b7c203c9a6
Comment 4 Shveta 2011-04-05 10:33:32 UTC 
verified
Comment 5 wes hayutin 2011-08-01 20:02:05 UTC 
release pending...
Comment 6 wes hayutin 2011-08-01 20:02:19 UTC 
release pending 3
Comment 7 wes hayutin 2011-08-01 20:02:22 UTC 
release pending...
Comment 8 wes hayutin 2011-08-01 20:02:34 UTC 
release pending.. 2
Comment 10 wes hayutin 2011-12-08 14:04:31 UTC 
closing out old bugs
Comment 11 wes hayutin 2011-12-08 14:16:18 UTC 
perm close
Note You need to log in before you can comment on or make changes to this bug.