How to configure the OpenShift-Scheduler to consider Cinder-volume-limits on Openstack-Instances

Solution In Progress - Updated -

Issue

In OpenStack versions there is a hardcoded limit of 26 Cinder Volumes and the problem is that the OpenShift-Scheduler does not know about this limit.
This leads to the fact that Pods still get scheduled on Nodes where the limit is already exceeded and therefore the Pods get stuck

This limitation is documented at several places:
Bug 1583553 - [RFE] Not able to attach more than 26 virtio-scsi volumes
https://review.openstack.org/567472
http://lists.openstack.org/pipermail/openstack-dev/2018-June/131289.html
https://review.openstack.org/597306

Environment

OpenShift 3.*,
The limitation is OpenStack/Cinder specific and maybe changed in future
OpenStack versions

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content