Bug 1356010
Summary: | Volume affinity in Openshift | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jaspreet Kaur <jkaur> | |
Component: | Node | Assignee: | Andy Goldstein <agoldste> | |
Status: | CLOSED ERRATA | QA Contact: | DeShuai Ma <dma> | |
Severity: | medium | Docs Contact: | ||
Priority: | urgent | |||
Version: | 3.2.0 | CC: | agoldste, aos-bugs, jkaur, jokerman, knakayam, michael.voegele, mmccomas, pep, tdawson, wmeng | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Enhancement | ||
Doc Text: |
Feature: Volume affinity in OpenShift
Reason: Cloud providers typically use multiple zones/regions for their virtual machines and storage offerings. A virtual machine in one zone/region can only mount storage from the same zone/region in which it resides. OpenShift pods that use cloud storage must be scheduled onto virtual machines in the same zone/region for their associated storage; otherwise, the pods will fail to run.
Result: Pods are scheduled to the same zone/region as their associated storage. Note, if you are not using the default scheduler configuration, you need to ensure that the NoVolumeZoneConflict scheduler predicate is enabled in your scheduler configuration file in order for volume affinity to function correctly.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1365600 (view as bug list) | Environment: | ||
Last Closed: | 2016-09-27 09:39:54 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: | ||||
Bug Blocks: | 1267746, 1365600 |
Description
Jaspreet Kaur
2016-07-13 09:16:08 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-2016:1933 |