Some requests to Blazar hang after sending a SIGHUP to blazar-manager

Bug #1807689 reported by Pierre Riteau on 2018-12-10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Asmita Singh

Bug Description

After sending a SIGHUP signal to blazar-manager, most (but not all) requests to Blazar don't receive any answer. It's as if RPC messaging between API and manager is partially broken.

Hint from Masahito:

09:56:37 <masahito> I guess RPCServer in blazar.utils.service should need to have SIGHUP signal handler.

Discovered while testing

Changed in blazar:
assignee: nobody → Asmita Singh (asmita2018)
Changed in blazar:
assignee: Asmita Singh (asmita2018) → nobody
Changed in blazar:
assignee: nobody → Asmita Singh (asmita2018)
status: New → In Progress

Submitter: Zuul
Branch: master

commit 89bfc325caa86fd0af4eaa691d04e6772d55f588
Author: asmita singh <email address hidden>
Date: Wed Feb 27 13:40:32 2019 +0000

    Handle SIGHUP signal for blazar-manager correctly

    After a SIGHUP signal is sent to blazar-manager, the RPC messaging
    between API and blazar-manager stops working and users start seeing
    "Internal Server Error".

    This issue is fixed in this patch, which adds a wait method to the
    RPCServer class and calls the wait method of the RPC server from
    oslo.messaging, so that all existing requests are fulfilled before
    restarting the blazar-manager service again.

    Change-Id: I8272975afeabfb74f974e9bf9a6ae9162c22a6e0
    Closes-Bug: #1807689

Changed in blazar:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers