GET on router does not report internal interfaces
Bug #1049246 reported by
Salvatore Orlando
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
The l3 API extension does not have an attribute for listing the interfaces added to a router with{add|
It would be to see the corresponding subnets in responses to GET requests on /routers
Assignign to myself while I work out the size of a patch for prospective rc1 inclusion.
Revision history for this message
| dan wendlandt (danwent) wrote | #1 |
Revision history for this message
| Salvatore Orlando (salvatore-orlando) wrote | #2 |
| Changed in quantum: | |
| importance: | Medium → Undecided |
| status: | Confirmed → Invalid |
| assignee: | Salvatore Orlando (salvatore-orlando) → nobody |
To post a comment you must log in.
This was by design, though you could argue its a bit confusing.
The thought was that router interfaces would be fetched by search for all ports with device_id=<router uuid>