SIGHUP: handle listening socket correctly

Bug #1436272 reported by Stuart McLaren
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Glance
Fix Released
Undecided
Stuart McLaren

Bug Description

When a SIGHUP signal is received prompting a reload of the configuration we need to ensure that changes to the listening socket take effect.

Revision history for this message
Stuart McLaren (stuart-mclaren) wrote :
Changed in glance:
assignee: nobody → Stuart McLaren (stuart-mclaren)
status: New → In Progress
tags: added: kilo-rc-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to glance (master)

Reviewed: https://review.openstack.org/123482
Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=ff59a907937a8a2f1a7134332102d5a526594228
Submitter: Jenkins
Branch: master

commit ff59a907937a8a2f1a7134332102d5a526594228
Author: Stuart McLaren <email address hidden>
Date: Tue Sep 16 13:55:41 2014 +0000

    Zero downtime config reload (socket handling)

    Pick up changes to socket configuration on reload.

    To avoid any interruption to request handling on reload we recycle the
    original listening socket rather than closing it (if at all possible).

    Closes-bug: 1436272
    Change-Id: Ibf0ad60a3a50e60b1bc8b32f9a2e567079a6f821

Changed in glance:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in glance:
milestone: none → kilo-rc1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in glance:
milestone: kilo-rc1 → 2015.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.