You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Makrand Sanap (JIRA)" <ji...@apache.org> on 2018/08/24 12:00:00 UTC

[jira] [Issue Comment Deleted] (CLOUDSTACK-4735) Management IP address pool exhausted

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Makrand Sanap updated CLOUDSTACK-4735:
--------------------------------------
    Comment: was deleted

(was: From the details, it seems this issue is not solved in any of the releases of CS so far. Am I right? I've encountered the same. [~mattycourtney]querry worked like charm.)

> 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
>            Priority: Major
>
> 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
(v7.6.3#76005)