Blazar

  1. Bug #1807689
  2. Comment #2

Comment 2 for bug 1807689

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to blazar (master)

Reviewed: https://review.opendev.org/650635
Committed: https://git.openstack.org/cgit/openstack/blazar/commit/?id=89bfc325caa86fd0af4eaa691d04e6772d55f588
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