Swift Recon middleware can't be launched due to wrong configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Won't Fix
|
Medium
|
Oleksiy Molchanov | ||
Mitaka |
Fix Released
|
Medium
|
Oleksiy Molchanov |
Bug Description
--- Environment ---
Release: MOS 9.2 (build 574)
Storage backend: Swift
--- Description ---
There is a cron job "/etc/cron.
However, it can't be launched and fails because there is no "[filter:recon]" section in object-server.conf
--- Steps to reproduce ---
1. Deploy an HA environment with Swift backend
2. On a Controller node run the following command:
/usr/bin/
--- Actual result ---
Launch of Swift Recon fails with the following traceback:
Traceback (most recent call last):
File "/usr/bin/
main()
File "/usr/bin/
conf = dict(c.
File "/usr/lib/
raise NoSectionError(
ConfigParser.
# echo $?
1
--- Expected result ---
Swift Recon has successfully launched:
# echo $?
0
--- Notes ---
Here is example of the configuration:
https:/
Changed in fuel: | |
assignee: | nobody → Oleksiy Molchanov (omolchanov) |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in fuel: | |
milestone: | none → 11.x-updates |
Changed in fuel: | |
status: | In Progress → Won't Fix |
sla2 for 9.0-updates