doc: setting [compute]max_disk_devices_to_attach = 0 prevents instances from booting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
melanie witt | ||
Stein |
New
|
Undecided
|
Unassigned | ||
Train |
Fix Released
|
Low
|
Stephen Finucane | ||
Ussuri |
Fix Released
|
Low
|
Stephen Finucane | ||
Victoria |
Fix Released
|
Low
|
Stephen Finucane |
Bug Description
This is a bug to track the addition of a note to the config option help for [compute]
The CONF.max_
of disk devices allowed to attach to an instance. If it is set to 0, it
will literally allow no disk device for instances, preventing them from
being able to boot.
There doesn't appear to be any way to disallow particular values
in a oslo.config IntOpt other than the min/max values. Here we need the
min value to be -1 to represent unlimited. There is a 'choices' kwarg
available but that is only for enumerating valid values and we need to
allow any integer >= 1 as well. Finally, there doesn't seem to be a
good way to validate this option setting as -1 or >= 1 because it's a
nova-compute config option and our choices there are likely: prevent
nova-compute from starting because of value 0 or log a WARNING about
it, both of which seem like they might be overkill. So, highlighting
the behavior of value 0 in the documentation might be the best way to
handle the issue.
Changed in nova: | |
status: | New → In Progress |
I have updated the patch to raise InvalidConfigur ation during nova-compute init_host based on seeing other usage of InvalidConfigur ation around CPU pinning config validation.