Bug 1298942
Summary: | atomic-openshift-node crash | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jeremy Eder <jeder> |
Component: | Networking | Assignee: | Dan Winship <danw> |
Status: | CLOSED ERRATA | QA Contact: | Meng Bo <bmeng> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.1.0 | CC: | agoldste, aos-bugs, danw, eparis, jamills, jeder, jokerman, mmccomas, rpenta, tdawson, tstclair, uobergfe |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-05-12 16:26:43 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: |
Comment 5
Andy Goldstein
2016-01-15 16:17:51 UTC
Need a bump commit for origin; moving back to assigned. I am marking this UpcomingRelease. This is a transient failure at node startup which should be recovered when systemd restarts the node a second time. We recognize the need to fix this problem but since we are already 3 days past the code due date and since this does not appear to be a new problem, I am not going to blocker the 3.1.1 release. Although we thought we had a reasonable path forward as this bug was debugged it was found that the order in which the system comes up means that fixing the issue is much more complex than anticipated. Thanks, I have built OSE test packages with the commit below, and will let you know if it happens again. https://github.com/danwinship/ose/commit/bde7b29ffa9c0782eb0754654702857ace2158c7 This is fixed in git master (by https://github.com/openshift/origin/pull/6684) @Jeremy Did you meet the crash recently? Can we close this bug? It is difficult to reproduce/verify this bug from my side. Thanks. Yep, I think it's fixed. Thanks. Resolve the bug. 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/RHSA-2016:1064 |