Bug 798587

Summary:	rhc-list-stale treats new app as stale when local date fell behind
Product:	OKD	Reporter:	Linqing Lu <lilu>
Component:	Containers	Assignee:	Mrunal Patel <mpatel>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	1.x	CC:	gshipley, jizhao
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-03-02 21:56:41 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Linqing Lu 2012-02-29 10:39:05 UTC

Description of problem:
because rhc-list-stale bases on latest commit date of the app repo, so it will affected by the accuracy of user's local date

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

How reproducible:


Steps to Reproduce:
1. set local date as 2011-1-1
2. create an app and make a commit
3. check rhc-list-stale in devenv
  
Actual results:
the newly created app is listed as stale

Expected results:
the newly created app should not be listed as stale

Additional info:

Comment 1 jizhao 2012-03-01 03:31:18 UTC

Verified on devenv-stage_139.