Bug 1348824
| Summary: | [docker1.10] hawkular-cassandra in CrashLoopBackOff against ose-3.1 with docker-1.10 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | chunchen <chunchen> | ||||||
| Component: | Hawkular | Assignee: | Matt Wringe <mwringe> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Peng Li <penli> | ||||||
| Severity: | low | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 3.1.0 | CC: | aos-bugs, bleanhar, wsun | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 3.2.1 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2016-10-31 16:14:26 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
chunchen
2016-06-22 07:41:56 UTC
Lowering the severity simply because we haven't decided if this is even supported. Can you please provide the logs for the Cassandra pod which was killed? You can normally get this with 'oc logs -p' which gives the logs of the previous pod. Attaching the logs as a file is usually easier to parse than pasting it in the comment section. Also, what is under the events tab for this Cassandra pod? Created attachment 1171228 [details]
hawkular-cassandra logs
Created attachment 1171229 [details]
hawkular-cassandra events
If those are the full logs using 'oc logs -p', then Cassandra appears to be starting up. So its not that Cassandra is failing to start. From the events, it looks like something is killing the Cassandra container, which would most likely be something like a lifecycle script. Except in Cassandra 3.1.1 we don't have a lifecycle script which would kill the pod, it should just prevent the pod from reaching the ready state. Is the only main difference now that you are running on Docker 1.10 instead of 1.8? Yes, the main difference is docker version, docker 1.10 is running in one environment and docker 1.8 is running in another one. Closing this as WONTFIX as it appears this is not a supported configuration. |