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

Bug 1491761

Summary:	Two PVC mounted to the same pod provisioned to different AWS zones by dynamic provisioning
Product:	OpenShift Container Platform	Reporter:	Takayoshi Tanaka <tatanaka>
Component:	RFE	Assignee:	Bradley Childs <bchilds>
Status:	CLOSED WONTFIX	QA Contact:	Xiaoli Tian <xtian>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.6.1	CC:	aos-bugs, aos-storage-staff, bchilds, jokerman, jsafrane, lxia, mmccomas, tim.gollschewsky
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-12 11:59:48 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 Takayoshi Tanaka 2017-09-14 15:22:26 UTC

Description of problem:
It happened during the customer deployed CloudForms on OpenShift with AWS dynamic provisioning.
https://access.redhat.com/documentation/en-us/red_hat_cloudforms/4.5/html-single/installing_red_hat_cloudforms_on_openshift_container_platform/

The customer deployed OpenShift across three zones. Then he tagged EC2 instances as follows.
https://docs.openshift.com/container-platform/3.6/install_config/persistent_storage/dynamically_provisioning_pvs.html#available-dynamically-provisioned-plug-ins

XXX-2a    Key=kubernetes.io/cluster/zone-a,Value=zone-a
XXX-2b    Key=kubernetes.io/cluster/zone-b,Value=zone-b
XXX-2c    Key=kubernetes.io/cluster/zone-b,Value=zone-c

A cloudforms pod has two PVC. The created pods by dynamic provisioning were located at different zones.,


Version-Release number of selected component (if applicable):


How reproducible:
On the customer side, yes.
I haven't tested in CEE AWS account.


Steps to Reproduce:
1. Set up OpenShift across different AWS zone. Configure dynamic provisioning.
2. Deploy CloudForms on OpenShift

Actual results:
Created PVC are located at different zones, and the pod can't be scheduled by NoVolumeZoneConflict error.

Expected results:
Deployed without error

Additional info:
The issue was reported to another BZ and I was asked to file a new BZ.
https://bugzilla.redhat.com/show_bug.cgi?id=1365398#c18

Comment 1 Jan Safranek 2017-09-14 15:37:39 UTC

Thanks for creating a new bug.

Currently, our provisioners spread PVCs among zones randomly. So it can happen that a pod that uses two PVCs has to run in two zones which is not possible.

As a workaround, one can create a specific storage class for each zone and provision PVCs that need to be together in the same zone this way.

Proper fix requires significant changes in pod scheduler and PV binder and is discussed upstream in https://github.com/kubernetes/community/pull/1054. It is going to be implemented in 3.9 at the earliest.

Comment 2 Bradley Childs 2017-09-14 20:19:17 UTC

Marking low as this is an ongoing RFE.

Comment 3 Bradley Childs 2017-09-14 20:30:43 UTC

Added a trello card https://trello.com/c/GwNwzmUo/561-update-the-scheduler-to-take-pv-topology-into-account

Comment 6 Kirsten Newcomer 2019-06-12 11:59:48 UTC

With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers.  Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant.

This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. 

If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new 

Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new 

As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.