Bug 1365379

Summary:	Need to have 'NoVolumeZoneConflict' scheduler policy enabled by installer
Product:	OpenShift Container Platform	Reporter:	Jianwei Hou <jhou>
Component:	Installer	Assignee:	Andrew Butcher <abutcher>
Status:	CLOSED ERRATA	QA Contact:	Jianwei Hou <jhou>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.3.0	CC:	adellape, aos-bugs, gpei, jokerman, mmccomas, xtian
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:	The installer now enables the NoVolumeZoneConflict scheduler policy by default. This policy restricts that with pods with persistent volumes (PVs) be scheduled in the availability zone where its PV is located.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-18 19:30:55 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:

Comment 1 openshift-github-bot 2016-08-09 20:18:26 UTC

Commit pushed to master at https://github.com/openshift/openshift-ansible

https://github.com/openshift/openshift-ansible/commit/4a87e79b695c08392cebc20135a2e38300863d18
Merge pull request #2279 from abutcher/no-volume-zone

Bug 1365379 - Need to have 'NoVolumeZoneConflict' scheduler policy enabled by installer

Comment 3 Gaoyun Pei 2016-08-11 02:20:32 UTC

Verify this bug with openshift-ansible-3.2.20-1.git.0.dd68681.el7.noarch.rpm

After installation, NoVolumeZoneConflict scheduler policy is enabled by default.
[root@openshift-218 ~]# cat /etc/origin/master/scheduler.json
{
    "apiVersion": "v1",
    "kind": "Policy",
    "predicates": [
        {
            "name": "MatchNodeSelector"
        },
        {
            "name": "PodFitsResources"
        },
        {
            "name": "PodFitsPorts"
        },
        {
            "name": "NoDiskConflict"
        },
        {
            "name": "NoVolumeZoneConflict"
        },
        {
            "argument": {
                "serviceAffinity": {
                    "labels": [
                        "region"
                    ]
                }
            },
            "name": "Region"
        }
    ],
    "priorities": [
        {
            "name": "LeastRequestedPriority",
            "weight": 1
        },
        {
            "name": "SelectorSpreadPriority",
            "weight": 1
        },
        {
            "argument": {
                "serviceAntiAffinity": {
                    "label": "zone"
                }
            },
            "name": "Zone",
            "weight": 2
        }
    ]

Comment 5 errata-xmlrpc 2016-08-18 19:30:55 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:1639