cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matty Courtney (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-4735) Management IP address pool exhausted
Date Thu, 14 Jan 2016 10:23:39 GMT


Matty Courtney commented on CLOUDSTACK-4735:

I realize this bug is quite old, but I encountered it today so it seems to be still around.

For anyone that faces the same issue here is a generic SQL statement that will release any
Management IP addresses that are reported as released by the nics table:

mysql> UPDATE cloud.op_dc_ip_address_alloc ip SET ip.reservation_id = NULL, ip.taken =
NULL WHERE ip.nic_id IN (SELECT id FROM cloud.nics n WHERE n.removed IS NOT NULL);

> Management IP address pool exhausted
> ------------------------------------
>                 Key: CLOUDSTACK-4735
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: XenServer
>    Affects Versions: 4.1.0
>         Environment: Management server (CentOS 6.4 64 bit, CLoudStack 4.1.1), XenServer
>            Reporter: Daniel Hertanu
> With only one computing node in the Zone, rebooting it without enabling maintenance mode
on it, determines the management IP addresses pool to be exhausted as a result of CloudStack
attempting continuously to provision the system VMs. Regardless the expunge delay or interval
values, the management IPs are not released anymore and the common error reported in the logs
> 2013-09-24 14:56:24,410 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-22:job-72)
Insufficient capacity Unable to
get a management ip addressScope=interface; id=1

This message was sent by Atlassian JIRA

View raw message