Bug 1317577

Summary: postgresql-persistent template pv enters failed state when started from the web ui
Product: OpenShift Container Platform Reporter: Scott Dodson <sdodson>
Component: StorageAssignee: Sami Wagiaalla <swagiaal>
Status: CLOSED ERRATA QA Contact: Jianwei Hou <jhou>
Severity: urgent Docs Contact:
Priority: medium    
Version: 3.2.0CC: agrimm, aos-bugs, bchilds, dakini, haowang, hchen, jeder, jhou, jsafrane, mmccomas, mmcgrath, pmorie, sdodson, sten, swagiaal, tdawson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1313560 Environment:
Last Closed: 2016-05-12 16:32:43 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:
Bug Depends On: 1313560, 1318161    
Bug Blocks: 1303130    

Comment 1 Sami Wagiaalla 2016-03-16 17:26:15 UTC 
The fix for this is here: https://github.com/kubernetes/kubernetes/pull/22791
this was cherry piked into 1.2 here: https://github.com/kubernetes/kubernetes/pull/22945

and will likely be pulled into 3.2 in a rebase
Comment 2 Sami Wagiaalla 2016-03-16 17:51:49 UTC 
> and will likely be pulled into 3.2 in a rebase

https://github.com/kubernetes/kubernetes/pull/22791

will be pulled into 3.2:

https://github.com/openshift/origin/issues/6766

that should cover this bug.
Comment 3 Paul Morie 2016-03-17 21:54:38 UTC 
The 1.2.0 tag of origin should contain the cherry-pick of the upstream commit now.
Comment 4 Jianwei Hou 2016-03-18 09:23:18 UTC 
Tested on ded-int.
The pods using ebs persistent volume could be successfully created. The PV/PVC binding and invalid ebs volume id issue is gone. I'll mark this bug as verified. The rest aws issues will be tracked on separate bugs.
Comment 6 errata-xmlrpc 2016-05-12 16:32:43 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-2016:1064