Bug 1255943

Summary:	Jenkins periodical jobs don't execute
Product:	OpenShift Online	Reporter:	Rares Vernica <rvernica>
Component:	Image	Assignee:	John W. Lamb <jolamb>
Status:	CLOSED NOTABUG	QA Contact:	Wenjing Zheng <wzheng>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.x	CC:	jokerman, libra-bugs, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-13 15:49:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Rares Vernica 2015-08-22 05:14:10 UTC

Description of problem:

I have a gear running Jenkins in OpenShift I setup a job and enabled periodic execution to "@weekly". It has been almost two weeks and the job did not execute.

I think when not it use, the gear goes into a "stand-by" mode. I access the Jenkins UI daily and the first access every day returns a connection failed message (like the server is down). Upon refresh everything works fine. I think the gear goes into "stand-by" and then recovers when accessed.


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

Jenkins ver. 1.609.1

Comment 1 John W. Lamb 2015-10-13 15:49:12 UTC

This is a result of gear idling: https://developers.openshift.com/en/managing-idling.html

After 48 hours with no external requests, OpenShift "idles" your gears, essentially shutting it down until it's woken up again by an external request (i.e. a HTTP GET). This affects Cron carts as well, so weekly jobs run from an app that sees traffic less than once every 48 hours will tend not to run.

This can be avoided by making sure your app is browsed at least once every two days, or upgrading to a premium account: http://stackoverflow.com/questions/25379410/ping-service-to-stop-openshift-application-from-idle