commit 82537871376afe98a286e1ba424cf192ae60869a
Author: Matt Riedemann <email address hidden>
Date: Fri Jan 18 10:42:13 2019 -0500
Restrict database access to nova-compute in singleconductor mode
Change I4820abe57a023050dd8d067c77e26028801ff288 removed access
to the database for the nova-compute process but only in
superconductor mode. Grenade runs in singleconductor mode though
so we are getting tracebacks in nova-compute logs during grenade
runs because nova-compute is running with nova.conf which is
configured with access to the nova API database.
This change handles removing database access for nova-compute
generically to cover both the singleconductor and superconductor
cases.
Reviewed: https:/ /review. openstack. org/631811 /git.openstack. org/cgit/ openstack- dev/devstack/ commit/ ?id=82537871376 afe98a286e1ba42 4cf192ae60869a
Committed: https:/
Submitter: Zuul
Branch: master
commit 82537871376afe9 8a286e1ba424cf1 92ae60869a
Author: Matt Riedemann <email address hidden>
Date: Fri Jan 18 10:42:13 2019 -0500
Restrict database access to nova-compute in singleconductor mode
Change I4820abe57a0230 50dd8d067c77e26 028801ff288 removed access
to the database for the nova-compute process but only in
superconductor mode. Grenade runs in singleconductor mode though
so we are getting tracebacks in nova-compute logs during grenade
runs because nova-compute is running with nova.conf which is
configured with access to the nova API database.
This change handles removing database access for nova-compute
generically to cover both the singleconductor and superconductor
cases.
Change-Id: I81301eeecc7669 a169deeb1e2c5d2 98a595aab94
Closes-Bug: #1812398