cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Hertanu (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-4735) Management IP address pool exhausted
Date Thu, 18 Dec 2014 07:59:14 GMT


Daniel Hertanu commented on CLOUDSTACK-4735:

That's how I fixed it at the time...

Having 4 management IP addresses, I found in the table op_dc_ip_address_alloc two of them
being reserved so I simply did this (after I took a backup of the database):

mysql> update op_dc_ip_address_alloc set nic_id=NULL,reservation_id=NULL,taken=NULL where

Don’t forget to replace the id above with the proper id from your database.

> 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