Bug #3443
VNet can assign out of range leases
| Status: | Closed | Start date: | 12/11/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Ruben S. Montero | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 4.10.2 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 4.10 |
Description
Steps to reproduce:
- Create a vnet with size 10
- Create 5 VMs
- Delete those 5 VMs
- Resize AR to 2
- Create a new VM. The lease is out of the new range
Associated revisions
bug #3443: Reset address index when size is updated
bug #3443: Reset address index when size is updated
(cherry picked from commit bda68ea01183725204b931a3da44c5ea5428cbc7)
History
#1
Updated by Ruben S. Montero over 6 years ago
- Assignee set to Ruben S. Montero
- Target version set to Release 4.10.2
#2
Updated by Carlos Martín over 6 years ago
A side effect is that the out-of-range lease will not be freed when the VM is deleted.
#3
Updated by Ruben S. Montero over 6 years ago
- Status changed from New to Closed
- Resolution set to fixed