Bug 1554711
| Summary: | [online-stg]Can't login jenkins webconsole due to "Liveness probe failed" | ||
|---|---|---|---|
| Product: | OpenShift Online | Reporter: | XiuJuan Wang <xiuwang> |
| Component: | Templates | Assignee: | Stefanie Forrester <dakini> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | XiuJuan Wang <xiuwang> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.x | CC: | aos-bugs, bparees, dakini, ddelcian, dyan, gmontero, jokerman, mmccomas, wewang, wzheng, xiuwang, yufchang |
| Target Milestone: | --- | Keywords: | OnlinePro, OnlineStarter, Regression |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1551500 | Environment: | |
| Last Closed: | 2018-07-30 15:37:59 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: | |||
| Bug Depends On: | 1551500 | ||
| Bug Blocks: | |||
|
Comment 1
XiuJuan Wang
2018-03-13 08:39:05 UTC
Looks ok after the latest updates in online-int and free-int. @Stefanie jenkins-persistent template are updated in free-int free-stg and online-int. And can't reproduce 504 error when access jenkins console via route at first time Could you help to update this template in online-stg too? online-stg is using the jenkins image from registry.access.redhat.com, whereas online-int is using reg-aws. This should be correct... (We want to use reg-aws in INT but not in STG or PROD). I'm able to visit the route to my jenkins app. Is it really still broken in online-stg? Maybe I don't understand which part is broken. Thanks, https://jenkins-dakinitest20180413.717f.online-stg.openshiftapps.com/securityRealm/commenceLogin?from=%2F This bug is fixed by update jenkins-persistent template[1],but the template is old in online-stg. So we still met 504 error when access jenkins webconsole at first time. [1] https://github.com/openshift/origin/pull/18839/ Thanks, that's good to know. I think we'll have to live with the initial 504 error until the updated image is pushed to registry.access. The reason is that we want to use registry.access for production and stg, to ensure we're getting the most stable images. Removing from blocker list. While looking at bz #1579188 I realized this bug isn't waiting on a new image to be pushed to the registry. We were waiting on a template update. I'll be updating the template in the next week, so I should be able to pull in this change too. The jenkins-persistent template in online-stg has updated as [1]. Also jenkins app could be accessed successfully. [1] https://github.com/openshift/origin/pull/18839/ Server https://api.online-stg.openshift.com:443 openshift v3.9.31 kubernetes v1.9.1+a0ce1bc657 |