Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1422457

Summary: Failed to attach ebs volume due to InvalidParameterValue for parameter device
Product: OpenShift Container Platform Reporter: Chao Yang <chaoyang>
Component: StorageAssignee: Hemant Kumar <hekumar>
Status: CLOSED ERRATA QA Contact: Jianwei Hou <jhou>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.5.0CC: aos-bugs, bchilds, eparis, tdawson
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: incorrect aws device ids Consequence: Failed to attach ebs volume due to InvalidParameterValue for parameter device Fix: update aws device ids. Result: attach ebs volume success.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-12 19:13:04 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:

Description Chao Yang 2017-02-15 11:36:55 UTC 
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
Comment 1 Chao Yang 2017-02-15 11:37:53 UTC 
We could reproduce this issue https://github.com/kubernetes/kubernetes/issues/41453 on OCP, so report this bug
Comment 2 Hemant Kumar 2017-02-15 21:10:33 UTC 
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 ***
Comment 3 Chao Yang 2017-02-28 06:23:42 UTC 
Reopen this due to we need track this in the OCP product according to QE workflow
Comment 4 Hemant Kumar 2017-03-01 16:24:20 UTC 
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
Comment 5 Troy Dawson 2017-03-01 22:50:48 UTC 
This has been merged into ocp and is in OCP v3.5.0.37 or newer.
Comment 7 Chao Yang 2017-03-02 02:31:57 UTC 
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
Comment 9 errata-xmlrpc 2017-04-12 19:13:04 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/RHBA-2017:0884