Bug #3646
XMLRPC does not filter reservation vnets
| Status: | Closed | Start date: | 03/03/2015 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Carlos Martín | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 4.12 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 4.10 |
Description
When asking for an specific set of vnets with one.vnpool.info with start and end all the reservations after the initial ID are retrieved. For example:
# onevnet list ID USER GROUP NAME CLUSTER BRIDGE LEASES 3000 oneadmin oneadmin net.3000 - br.3000 101 3001 oneadmin oneadmin reservation - br.3000 0 3002 oneadmin oneadmin reservation.200 - br.3000 0 3003 oneadmin oneadmin reservation.201 - br.3000 0 3004 oneadmin oneadmin net.3004 - br.3004 0 3005 oneadmin oneadmin net.3005 - br.3005 0
The call network_pool.info(-2, 3000, 3000) returns the IDs 3000, 3001, 3002 and 3003
Associated revisions
Bug #3646: Filter reservation by start & end ids
History
#1
Updated by Ruben S. Montero over 6 years ago
- Status changed from Pending to New
- Target version set to Release 4.12
#2
Updated by Carlos Martín over 6 years ago
- Status changed from New to Closed
- Assignee set to Carlos Martín
- Resolution set to fixed