Bug 1502789

Summary:	Pod running but logs say volume not attached
Product:	OpenShift Container Platform	Reporter:	Hemant Kumar <hekumar>
Component:	Storage	Assignee:	Hemant Kumar <hekumar>
Status:	CLOSED ERRATA	QA Contact:	Liang Xia <lxia>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.5.0	CC:	aos-bugs, aos-storage-staff, eparis, hekumar, mawong, pdwyer, smunilla, wehe
Target Milestone:	---
Target Release:	3.5.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1444096	Environment:
Last Closed:	2017-12-07 07:13:19 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:
Bug Depends On:	1444096
Bug Blocks:

Comment 3 Liang Xia 2017-11-07 08:16:01 UTC

Tested on below version:
openshift v3.5.5.31.41
kubernetes v1.5.2+43a9be4
etcd 3.1.0


1. Create dynamic pvc and pod.
2. Restart atomic-openshift-node.service.
3. Run command "oc get events -w" for the project.
4. Run command "journalctl -u atomic-openshift-node -f" on the node which above pod is running on.


Did NOT see errors in step 3 and step 4 as describe in #comment 0.

So move bug to verified.

Comment 6 errata-xmlrpc 2017-12-07 07:13:19 UTC

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:3389