We just recently added a warning about this in the OSP6 docs:
https://bugzilla.redhat.com/show_bug.cgi?id=1311508

Just to verify, did this problem persist in OSP7-8? If so, we will add the same warning to those two releases.

(In reply to Don Domingo from comment #1)
> We just recently added a warning about this in the OSP6 docs:
> https://bugzilla.redhat.com/show_bug.cgi?id=1311508
> 
> Just to verify, did this problem persist in OSP7-8? If so, we will add the
> same warning to those two releases.

Per Eoghan's last comment on the original bug (which appears in the description here), yes. Unfortunately it may also persist in 9 (need to double check).

This bug is well known, and is in progress upstream under the Resource Pools banner. I would say at this point this will not land for Newton (OSP10). Ocata remains a possibility.

Closing this here, as it can't be fixed in RHOS 6. This is a highly visible, priority upstream feature, though. It will be resolved, and there's no great benefit to tracking it separately in BZ.