Not possible to configure Nova at the service level

Bug #2034949 reported by Doug Szumski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Status tracked in Bobcat
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
Doug Szumski (dszumski)
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (master)

Reviewed: https://review.opendev.org/c/openstack/kolla-ansible/+/894298
Committed: https://opendev.org/openstack/kolla-ansible/commit/69a67823297d0772d39abf154e2b7c8dc49c684f
Submitter: "Zuul (22348)"
Branch: master

commit 69a67823297d0772d39abf154e2b7c8dc49c684f
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-compute-ironic service configuration without affecting
    other Nova services.

    Closes-Bug: #2034949

    Change-Id: If8648d8e85ab3dbcbb4ecba674b2e34b06898327

Changed in kolla-ansible:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.