You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Brian Federle (JIRA)" <ji...@apache.org> on 2013/07/12 21:11:48 UTC
[jira] [Updated] (CLOUDSTACK-3095) [UI][API]Able to add multiple tier networks to a deployed VM using “Add network” option.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Federle updated CLOUDSTACK-3095:
--------------------------------------
Component/s: (was: UI)
API issue. The API needs to add the validation check and return an error when adding a 2nd VPC tier to a NIC.
> [UI][API]Able to add multiple tier networks to a deployed VM using “Add network” option.
> ----------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3095
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3095
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: API
> Affects Versions: 4.2.0
> Reporter: manasaveloori
> Fix For: 4.2.0
>
>
> Steps:
> 1. Have a CS with advanced zone.
> 2. Create 2 VPCs and tier network under each VPC.(say VPC1-tier1 and VPC2-tier2).
> 3. Create a instance under VPC1 using tier1.
> 4. Now go to that created Vm->Nics->Add network->select tier2 from drop down.Add a network.
> Observation:
> As expected the network addition fails with exception. But the UI and API is listing all the networks under NICs for a VM. That is UI and API are listing multiple tiers to a VM.
> Ifconfig –a in Vm is not displaying the failed NICs.
> Also User should not be allowed to add VPC2 tier network to a VM belong to one VPC1.
> API passed:
> http://10.147.38.154:8096/client/api?command=listVirtualMachines&details=nics&id=c1024642-b4ba-4228-ace3-cf3cca587745
> API response:
> <listvirtualmachinesresponse cloud-stack-version="4.2.0-SNAPSHOT"><count>1</count><virtualmachine><id>c1024642-b4ba-4228-ace3-cf3cca587745</id><name>c1024642-b4ba-4228-ace3-cf3cca587745</name><account>admin</account><domainid>58f45860-d73e-11e2-8845-063078000024</domainid><domain>ROOT</domain><created>2013-06-20T21:53:15+0530</created><state>Running</state><haenable>false</haenable><zoneid>0f17ac3e-9499-4486-b7ab-5928cc97c98f</zoneid><zonename>zoneVMw</zonename><zonetype>Advanced</zonetype><hostid>1d17a148-9a60-4e2b-88fd-50187f4aeb21</hostid><hostname>10.147.40.29</hostname><guestosid>590a7c3a-d73e-11e2-8845-063078000024</guestosid><nic><id>600b7332-e285-4d36-9696-9435dbee4563</id><networkid>a311c39a-cabd-4fa5-9f96-8716a7145a4e</networkid><networkname>tierVMw</networkname><netmask>255.255.255.0</netmask><gateway>172.16.1.1</gateway><ipaddress>172.16.1.180</ipaddress><isolationuri>vlan://971</isolationuri><broadcasturi>vlan://971</broadcasturi><traffictype>Guest</traffictype><type>Isolated</type><isdefault>true</isdefault><macaddress>02:00:1d:a8:00:03</macaddress></nic><nic><id>595d0ea1-fdc8-4138-8880-e201edeb8d96</id><networkid>178d6d12-e7d3-41df-b6cf-22db48b88db4</networkid><networkname>tier1</networkname><netmask>255.255.255.0</netmask><gateway>10.0.1.1</gateway><ipaddress>10.0.1.61</ipaddress><isolationuri>vlan://970</isolationuri><broadcasturi>vlan://970</broadcasturi><traffictype>Guest</traffictype><type>Isolated</type><isdefault>false</isdefault><macaddress>02:00:40:94:00:08</macaddress></nic><nic><id>232420cc-6eec-432f-9679-9751e1ce0d47</id><networkid>dff16b9f-0484-477d-a16e-887db1d7a7d2</networkid><networkname>sh</networkname><netmask>255.255.255.0</netmask><gateway>10.147.55.1</gateway><ipaddress>10.147.55.102</ipaddress><isolationuri>vlan://55</isolationuri><broadcasturi>vlan://55</broadcasturi><traffictype>Guest</traffictype><type>Shared</type><isdefault>false</isdefault><macaddress>06:cb:1a:00:00:83</macaddress></nic><hypervisor>VMware</hypervisor><publicipid>a90c4f5a-6ad5-4a7c-a425-36d227255ff7</publicipid><publicip>10.147.47.9</publicip><instancename>i-2-25-VM</instancename><displayvm>true</displayvm></virtualmachine>
--
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