nova metadata_workers configured in wrong section
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Nova Compute Charm |
Fix Released
|
Medium
|
Drew Freiberger |
Bug Description
Hi,
mitaka cloud on xenial running 17.11 charms. I haven't touched nova-compute's worker-multiplier, so it has its default value. nova.conf looks like this :
# mitaka
#######
# [ WARNING ]
# Configuration file maintained by Juju. Local changes may be overwritten.
#######
[DEFAULT]
[... irrelevant stuff ...]
default_
[neutron]
url = http://
auth_url = http://
auth_type = password
project_domain_name = default
user_domain_name = default
project_name = services
username = nova
password = password
signing_dir =
metadata_workers = 120
[keystone_
[... some more irrelevant stuff ...]
As you can see, the metadata_workers is in the [neutron] section. However, when I start the nova-compute service, here's what it logs :
$ grep metadata_workers /var/log/syslog
Mar 9 10:53:56 a nova-compute[
So it's failing to parse the number, presumably because it's in the wrong section. If I move "metadata_workers = 120" to the [DEFAULT] section, then nova-compute properly logs "metadata_workers = 120 log_opt_values"
The nova.conf template likely needs fixing. Other OpenStack version may be impacted.
PS : I'm not even sure this number is relevant for nova-compute.
Thanks
Changed in charm-nova-compute: | |
status: | Triaged → In Progress |
Changed in charm-nova-compute: | |
status: | Fix Committed → Fix Released |
metadata_workers has context in DVR based deployments where the neutron and nova metadata agents are run on all compute hosts - so in a 'normal' deployment this has no side effect.