Bug 1567827
| Summary: | [3.9]hawkular metrics pod failed at liveness check, pod can not be started up | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> |
| Component: | Hawkular | Assignee: | Ruben Vargas Palma <rvargasp> |
| Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.9.0 | CC: | aos-bugs, juzhao, rvargasp |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | 3.9.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1551474 | Environment: | |
| Last Closed: | 2018-05-17 06:43:35 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: | 1551474, 1613130 | ||
| Bug Blocks: | |||
|
Comment 1
Junqi Zhao
2018-04-16 09:22:40 UTC
metrics-hawkular-metrics-v3.9.25-1 already fixed this issue. Remove TestBlocker keyword, and please set it to ON_QA Tested with metrics-hawkular-metrics:v3.9.20-2, hawkular metrics pod can be started up now # oc get po -n openshift-infra NAME READY STATUS RESTARTS AGE hawkular-cassandra-1-m5kf5 1/1 Running 0 50m hawkular-metrics-5mrpb 1/1 Running 0 50m heapster-xv882 1/1 Running 0 50m Images: metrics-cassandra/images/v3.9.20-2 metrics-hawkular-metrics/images/v3.9.20-2 metrics-heapster/images/v3.9.20-2 The currently latest images also passed testing # oc get po -n openshift-infra NAME READY STATUS RESTARTS AGE hawkular-cassandra-1-d7bvp 1/1 Running 0 4m hawkular-metrics-lp8bv 1/1 Running 0 4m heapster-25dwc 1/1 Running 0 4m metrics-heapster/images/v3.9.27-1 metrics-hawkular-metrics/images/v3.9.27-1 metrics-cassandra/images/v3.9.27-1 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:1566 |