fallocate_reserve is still broken on py3
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
We thought we fixed bug #1844368 -- but we only fixed up the WSGI servers. Which meant that if you put the config option in your [DEFAULT] section, your background daemons would blow up like
Traceback (most recent call last):
File "/usr/local/
exec(
File "/vagrant/
run_
File "/vagrant/
log_
File "/vagrant/
conf = dict(c.
File "/usr/lib/
return [(option, value_getter(
File "/usr/lib/
return [(option, value_getter(
File "/usr/lib/
section, option, d[option], d)
File "/usr/lib/
self.
File "/usr/lib/
"found: %r" % (rest,))
configparser.
Reviewed: https:/ /review. opendev. org/734721 /git.openstack. org/cgit/ openstack/ swift/commit/ ?id=2854eddb442 4327fc6dc9b7930 fd2874b5b23df4
Committed: https:/
Submitter: Zuul
Branch: master
commit 2854eddb4424327 fc6dc9b7930fd28 74b5b23df4
Author: Tim Burke <email address hidden>
Date: Tue Jun 9 16:45:21 2020 -0700
py3: (Better) fix percentages in configs
We previously fixed a bunch of places, but not quite *all* the places;
at the very least, some account-layer services (like the replicator and
auditor IIRC) could still bomb out -- and it's important that
replicators still respect fallocate_reserve!
Now, do the NicerInterpolation thing every time we call readconf.
Additionally, clean up the original fix to avoid globally
monkey-patching configparser.
Related-Bug: #1844368 30f0482909f5372 20a57fef76b
Closes-Bug: #1872553
Change-Id: I4512e686cde379