Bug 1501319
Summary: | Panic error "cap out of range" on node when deleting other node in the cluster | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Meng Bo <bmeng> |
Component: | Networking | Assignee: | Dan Winship <danw> |
Status: | CLOSED ERRATA | QA Contact: | Meng Bo <bmeng> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.7.0 | CC: | aos-bugs, bbennett |
Target Milestone: | --- | ||
Target Release: | 3.7.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: Unchecked boundary condition
Consequence: In a cluster with two nodes, deleting one of them would cause the other one to crash (though it would be fine again after restarting).
Fix: The erroneous code was fixed
Result: No crash
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-11-28 22:16:57 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: |
Description
Meng Bo
2017-10-12 11:22:52 UTC
Code merged in v3.7.0-0.150.0. Tested on v3.7.0-0.150.0 The issue has been fixed. No panic error during node deletion. Verify the bug. (removed egress IP trello ID from the summary because this bug wasn't related to egress IPs at all, it was just a random bug introduced in the 3.7 cycle) 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-2017:3188 |