Bug 1669544

Summary:	Clarification on KUBE_MAX_PD_VOLS for OpenShift/OpenStack Integration
Product:	OpenShift Container Platform	Reporter:	Hemant Kumar <hekumar>
Component:	Storage	Assignee:	Hemant Kumar <hekumar>
Status:	CLOSED ERRATA	QA Contact:	Chao Yang <chaoyang>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.1.0	CC:	aos-bugs, aos-storage-staff, bbennett, bchilds, chaoyang, florin-alexandru.peter, lxia, piqin
Target Milestone:	---
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1669543	Environment:
Last Closed:	2019-10-16 06:27:41 UTC	Type:	---
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:	1659442, 1669543
Bug Blocks:	1668893

Comment 1 Hemant Kumar 2019-02-07 22:13:03 UTC

Fix for 4.0 - https://github.com/openshift/origin/pull/21989 

We still need to enable this in scheduler. We can use https://github.com/openshift/cluster-kube-scheduler-operator/pull/57 to enable it.

Comment 5 Liang Xia 2019-05-06 02:43:40 UTC

Moving to 4.2 as OpenStack is not supported in 4.1

Moving to modified as there is no build ready yet.

Comment 6 Hemant Kumar 2019-05-06 14:14:16 UTC

This bug can be verified by deploying Openshift on Openstack and then manually enabling the predicate via scheduler.json file. The limits can be configured via openstack.conf file. We should also document this stuff for Openshift 4.2.

Comment 9 Florin Peter 2019-09-04 18:33:37 UTC

Is there some kind of docs how to set it on 4.2? 
I want to test it with our 4.2 preview version.

Comment 10 Chao Yang 2019-09-20 08:05:23 UTC

Due to the resource limit, testing this bug as below.    

            {
                        newPod:       twoVolCinderPod,
                        existingPods: []*v1.Pod{twoVolCinderPod},
                        filterName:   CinderVolumeFilterType,
                        maxVols:      1,
                        fits:         true,
                        test:         "fits when node capacity >= new pod's Cinder volumes",
                },
 


go test -run TestVolumeCountConflicts
--- FAIL: TestVolumeCountConflicts (0.00s)
	max_attachable_volume_predicate_test.go:802: [Cinder]fits when node capacity >= new pod's Cinder volumes: expected true, got false
	max_attachable_volume_predicate_test.go:820: Using allocatable [Cinder]fits when node capacity >= new pod's Cinder volumes: expected true, got false
FAIL
exit status 1
FAIL	k8s.io/kubernetes/pkg/scheduler/algorithm/predicates	0.013s

Comment 12 errata-xmlrpc 2019-10-16 06:27:41 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-2019:2922

Comment 13 Red Hat Bugzilla 2023-09-14 04:45:41 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days