Nova-compute generates incorrect exit code in case if child spawning failed

Bug #1853800 reported by Margarita Shakhova on 2019-11-25
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Undecided
Unassigned
oslo.service
Undecided
Unassigned

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.

Matt Riedemann (mriedem) wrote :

This is likely something that is controlled down in the oslo.service library code which nova-compute uses.

Changed in nova:
status: New → Confirmed
Changed in oslo.service:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers