[
https://issues.apache.org/jira/browse/CLOUDSTACK-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Hertanu updated CLOUDSTACK-4735:
---------------------------------------
Description:
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
was:
With only one computing node in the Zone, rebooting it (or a crash) 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
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
