Bug 1415282 – [3.3] Hit panic and segment error in atomic-openshift-node log

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1415282 - [3.3] Hit panic and segment error in atomic-openshift-node log

Summary:	[3.3] Hit panic and segment error in atomic-openshift-node log

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Networking (Show other bugs)
Sub Component:
Version:	3.3.1
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	---
Target Release:	3.3.1
Assigned To:	Ben Bennett
QA Contact:	Zhang Cheng
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1412087
Blocks:
	Show dependency tree / graph

Reported:	2017-01-20 13:19 EST by Scott Dodson
Modified:	2017-01-26 15:43 EST (History)
CC List:	11 users (show)

See Also:
Fixed In Version:	atomic-openshift-3.3.1.11-1.git.0.cba037c.el7
Doc Type:	Bug Fix
Doc Text:	Cause: Use of a nil pointer. Consequence: OpenShift would panic and generate a segment error. Fix: Check the pointer before dereferencing. Result: OpenShift functions correctly.
Story Points:	---
Clone Of:	1412087
Environment:
Last Closed:	2017-01-26 15:43:56 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Origin (Github)	12446	None	None	None	2017-01-20 13:19 EST
Red Hat Product Errata	RHBA-2017:0199	normal	SHIPPED_LIVE	OpenShift Container Platform 3.3.1.11 and 3.2.1.23 bug fix update	2017-01-26 20:41:56 EST

Groups: None (edit)

Comment 2 DeShuai Ma 2017-01-22 04:57:52 EST

Verify on v3.3.1.11, bug is fixed.
Steps: https://bugzilla.redhat.com/show_bug.cgi?id=1412087#c9

Comment 4 errata-xmlrpc 2017-01-26 15:43:56 EST

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-2017:0199

Note You need to log in before you can comment on or make changes to this bug.