[
https://issues.apache.org/jira/browse/CLOUDSTACK-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720583#comment-13720583
]
Koushik Das commented on CLOUDSTACK-2025:
-----------------------------------------
Looked at the db dump. The vm which failed to deploy is showing up in 'Error'
state and also not yet expunged as the removed field is still set to null.
IP address is allocated while deploying the VM and released while the VM is
expunged. Expunge happens based on the following global config parameters:
- expunge.delay
- expunge.interval
- expunge.workers
The default for delay/interval is set to 1day. Please verify with a smaller
value for these parameters. If the IP is not release even after the VM is
expunged then reopen.
> Failed VM creation on Xen Server does not release shared IP address
> -------------------------------------------------------------------
>
> Key: CLOUDSTACK-2025
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2025
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: XenServer
> Affects Versions: 4.1.0, 4.2.0
> Reporter: Demetrius Tsitrelis
> Assignee: Koushik Das
> Priority: Critical
> Attachments: management_logs.tgz, mysql_cloudstack_dump.sql
>
>
> Install and configure CS.
> Create VM instance from built-in CentOS template. Observe that instance is
> successfully created and shared IP address is allocated. Note shared IP
> address count.
> Upload and .ISO to CS.
> Create a new instance based on the .ISO; if that fails see that shared IP
> address still increases.
> Management logs and database dump attached.
--
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
