Bug 2153815 - [17.0 known issue] Document that the quota:cpu_* flavor extra specs do not work with cgroups v2 in RHEL 9
Summary: [17.0 known issue] Document that the quota:cpu_* flavor extra specs do not wo...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Irina
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-12-15 14:34 UTC by Artom Lifshitz
Modified: 2023-09-05 01:51 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
There is currently a known issue with creating instances when the instance flavor includes resource usage extra specs, `quota:cpu_*`. On RHOSP 17.0, attempts to create an instance with a flavor that limits the CPU quotas encounter the following error: "Requested CPU control policy not supported by host". This error is raised on RHOSP 17.0 on RHEL 9 because the Compute service assumes that the host is running `cgroups` instead of `cgroups-v2`, therefore it incorrectly detects that the host does not support resource usage extra specs.
Clone Of:
Environment:
Last Closed: 2022-12-21 11:46:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-20904 0 None None None 2022-12-15 14:44:10 UTC

Description Artom Lifshitz 2022-12-15 14:34:23 UTC
Known issue for https://bugzilla.redhat.com/show_bug.cgi?id=2118968, which will be fixed in 17.1.

Comment 1 Artom Lifshitz 2022-12-15 14:38:33 UTC
We'd also like to add the following to our product docs:


Document that the values for quota:cpu_* are host and virt driver dependant, and if you're upgrading to 17.1 you need to:

a. Make sure the values in your extra specs are supported by cgroups v2 on RHEL 9.

b. Create new flavors and resize your instances if they're not.

Comment 3 Artom Lifshitz 2022-12-19 15:20:48 UTC
Doc text seems a bit vague, but if that's the level of "generality" that we use in our release notes, I won't contradict it. Left a comment on the product docs MR.


Note You need to log in before you can comment on or make changes to this bug.