[
https://issues.apache.org/jira/browse/CLOUDSTACK-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Abhinandan Prateek updated CLOUDSTACK-4083:
-------------------------------------------
Assignee: Bharat Kumar
> [Multiple_IP_Ranges] Failure in adding additional network to a vm should
> delete the IP alias created
> -----------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4083
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4083
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Environment: Latest build from ACS 4.2 branch
> Reporter: Sanjeev N
> Assignee: Bharat Kumar
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: cloud.dmp, management-server.rar
>
>
> Failure in adding additional network to a vm should delete the IP alias
> created if the additional network is a shared network and it has multiple
> subnets.
> Steps to Reproduce:
> =================
> 1.Bring up CS in advanced zone with vmware cluster
> 2.Create a guest vm with isolated network using default cent os template
> 3.Create a shared network with two subnets in the same vlan.
> 4.Exhaust all the ip addresses from the first subnet.
> 5.Add this shared network to guest vm created above.
> Adding shared network will create ip alias on the VR since the ip address
> that CS picks to assign to the vm will be from the second subnet in that
> shared network.
> 6. Since vmware-tools are not installed on guest vm adding additional network
> would fail.
> Failure in adding additional nic will unplug the nic from vm and the nic will
> be in "Deallocating" state. As part of clean up the IP Alias got created at
> step5 should also be deleted and should be freed-up. Otherwise user will be
> charged for the IP usage even though not using it.
> Please look for job-270 in the attached log file for the sequence of events .
--
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
