Bug 118708 - History not showing "Expired"
Summary: History not showing "Expired"
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise CMS
Classification: Retired
Component: APLAWS (Show other bugs)
(Show other bugs)
Version: nightly
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: ccm-bugs-list
QA Contact: Daniel Berrange
URL: http://aplaws-ws3.ccm-demo.redhat.de/...
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-03-19 10:32 UTC by James Kearns
Modified: 2010-09-03 14:32 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-09-03 14:32:51 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 James Kearns 2004-03-19 10:32:03 UTC
Description of problem:
The History tab shows when an item is "Published Deployed" but does 
not capture the opposite event, when the item expires.

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


How reproducible:
Always

Steps to Reproduce:
1. Publish an item using a lifecycle which will expire.
2. For example item "VENUS", using lifecycle "Deploy now , Expire in 
1 hour and 20 minutes"
3.
  
Actual results:
History records "Published Deployed" but no record of it unpublishing.

Expected results:
History records an additional event 1 hour and 20 minutes later when 
the item expires.

Additional info:


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