Errors found for octavia api----get listener stats
Bug #1543356 reported by
min wang
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| octavia |
Fix Released
|
Medium
|
Stephen Balukoff | ||
Bug Description
When I tested the octavia api with postman, I found the following services are not able to work properly, need someone to take a look at them:
List Listener Statistics with endpoint url---{
<html>
<head>
<title>404 Not Found</title>
</head>
<body>
<h1>404 Not Found</h1>
The resource could not be found.
<br />
<br />
</body>
</html>
| description: | updated |
| summary: |
- Errors found for octavia api + Errors found for octavia api----get listener stats |
| Changed in octavia: | |
| importance: | Undecided → Medium |
| tags: | added: lbaas |
| tags: |
added: sharedpools removed: lbaas |
| Changed in octavia: | |
| assignee: | nobody → Stephen Balukoff (sbalukoff) |
| tags: | added: target-mitaka |
Revision history for this message
| Stephen Balukoff (sbalukoff) wrote | #1 |
| Changed in octavia: | |
| status: | New → Confirmed |
Revision history for this message
| Stephen Balukoff (sbalukoff) wrote | #3 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to octavia (master) | #4 |
| Changed in octavia: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to octavia (master) | #5 |
| Changed in octavia: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Michael-- looking at the Octavia API prior to the shared pools patch, it doesn't look like we ever actually coded a listener stats endpoint. So... even though the documentation talks about it, it looks like this has never actually worked for Octavia before. For what it's worth, it looks like the stats table in the database is being populated correctly.
Shall I go ahead an code an API endpoint which dumps the stats for a given listener, per the Octavia API docs, or, since we've never had this working before, do we want to take the chance to discuss the stats interface (ie. before we get locked into an API / stats model that we don't want to support long-term)?