Bug 1499172 – [3.7] Deleted in use PVCs can break the scheduler

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

Bug 1499172 - [3.7] Deleted in use PVCs can break the scheduler

Summary:	[3.7] Deleted in use PVCs can break the scheduler

Status:	CLOSED ERRATA

Aliases:	None

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

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

URL:
Whiteboard:
Keywords:

Depends On:	1496256 1499174 1499175 1499176 1499177 1499178
Blocks:
	Show dependency tree / graph

Reported:	2017-10-06 05:57 EDT by Jan Safranek
Modified:	2017-11-28 17:15 EST (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:	1496256
Environment:
Last Closed:	2017-11-28 17:15:02 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
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)

Comment 1 Jan Safranek 2017-10-06 07:30:07 EDT

downstream PR: https://github.com/openshift/origin/pull/16718

Comment 2 Jan Safranek 2017-10-11 14:37:05 EDT

merged in Origin / 3.7

Comment 4 Wenqi He 2017-10-13 02:23:56 EDT

Tested on below version:
openshift v3.7.0-0.143.3
kubernetes v1.7.0+80709908fd

This bug has been fixed. Pod in another name space is running.

Comment 7 errata-xmlrpc 2017-11-28 17:15:02 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.