Not possible to configure Nova at the service level
Bug #2034949 reported by
Doug Szumski
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kolla-ansible |
Fix Released
|
Low
|
John Garbutt | ||
| Antelope |
Confirmed
|
Low
|
Unassigned | ||
| Bobcat |
Fix Released
|
Low
|
John Garbutt | ||
| Yoga |
Confirmed
|
Low
|
Unassigned | ||
| Zed |
Confirmed
|
Low
|
Unassigned | ||
Bug Description
Scenarios exist where it is necessary to customise Nova configuration at the service instance level. Eg. to specifically change a setting in the nova-compute-ironic service without changing the same setting in the other nova services. This is currently not possible in KA.
As an example, this may be required when working around known issues with nova-compute-ironic HA failover.
| Changed in kolla-ansible: | |
| status: | New → In Progress |
| description: | updated |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to kolla-ansible (master) | #1 |
| Changed in kolla-ansible: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/kolla-ansible 17.0.0.0rc1 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 69a67823297d077
Author: John Garbutt <email address hidden>
Date: Fri Sep 8 14:21:58 2023 +0100
Support customising Nova config at the individual service level
For example, an operator may wish to customise the
nova-
other Nova services.
Closes-Bug: #2034949
Change-Id: If8648d8e85ab3d