From 52d9dd2c0bbca1e8efcddf0539793b3481c095a5 Mon Sep 17 00:00:00 2001 From: Artom Lifshitz Date: Mon, 19 Jul 2021 11:48:05 +0200 Subject: [PATCH] doc: allow_resize_to_same_host needs nova-api restarted [DEFAULT]allow_resize_to_same host is a bit weird. It controls scheduling, is set in the [DEFAULT] section, but needs nova-api to be restarted for changes to take effect (the API layer calls compute_api.resize(), and the allow_resize_to_same_host check is performed there, and not in the scheduler). This patch adds a small blurn to the config help text to explain this. Change-Id: I5393dfaeaf123d28bb1889635792ee1ece2c5295 --- nova/conf/compute.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/nova/conf/compute.py b/nova/conf/compute.py index e787424977..5cf8c31714 100644 --- a/nova/conf/compute.py +++ b/nova/conf/compute.py @@ -51,7 +51,8 @@ Allow destination machine to match source for resize. Useful when testing in single-host environments. By default it is not allowed to resize to the same host. Setting this option to true will add the same host to the destination options. Also set to true -if you allow the ServerGroupAffinityFilter and need to resize. +if you allow the ServerGroupAffinityFilter and need to resize. For changes to +this option to take effect, the nova-api service needs to be restarted. """), cfg.ListOpt('non_inheritable_image_properties', default=['cache_in_nova', 'bittorrent'],