Red Hat Bugzilla – Bug 1422457
Failed to attach ebs volume due to InvalidParameterValue for parameter device
Last modified: 2017-07-24 10:11 EDT
Description of problem: Failed to attach ebs volume due to InvalidParameterValue for parameter device Version-Release number of selected component (if applicable): openshift v3.5.0.20+87266c6 kubernetes v1.5.2+43a9be4 etcd 3.1.0 How reproducible: 80% Steps to Reproduce: 1.Create 60 pv, pvc and pods 2.Check pods status Actual results: Some pods could not running Expected results: All of pods should be running Additional info: Error attaching EBS volume "vol-03c758a43bd51581c" to instance "i-072d9328131bcd9cd": InvalidParameterValue: Value (/dev/xvdpa) for parameter device is invalid. /dev/xvdpa is not a valid EBS device name
We could reproduce this issue https://github.com/kubernetes/kubernetes/issues/41453 on OCP, so report this bug
Closing this as dup of https://bugzilla.redhat.com/show_bug.cgi?id=1422531 *** This bug has been marked as a duplicate of bug 1422531 ***
Reopen this due to we need track this in the OCP product according to QE workflow
Fix for 3.5 has been merged in origin: https://github.com/openshift/origin/pull/13131 Fix for master: https://github.com/openshift/origin/pull/13130
This has been merged into ocp and is in OCP v3.5.0.37 or newer.
I have tested against openshift v3.5.0.37 and it passed 1.oc new-app openshift/postgresql-92-centos7 -e POSTGRESQL_USER=user -e POSTGRESQL_DATABASE=db -e POSTGRESQL_PASSWORD=password 2.oc create -f https://raw.githubusercontent.com/chao007/v3-testfiles/master/persistent-volumes/ebs/dynamic-provisioning-pvc.json 3.oc volume dc/postgresql-92-centos7 --add --type=persistentVolumeClaim --mount-path=/opt1 --name=v1 --claim-name=ebsc deploymentconfig "postgresql-92-centos7" updated 4.check pod is running 5.oc scale dc/postgresql-92-centos7 --replicas=0 6.wait for 10 seconds 7.oc scale dc/postgresql-92-centos7 --replicas=1 8.This pod is running I also create 50 pods using ebs volume, all the pods are running
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-2017:0884