Bug 592414 - Need to process "Deleted" system logic in SDC
Summary: Need to process "Deleted" system logic in SDC
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: WebUI (Show other bugs)
(Show other bugs)
Version: unspecified
Hardware: All Linux
low
medium
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: 462714
TreeView+ depends on / blocked
 
Reported: 2010-05-14 19:52 UTC by Partha Aji
Modified: 2014-07-04 13:26 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-07-04 13:26:25 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Partha Aji 2010-05-14 19:52:03 UTC
Select a bunch of systems in SSM and delete them. What happens is they get queued for deletion but get actually deleted in an asynchronous process. Given that it takes about > 10 secs to delete a system if the user was deleting a 100 systems, it'd take around 1000 secs. At this stage some systems still be browsable through SDC even though they are technically "Deleted". We would need to change the SDC header to Hide the system and say "the following system has been deleted and you can't browse it"


Note You need to log in before you can comment on or make changes to this bug.