Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jenkins Reliability #1

Open
glamperi opened this issue Aug 6, 2018 · 1 comment
Open

Jenkins Reliability #1

glamperi opened this issue Aug 6, 2018 · 1 comment

Comments

@glamperi
Copy link

glamperi commented Aug 6, 2018

I am having an issue were when the lab is provisioned It has an issue provisioning the Jenkins pod. If I try to do this using the service catalog, it also remains pending. When I try to deploy manual, I get the following error:

oc rollout latest dc/jenkins
Error from server (BadRequest): cannot trigger a deployment for "jenkins"
because it contains unresolved images

@bkoz
Copy link

bkoz commented Aug 29, 2018

Not sure if this is related but I just ran through the lab (v3.10) on RHDPS and had an issue where the Jenkins pod runs but does not come ready (1/1) and eventually times out. I noticed it was running really slow so I increased the default cpu limit from 500m to 2000m and it fixed the issue. The Jenkins pod seems really cpu intensive when it starts up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants