← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1853800] [NEW] Nova-compute generates incorrect exit code in case if child spawning failed

 

Public bug reported:

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.

** Affects: nova
     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

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


Follow ups