swift-proxy not restarted after config file change

Bug #1775411 reported by Edward Hope-Morley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Swift Proxy Charm
Invalid
High
Unassigned

Bug Description

I just upgraded my charm which wrote a new proxy-server.conf (with changes) but the charm did not restart the swift-proxy service as a result:

root@juju-8d95f0-swift-3:~# ll /etc/swift/proxy-server.conf
-rw-r--r-- 1 root root 2172 Jun 6 14:26 /etc/swift/proxy-server.conf
root@juju-8d95f0-swift-3:~# date
Wed Jun 6 14:30:26 UTC 2018
root@juju-8d95f0-swift-3:~# ps -e -opid,etime,cmd| grep swift
 6056 00:16 python3 /var/lib/juju/agents/unit-swift-proxy-0/charm/hooks/update-status
 6389 00:00 grep --color=auto swift
12294 52:06 bash /var/lib/juju/init/jujud-unit-swift-proxy-0/exec-start.sh
12304 52:06 /var/lib/juju/tools/unit-swift-proxy-0/jujud unit --data-dir /var/lib/juju --unit-name swift-proxy/0 --debug
31326 38:46 /usr/bin/python /usr/bin/swift-proxy-server /etc/swift/proxy-server.conf
31338 38:44 /usr/bin/python /usr/bin/swift-proxy-server /etc/swift/proxy-server.conf

Changed in charm-swift-proxy:
milestone: none → 18.08
importance: Undecided → High
tags: added: sts
James Page (james-page)
Changed in charm-swift-proxy:
status: New → Triaged
James Page (james-page)
Changed in charm-swift-proxy:
milestone: 18.08 → 18.11
Revision history for this message
Liam Young (gnuoy) wrote :

I haven't been able to reproduce this and config-changed appears to have the correct restart decorator. Can you confirm that this bug is still occurring please?

Changed in charm-swift-proxy:
status: Triaged → Incomplete
David Ames (thedac)
Changed in charm-swift-proxy:
milestone: 18.11 → 19.04
David Ames (thedac)
Changed in charm-swift-proxy:
milestone: 19.04 → 19.07
David Ames (thedac)
Changed in charm-swift-proxy:
milestone: 19.07 → 19.10
David Ames (thedac)
Changed in charm-swift-proxy:
milestone: 19.10 → 20.01
tags: added: charm-upgrade
Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

Setting to invalid as there has been no movement in over a year, and the bug appears to not have been reproduced. It may have been overtaken by events.

Changed in charm-swift-proxy:
status: Incomplete → Invalid
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.