Bug 1427227 – Fix controller panic in creating pod event

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

Bug 1427227 - Fix controller panic in creating pod event

Summary:	Fix controller panic in creating pod event

Status:	CLOSED ERRATA

Aliases:	None

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

Priority	unspecified Severity high
Target Milestone:	---
Target Release:	3.7.0
Assigned To:	hchen
QA Contact:	Wenqi He
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1428009
	Show dependency tree / graph

Reported:	2017-02-27 11:03 EST by Hemant Kumar
Modified:	2017-11-28 16:52 EST (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	No Doc Update
Doc Text:	undefined
Story Points:	---
Clone Of:
Clones:	1428009 (view as bug list)
Environment:
Last Closed:	2017-11-28 16:52:23 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)	13175	None	None	None	2017-03-01 12:09 EST
Red Hat Product Errata	RHSA-2017:3188	normal	SHIPPED_LIVE	Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update	2017-11-28 21:34:54 EST

Groups: None (edit)

Description Hemant Kumar 2017-02-27 11:03:37 EST

We need to bring the fix for panic in creating pod events:

https://github.com/openshift/origin/pull/12263

to Openshift 3.5 and master.

Comment 9 Wenqi He 2017-04-07 04:41:02 EDT

Per https://bugzilla.redhat.com/show_bug.cgi?id=1428009#c3, this bug is fixed. Changing status to verified.

Comment 14 errata-xmlrpc 2017-11-28 16:52:23 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/RHSA-2017:3188

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