You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sanjeev N (JIRA)" <ji...@apache.org> on 2014/05/20 13:36:39 UTC
[jira] [Created] (CLOUDSTACK-6722) [OVS][UI] Network created with
StretchedL2Subnet is not available for vm deployement in other zones
Sanjeev N created CLOUDSTACK-6722:
-------------------------------------
Summary: [OVS][UI] Network created with StretchedL2Subnet is not available for vm deployement in other zones
Key: CLOUDSTACK-6722
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6722
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Network Controller, UI
Affects Versions: 4.4.0
Environment: Latest build from 4.4 with commit e6961fd21bb6d793302c234d0f409f66dc498072
Reporter: Sanjeev N
Assignee: Gabor Apati-Nagy
Priority: Critical
Fix For: 4.4.0
[OVS][UI] Network created with StretchedL2Subnet is not available for vm deployement in other zones
Steps to Reproduce:
=================
1.Bring up CS with two or more zones say zone1 and zone2
2.Create physical networks with GRE isolation in all the zones
3.Create isolated network offering with VirtualNetwork service and ovs as the service provider and with StretchedL2Subnet Capability
4.In zone1 create guest network with above network offering
5.Deploy few vms in zone1 in the above network
6.In zone2 try to deploy vm in above network
Result:
======
vm deployment wizard does not show the network created in zone1 in list of available networks for vm deployment. It only shows the network created in zone2
Expected Result:
=============
Wizard should show networks created in zone2 as well as stretched networks created in other zones
Vm deployment in zone2 with stretched network created in zone1 works fine with API
--
This message was sent by Atlassian JIRA
(v6.2#6252)