IP not assigned to service instances in service chaining.

Bug #1602167 reported by Shashikiran H
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R3.1
Fix Released
High
Sachin Bansal
Trunk
Fix Released
High
Sachin Bansal

Bug Description

Version: 3.1.0.0-2739 mitaka
Topo:
host1 = 'root@10.204.216.201'
env.roledefs = {
    'all': [host1],
    'cfgm': [host1],
    'openstack': [host1],
    'control': [host1],
    'compute': [host1],
    'collector': [host1],
    'webui': [host1],
    'database': [host1],
    'build': [host_build],
}

I create a v1 transparent service chain between left and right vm. There are 2 SI in between the vms.
IP address is not assigned to the service instances when I create transparent service chain. The addresses to the left and right vms are assigned correctly.

root@nodeb8:~# nova list --all-tenants
+--------------------------------------+-------------------------------+----------------------------------+--------+------------+-------------+-----------------------------------------+
| ID | Name | Tenant ID | Status | Task State | Power State | Networks |
+--------------------------------------+-------------------------------+----------------------------------+--------+------------+-------------+-----------------------------------------+
| d4c55935-70bd-47ab-a9f6-2543ea28c045 | ctest-bridge_si-70529707_1001 | 2604ee19480a4200a4c4320131ef30a4 | ACTIVE | - | Running | |
| 6f6e47bb-6af1-430a-b0a9-20820d577ae0 | ctest-bridge_si-70529707_1002 | 2604ee19480a4200a4c4320131ef30a4 | ACTIVE | - | Running | |
| 38ffddf4-e007-47b5-9a52-2fe0aeaac7b8 | ctest-bridge_vm1-97858249 | 2604ee19480a4200a4c4320131ef30a4 | ACTIVE | - | Running | ctest-bridge_vn1-34590655=213.151.235.4 |
| 6e4eb0b1-5e4c-49ef-afd3-a6e24e331d3c | ctest-bridge_vm2-53567278 | 2604ee19480a4200a4c4320131ef30a4 | ACTIVE | - | Running | ctest-bridge_vn2-99329836=221.192.71.3 |

Did not find any schema crashes. I see flow drops with the error "short flow" when I ping from left to right vm because of this and no flows created in the agent.

Shashikiran H (skiranh)
summary: - IP not assigned to service instances in chaining.
+ IP not assigned to service instances in service chaining.
Revision history for this message
Vedamurthy Joshi (vedujoshi) wrote :
Download full text (11.0 KiB)

It is seen that this happens with Vns created using VncApi
neutron net-list would not show the subnet associated with that VN
For vms booted with that VN, nova show would not show the IPs from the VN.

Same behavior is seen for SIs.

root@nodeb8:~# python
Python 2.7.6 (default, Jun 22 2015, 17:58:13)
[GCC 4.8.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from vnc_api.vnc_api import *
>>> vh=VncApi(username='admin',password='contrail123',tenant_name='admin',api_server_host='127.0.0.1',api_server_port='8082')
>>> proj_obj = vh.project_read(fq_name=['default-domain','admin'])
>>> ipam_real_obj = vh.network_ipam_read(fq_name = ['default-domain','default-project','default-network-ipam'])
>>> api_vn_obj = VirtualNetwork(name='test1', parent_obj=proj_obj)
>>> vn_id = vh.virtual_network_create(vn_obj)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
NameError: name 'vn_obj' is not defined
>>> vn_id = vh.virtual_network_create(api_vn_obj)
>>> ipam = vh.network_ipam_read(fq_name = ['default-domain','default-project','default-network-ipam'])
>>> ipam_sn = IpamSubnetType(subnet=SubnetType('200.1.1.0', int(24)))
>>> ipam_sn_list=[]
>>> ipam_sn_lst.append(ipam_sn)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
NameError: name 'ipam_sn_lst' is not defined
>>> ipam_sn_list.append(ipam_sn)
>>> api_vn_obj.add_network_ipam(ipam, VnSubnetsType(ipam_sn_lst))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
NameError: name 'ipam_sn_lst' is not defined
>>> api_vn_obj.add_network_ipam(ipam, VnSubnetsType(ipam_sn_list))
>>> vh.virtual_network_update(api_vn_obj)
>>>

----------

root@nodeb8:/var/log/contrail# nova boot --nic net-id=95840df5-ad25-4a76-a8b1-e1d8cb86d673 --image 6b3d27f2-ed2c-484e-8f7a-db386f10e30a --flavor 1 vedu-vm1
+--------------------------------------+----------------------------------------------------------------+
| Property | Value |
+--------------------------------------+----------------------------------------------------------------+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-AZ:availability_zone | |
| OS-EXT-SRV-ATTR:host | - |
| OS-EXT-SRV-ATTR:hostname | vedu-vm1 |
| OS-EXT-SRV-ATTR:hypervisor_hostname | - |
| OS-EXT-SRV-ATTR:instance_name | instance-000000fc |
| OS-EXT-SRV-ATTR:kernel_id | |
| OS-EXT-SRV-ATTR:launch_index | 0 |
| OS-EXT-SRV-ATTR:ramdisk_id | |
| OS-EXT-SRV-ATTR:reservation_id | r-oq8vxghp ...

information type: Proprietary → Public
tags: added: blocker sanity
no longer affects: juniperopenstack/r3.0
Revision history for this message
Shashikiran H (skiranh) wrote :

Not seen on 12th and 14th build. Last known broken build was 6th.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.