Bug 1801931
Summary: | max_disk_devices_to_attach set to 0 don't allow to create any instance | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | jpateteg | |
Component: | openstack-nova | Assignee: | melanie witt <mwitt> | |
Status: | CLOSED ERRATA | QA Contact: | OSP DFG:Compute <osp-dfg-compute> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 16.0 (Train) | CC: | dasmith, eglynn, igallagh, jhakimra, kchamart, mwitt, rheslop, sbauza, sgordon, vromanso | |
Target Milestone: | beta | Keywords: | Triaged | |
Target Release: | 17.0 | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | openstack-nova-22.1.0-0.20210129121939.900fd51.el8ost | Doc Type: | Bug Fix | |
Doc Text: |
Before this update, the help text for the `max_disk_devices_to_attach` parameter did not state that `0` is an invalid value. Also, when the `max_disk_devices_to_attach` parameter was set to `0`, the `nova-compute` service started when it should have failed. With this update, the `max_disk_devices_to_attach` parameter help option text states that a value of `0` is invalid, and if `max_disk_devices_to_attach` is set to `0`, the `nova-compute` service will now log an error and fail to start.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1924406 (view as bug list) | Environment: | ||
Last Closed: | 2022-09-21 12:09:13 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1924406, 1924407 |
Description
jpateteg
2020-02-11 23:17:26 UTC
Here's a link to our existing documentation around the max_disk_devices_to_attach config option: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/15/html-single/advanced_overcloud_customization/index#sect-Config_max_disk_devices_to_attach 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 (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), 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/RHEA-2022:6543 |