Bug 1602963 – containerized atomic-openshift-node unable to mount flexvolume

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

Bug 1602963 - containerized atomic-openshift-node unable to mount flexvolume

Summary:	containerized atomic-openshift-node unable to mount flexvolume

Status:	CLOSED ERRATA

Aliases:	None

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

Priority	unspecified Severity high
Target Milestone:	---
Target Release:	3.11.0
Assigned To:	Hemant Kumar
QA Contact:	Jianwei Hou
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1588029 1592677
Blocks:
	Show dependency tree / graph

Reported:	2018-07-18 18:06 EDT by Hemant Kumar
Modified:	2018-10-11 03:22 EDT (History)
CC List:	12 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:	1592677
Environment:
Last Closed:	2018-10-11 03:21:41 EDT
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	RHBA-2018:2652	None	None	None	2018-10-11 03:22 EDT

Groups: None (edit)

Comment 1 Hemant Kumar 2018-07-18 18:07:27 EDT

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

Comment 3 Jianwei Hou 2018-08-28 01:57:05 EDT

We have tested this in rpm install and system container install. Flexvolume works for containerized kubelet.

Comment 5 errata-xmlrpc 2018-10-11 03:21:41 EDT

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-2018:2652

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