[jira] [Updated] (CLOUDSTACK-6796) [OVS]Failure in network update does not change network offering to original offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murali Reddy updated CLOUDSTACK-6796: - Fix Version/s: (was: 4.4.0) Future > [OVS]Failure in network update does not change network offering to original > offering > > > Key: CLOUDSTACK-6796 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6796 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller >Affects Versions: 4.4.0 > Environment: Latest build from 4.4 with commit > d130530bd3e1cd6d8249d5045e00e4e4e2201521 >Reporter: Sanjeev N >Assignee: Murali Reddy >Priority: Critical > Labels: ovs > Fix For: Future > > Attachments: management-server.rar > > > [OVS]Failure in network update does not change network offering to original > offering hence starting vms would fail in the network > Steps to Reproduce: > === > 1.Bring up CS in advanced zone with xen cluster > 2.Create physical network with GRE isolation > 3.Create network with default offering > "DefaultIsolatedNetworkOfferingWithSourceNatService" > 4.Deploy few vms in the above netwrok > 5.Create another network offering with virtual networking service and OVS as > the connectivity service provider > 6.Stop all the vms in the network > 7.Update network with new offering created at step5 > Results: > == > Network update will fail from vlan isolation to connectivity service due to > bug CS-6795. However the network offering id for the network is changing to > new network offering. It is not setting back to default isolated network > offering. > mysql> select * from ntwk_offering_service_map where network_offering_id=15; > ++-++---+-+ > | id | network_offering_id | service| provider | created > | > ++-++---+-+ > | 60 | 15 | Connectivity | Ovs | 2014-05-26 > 12:51:34 | > | 55 | 15 | Dhcp | VirtualRouter | 2014-05-26 > 12:51:34 | > | 54 | 15 | Dns| VirtualRouter | 2014-05-26 > 12:51:34 | > | 61 | 15 | Firewall | VirtualRouter | 2014-05-26 > 12:51:34 | > | 58 | 15 | Lb | VirtualRouter | 2014-05-26 > 12:51:34 | > | 57 | 15 | PortForwarding | VirtualRouter | 2014-05-26 > 12:51:34 | > | 56 | 15 | SourceNat | VirtualRouter | 2014-05-26 > 12:51:34 | > | 59 | 15 | StaticNat | VirtualRouter | 2014-05-26 > 12:51:34 | > | 53 | 15 | UserData | VirtualRouter | 2014-05-26 > 12:51:34 | > ++-++---+-+ > 9 rows in set (0.00 sec) > Following is the network created with default isolated network offering but > after network update failure the offering still shows the new offering: > mysql> select * from networks where id=211\G; > *** 1. row *** >id: 211 > name: vlan1 > uuid: f803e17f-b59b-4229-9e70-5bb4fcfc2570 > display_text: vlan1 > traffic_type: Guest > broadcast_domain_type: Vlan > broadcast_uri: vlan://986 > gateway: 10.1.1.1 > cidr: 10.1.1.0/24 > mode: Dhcp > network_offering_id: 15 > physical_network_id: 200 >data_center_id: 1 > guru_name: ExternalGuestNetworkGuru > state: Shutdown > related: 211 > domain_id: 1 >account_id: 2 > dns1: NULL > dns2: NULL > guru_data: NULL >set_fields: 0 > acl_type: Account >network_domain: cs2cloud.internal >reservation_id: c2b3cb64-adfd-4722-9aed-8d2d7710e32f >guest_type: Isolated > restart_required: 0 > created: 2014-05-28 11:09:16 > removed: NULL > specify_ip_ranges: 0 >vpc_id: NULL > ip6_gateway: NULL > ip6_cidr: NULL > network_cidr: NULL > display_network: 1 >network_acl_id: NULL > streched_l2: 0 > 1 row in set (0.00 sec) > ERROR: > No query specified > Impact of this: > === > Since the network offering is with connectivity service , CS is failed to > implement the network and vm start is failing. > 2014-05-28 07:52:28,188 DEBUG [c.c.n.e.OvsEle
[jira] [Updated] (CLOUDSTACK-6796) [OVS]Failure in network update does not change network offering to original offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Murali Reddy updated CLOUDSTACK-6796: - Assignee: (was: Murali Reddy) > [OVS]Failure in network update does not change network offering to original > offering > > > Key: CLOUDSTACK-6796 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6796 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller >Affects Versions: 4.4.0 > Environment: Latest build from 4.4 with commit > d130530bd3e1cd6d8249d5045e00e4e4e2201521 >Reporter: Sanjeev N >Priority: Critical > Labels: ovs > Fix For: Future > > Attachments: management-server.rar > > > [OVS]Failure in network update does not change network offering to original > offering hence starting vms would fail in the network > Steps to Reproduce: > === > 1.Bring up CS in advanced zone with xen cluster > 2.Create physical network with GRE isolation > 3.Create network with default offering > "DefaultIsolatedNetworkOfferingWithSourceNatService" > 4.Deploy few vms in the above netwrok > 5.Create another network offering with virtual networking service and OVS as > the connectivity service provider > 6.Stop all the vms in the network > 7.Update network with new offering created at step5 > Results: > == > Network update will fail from vlan isolation to connectivity service due to > bug CS-6795. However the network offering id for the network is changing to > new network offering. It is not setting back to default isolated network > offering. > mysql> select * from ntwk_offering_service_map where network_offering_id=15; > ++-++---+-+ > | id | network_offering_id | service| provider | created > | > ++-++---+-+ > | 60 | 15 | Connectivity | Ovs | 2014-05-26 > 12:51:34 | > | 55 | 15 | Dhcp | VirtualRouter | 2014-05-26 > 12:51:34 | > | 54 | 15 | Dns| VirtualRouter | 2014-05-26 > 12:51:34 | > | 61 | 15 | Firewall | VirtualRouter | 2014-05-26 > 12:51:34 | > | 58 | 15 | Lb | VirtualRouter | 2014-05-26 > 12:51:34 | > | 57 | 15 | PortForwarding | VirtualRouter | 2014-05-26 > 12:51:34 | > | 56 | 15 | SourceNat | VirtualRouter | 2014-05-26 > 12:51:34 | > | 59 | 15 | StaticNat | VirtualRouter | 2014-05-26 > 12:51:34 | > | 53 | 15 | UserData | VirtualRouter | 2014-05-26 > 12:51:34 | > ++-++---+-+ > 9 rows in set (0.00 sec) > Following is the network created with default isolated network offering but > after network update failure the offering still shows the new offering: > mysql> select * from networks where id=211\G; > *** 1. row *** >id: 211 > name: vlan1 > uuid: f803e17f-b59b-4229-9e70-5bb4fcfc2570 > display_text: vlan1 > traffic_type: Guest > broadcast_domain_type: Vlan > broadcast_uri: vlan://986 > gateway: 10.1.1.1 > cidr: 10.1.1.0/24 > mode: Dhcp > network_offering_id: 15 > physical_network_id: 200 >data_center_id: 1 > guru_name: ExternalGuestNetworkGuru > state: Shutdown > related: 211 > domain_id: 1 >account_id: 2 > dns1: NULL > dns2: NULL > guru_data: NULL >set_fields: 0 > acl_type: Account >network_domain: cs2cloud.internal >reservation_id: c2b3cb64-adfd-4722-9aed-8d2d7710e32f >guest_type: Isolated > restart_required: 0 > created: 2014-05-28 11:09:16 > removed: NULL > specify_ip_ranges: 0 >vpc_id: NULL > ip6_gateway: NULL > ip6_cidr: NULL > network_cidr: NULL > display_network: 1 >network_acl_id: NULL > streched_l2: 0 > 1 row in set (0.00 sec) > ERROR: > No query specified > Impact of this: > === > Since the network offering is with connectivity service , CS is failed to > implement the network and vm start is failing. > 2014-05-28 07:52:28,188 DEBUG [c.c.n.e.OvsElement] > (Work-Job-Executor-47:ctx-3e2b5a9e job-122/job-123
[jira] [Updated] (CLOUDSTACK-6796) [OVS]Failure in network update does not change network offering to original offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjeev N updated CLOUDSTACK-6796: -- Attachment: management-server.rar Attached MS log file > [OVS]Failure in network update does not change network offering to original > offering > > > Key: CLOUDSTACK-6796 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6796 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Network Controller >Affects Versions: 4.4.0 > Environment: Latest build from 4.4 with commit > d130530bd3e1cd6d8249d5045e00e4e4e2201521 >Reporter: Sanjeev N >Assignee: Murali Reddy >Priority: Critical > Labels: ovs > Fix For: 4.4.0 > > Attachments: management-server.rar > > > [OVS]Failure in network update does not change network offering to original > offering hence starting vms would fail in the network > Steps to Reproduce: > === > 1.Bring up CS in advanced zone with xen cluster > 2.Create physical network with GRE isolation > 3.Create network with default offering > "DefaultIsolatedNetworkOfferingWithSourceNatService" > 4.Deploy few vms in the above netwrok > 5.Create another network offering with virtual networking service and OVS as > the connectivity service provider > 6.Stop all the vms in the network > 7.Update network with new offering created at step5 > Results: > == > Network update will fail from vlan isolation to connectivity service due to > bug CS-6795. However the network offering id for the network is changing to > new network offering. It is not setting back to default isolated network > offering. > mysql> select * from ntwk_offering_service_map where network_offering_id=15; > ++-++---+-+ > | id | network_offering_id | service| provider | created > | > ++-++---+-+ > | 60 | 15 | Connectivity | Ovs | 2014-05-26 > 12:51:34 | > | 55 | 15 | Dhcp | VirtualRouter | 2014-05-26 > 12:51:34 | > | 54 | 15 | Dns| VirtualRouter | 2014-05-26 > 12:51:34 | > | 61 | 15 | Firewall | VirtualRouter | 2014-05-26 > 12:51:34 | > | 58 | 15 | Lb | VirtualRouter | 2014-05-26 > 12:51:34 | > | 57 | 15 | PortForwarding | VirtualRouter | 2014-05-26 > 12:51:34 | > | 56 | 15 | SourceNat | VirtualRouter | 2014-05-26 > 12:51:34 | > | 59 | 15 | StaticNat | VirtualRouter | 2014-05-26 > 12:51:34 | > | 53 | 15 | UserData | VirtualRouter | 2014-05-26 > 12:51:34 | > ++-++---+-+ > 9 rows in set (0.00 sec) > Following is the network created with default isolated network offering but > after network update failure the offering still shows the new offering: > mysql> select * from networks where id=211\G; > *** 1. row *** >id: 211 > name: vlan1 > uuid: f803e17f-b59b-4229-9e70-5bb4fcfc2570 > display_text: vlan1 > traffic_type: Guest > broadcast_domain_type: Vlan > broadcast_uri: vlan://986 > gateway: 10.1.1.1 > cidr: 10.1.1.0/24 > mode: Dhcp > network_offering_id: 15 > physical_network_id: 200 >data_center_id: 1 > guru_name: ExternalGuestNetworkGuru > state: Shutdown > related: 211 > domain_id: 1 >account_id: 2 > dns1: NULL > dns2: NULL > guru_data: NULL >set_fields: 0 > acl_type: Account >network_domain: cs2cloud.internal >reservation_id: c2b3cb64-adfd-4722-9aed-8d2d7710e32f >guest_type: Isolated > restart_required: 0 > created: 2014-05-28 11:09:16 > removed: NULL > specify_ip_ranges: 0 >vpc_id: NULL > ip6_gateway: NULL > ip6_cidr: NULL > network_cidr: NULL > display_network: 1 >network_acl_id: NULL > streched_l2: 0 > 1 row in set (0.00 sec) > ERROR: > No query specified > Impact of this: > === > Since the network offering is with connectivity service , CS is failed to > implement the network and vm start is failing. > 2014-05-28 07:52:28,188 DEBUG [c.c.n.e.OvsElement] >
