Bug 1502789 - Pod running but logs say volume not attached
Summary: Pod running but logs say volume not attached
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.5.z
Assignee: Hemant Kumar
QA Contact: Liang Xia
URL:
Whiteboard:
Depends On: 1444096
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-16 17:02 UTC by Hemant Kumar
Modified: 2023-09-07 18:58 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1444096
Environment:
Last Closed: 2017-12-07 07:13:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:3389 0 normal SHIPPED_LIVE Moderate: Red Hat OpenShift Enterprise security, bug fix, and enhancement update 2017-12-07 12:09:10 UTC

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
Note You need to log in before you can comment on or make changes to this bug.