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.

Moving to 4.2 as OpenStack is not supported in 4.1

Moving to modified as there is no build ready yet.

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.

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

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

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

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