Cannot reload configuration in manila-scheduler
Bug #1785129 reported by
Goutham Pacha Ravi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Shared File Systems Service (Manila) |
Fix Released
|
Medium
|
Tom Barron |
Bug Description
Mutable configuration was introduced to manila in [1]. However, the scheduler process ignores any SIGHUP sent to it.
RCA:
The manila-scheduler process does not use the ProcessLauncher that we fixed up in [1]. It uses service.launch()
Changed in manila: | |
importance: | Undecided → Medium |
assignee: | nobody → sajuptpm (sajuptpm) |
milestone: | none → rocky-3 |
Changed in manila: | |
assignee: | sajuptpm (sajuptpm) → Tom Barron (tpb) |
status: | New → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/585890 /git.openstack. org/cgit/ openstack/ manila/ commit/ ?id=9da534344a9 b8790c88378816d b1c1fc378b2a59
Committed: https:/
Submitter: Zuul
Branch: master
commit 9da534344a9b879 0c88378816db1c1 fc378b2a59
Author: Saju.Madhavan <email address hidden>
Date: Thu Jul 26 02:46:17 2018 +0530
Fix mutable config in manila-scheduler
We had SIGHUP apply the "mutate" behavior to the
ProcessLauncher with [1], however, the scheduler
process does not use ProcessLauncher.
Oslo config made "debug" a mutable config option
in [3]
Closes-Bug: #1785129
[1] I6499ae6c98d948 9a123bb20febd6c 1ddb9e17b86 5f4c09954b2f46c e2da7106d90
[3] I1e7a69de169cc8
Change-Id: Ifffe3cad0f5cd5 2988ce253794efc 5b03ea9840b