You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 23, 2020. It is now read-only.
Multiple instances of the idler NOT idling/un-idling when expected were seen on January 7. The behavior is not being seen on January 8. Logging this issue to document the behavior.
Expected Behaviour
Current Behaviour
The idler was not able to un-idle when a new build pipeline was created. Also, the idler was triggered when a new build pipeline was created. This behavior was seen repeatedly and consistently on January 7.
Steps To Reproduce
Perform an environment reset in OpenShift.io
Verify in the OpenShift console that the Jenkins pod has successfully started
Wait anywhere from several minutes to several hours
Observe that despite no build pipelines being created, the Jenkins pod is not idled.
Create a new app
Observe that when the build pipeline is created, the Jenkins pod is idled
The text was updated successfully, but these errors were encountered:
The user account where this error is seen is provisioned on: starter-us-east-2
The booster used was Vert/X/REST HTTP
ldimaggi
changed the title
Idler intermittently stopping active build pipelines
Idler intermittently stopping active build pipelines on starter-us-east-2
Jan 8, 2019
We fixed #4739 issue on cluster 2 w.r.t to Idler. token was expired there. Can you please check if it's happening and if not then can you please close. Thanks
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue Overview
Multiple instances of the idler NOT idling/un-idling when expected were seen on January 7. The behavior is not being seen on January 8. Logging this issue to document the behavior.
Expected Behaviour
Current Behaviour
The idler was not able to un-idle when a new build pipeline was created. Also, the idler was triggered when a new build pipeline was created. This behavior was seen repeatedly and consistently on January 7.
Steps To Reproduce
The text was updated successfully, but these errors were encountered: