Open gibizer opened 1 year ago
I tried in devstack where we use uwsgi instead of mod_wsgi. There the nova-api process exists if the config is invalid.
Jul 05 08:20:08 gibi-devstack-aio devstack@n-api.service[3619164]: ERROR nova oslo_config.cfg.ConfigFileValueError: Value for option metadata_workers from LocationInfo(location=<Locations.user: (4, True)>, detai>
Jul 05 08:20:08 gibi-devstack-aio devstack@n-api.service[3619164]: ERROR nova
Jul 05 08:20:08 gibi-devstack-aio devstack@n-api.service[3619164]: unable to load app 0 (mountpoint='') (callable not found or import error)
Jul 05 08:20:08 gibi-devstack-aio devstack@n-api.service[3619164]: *** no app loaded. going in full dynamic mode ***
Jul 05 08:20:33 gibi-devstack-aio devstack@n-api.service[3619163]: --- no python application found, check your startup logs for errors ---
So there are two issues actually: 1) nova-operator generates a wrong config 2) the nova-api and nova-metadata detects the invalid config but it does not fail but instead starts with an incomplete config
We set metadata_workers to 0 for the nova-api and the nova-api starts but fails to load the full oslo configuration as the config validation fails with:
Then the nova-api only logs a subset of the oslo.config parameters so it actually runs with a partial config:
If the
metadata_workers
is set to 1 the nova-api dumps the full oslo.config as expected see full.txt