This is likely something that is controlled down in the oslo.service
library code which nova-compute uses.
** Also affects: oslo.service
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1853800
Title:
Nova-compute generates incorrect exit code in case if child spawning
failed
Status in OpenStack Compute (nova):
New
Status in oslo.service:
New
Bug description:
In situation if nova-compute main process fails to spawn a child
(worker) process e.g. because of database connection failure: ERROR
oslo_db.sqlalchemy.engines DBConnectionError:
(pymysql.err.OperationalError) worker process exits with code 1,
however, exit code of main process is 0. It shold be 1 because the
service failed to start because of error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1853800/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
