[
https://issues.apache.org/jira/browse/CLOUDSTACK-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14251350#comment-14251350
]
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 id=1;
Don’t forget to replace the id above with the proper id from your database.
> Management IP address pool exhausted
> ------------------------------------
>
> Key: CLOUDSTACK-4735
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4735
> 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 6.1
> 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 is:
> 2013-09-24 14:56:24,410 INFO [cloud.vm.VirtualMachineManagerImpl]
> (Job-Executor-22:job-72) Insufficient capacity
> com.cloud.exception.InsufficientAddressCapacityException: Unable to get a
> management ip addressScope=interface com.cloud.dc.Pod; id=1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
