[SRU] octavia-api won't start by default
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Fix Released
|
High
|
Unassigned | ||
Rocky |
Fix Released
|
High
|
Unassigned | ||
octavia (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Cosmic |
Fix Released
|
High
|
Unassigned | ||
Disco |
Fix Released
|
High
|
Unassigned |
Bug Description
[Impact]
After installing octavia-api the systemd unit fails to start:
Failed 'systemctl status octavia-api' output shows:
error: unrecognized arguments: --http-socket [::]:9876 --ini /etc/octavia/
The problem is that init files are configured with UWSGI options but the binary being run is not uwsgi. See full output: https:/
[Test Case]
1) sudo apt install octavia-api
2) watch systemctl status octavia-api # watch to ensure it doesn't fail
3) curl 127.0.0.1:9876 # should return something like [1], not [2]
[1] {"versions": [{"id": "v1", "status": "DEPRECATED", "updated": "2014-12-
[2] curl: (7) Failed to connect to 127.0.0.1 port 9876: Connection refused
[Regression Potential]
Low. The provided fix only touches the octavia-api and is using the standard approach that OpenStack has historically used to start a service which is to use the service's /usr/bin/
Changed in octavia (Ubuntu Cosmic): | |
importance: | Undecided → High |
status: | New → Triaged |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in cloud-archive: | |
status: | Triaged → Fix Committed |
I've uploaded a fix for this to the cosmic review queue: https:/ /launchpad. net/ubuntu/ cosmic/ +queue? queue_state= 1&queue_ text=