Bug 118708 – History not showing "Expired"

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 118708 - History not showing "Expired"

Summary:	History not showing "Expired"

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Enterprise CMS
Classification:	Retired
Component:	APLAWS (Show other bugs)
Sub Component:
Version:	nightly
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	ccm-bugs-list
QA Contact:	Daniel Berrange
Docs Contact:

URL:	http://aplaws-ws3.ccm-demo.redhat.de/...
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-03-19 05:32 EST by James Kearns
Modified:	2010-09-03 10:32 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2010-09-03 10:32:51 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description James Kearns 2004-03-19 05:32:03 EST

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.