Bug 1502789 – Pod running but logs say volume not attached

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

Bug 1502789 - Pod running but logs say volume not attached

Summary:	Pod running but logs say volume not attached

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 unspecified
Target Milestone:	---
Target Release:	3.5.z
Assigned To:	Hemant Kumar
QA Contact:	Liang Xia
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1444096
Blocks:
	Show dependency tree / graph

Reported:	2017-10-16 13:02 EDT by Hemant Kumar
Modified:	2017-12-07 02:13 EST (History)
CC List:	8 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:	1444096
Environment:
Last Closed:	2017-12-07 02:13:19 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:3389	normal	SHIPPED_LIVE	Moderate: Red Hat OpenShift Enterprise security, bug fix, and enhancement update	2017-12-07 07:09:10 EST

Groups: None (edit)

Comment 3 Liang Xia 2017-11-07 03:16:01 EST

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 02:13:19 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:3389

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