Description of problem:
New pod deployed created a claim on an existing pv, even though the claim correctly bound to the pv as seen by 'oc get pv' the pv did not attach to the instance as seen in AWS as the volume is still listed as 'Available' and unattached to the node.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
pvc still in pending, not correctly attached to the node. Volume is still marked as Available and not attached to the instance in aws.
pvc claim to correctly attach to the instance, pvc should not be in pending.
[root]# oc get pvc -n jrawlings
NAME STATUS VOLUME CAPACITY ACCESSMODES AGE
nexus-storage Pending nexus-storage 0 3h
[root]# oc get pvc nexus-storage -o yaml -n jrawlings
[root]# oc get pv pv-1-rh-idev-master-46a1e-vol-fe696d5b -o yaml
Attaching the node logs would be very helpful.
This looks very similar to #1369977
OpenShift master logs (with log level 5) from master start to would be very helpful indeed!
I also need some steps to reproduce - what did you do? What is PV pv-1-rh-idev-master-46a1e-vol-fe696d5b and PV nexus-storage? How did you create the PVC (i.e. the input yaml)? Did nexus-storage or pv-1-rh-* exist at that moment?
I believe that nexus-storage is the name of the pvc to claim the pv pv-1-rh-idev-master-46a1e-vol-fe696d5b
oc describe pv pv-1-rh-idev-master-46a1e-vol-fe696d5b
Reclaim Policy: Retain
Access Modes: RWO
Type: AWSElasticBlockStore (a Persistent Disk resource in AWS)
Based on the timestamp of creation, the pv was created before the pvc.
interesting, from pvc yaml I can read nexus-storage PVC is bound to nexus-storage PV:
Was there any nexus-storage PV?
*** This bug has been marked as a duplicate of bug 1370312 ***