[Ubuntu 14.04 LTS" 2.10-24~juno] vrouter core seen after service chain with transparent firewall and in-network analyzer is configured
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.1 |
Fix Released
|
High
|
Naveen N | |||
Trunk |
Fix Released
|
High
|
Naveen N |
Bug Description
1]. Setup:
========
env.roledefs = {
'all': [host1, host2, host3, host4, host5],
'cfgm': [host1],
'control': [host2, host3],
'compute': [host4, host5],
'collector': [host1],
'openstack': [host1],
'webui': [host1],
'database': [host1],
'build': [host_build],
}
env.hostnames = {
'all': ['nodec4', 'nodec5', 'nodec26', 'nodei27', 'nodei28']
}
2]. Steps
=======
Created a service chain between two networks. It had a transparent firewall and a in-network analyser.
Ping between the end-VMs was failing.
On the analyser VM, started-stopped packet capture for a couple of times.
Core
====
Core was generated by `/usr/bin/
Program terminated with signal 6, Aborted.
#0 0x00007fb2da5dbbb9 in ?? ()
Missing separate debuginfos, use: debuginfo-install glibc-2.
(gdb) bt
#0 0x00007fb2da5dbbb9 in ?? ()
#1 0x00007fb2da5defc8 in ?? ()
#2 0x0000000000000020 in ?? ()
#3 0x0000000000000000 in ?? ()
(gdb) quit
Attached the logs and cores at :/homes/
Changed in juniperopenstack: | |
milestone: | r2.1-fcs → none |
tags: | added: blocker vrouter |
tags: | removed: blocker |
information type: | Proprietary → Public |
Changed in juniperopenstack: | |
status: | New → Fix Released |
Seen in the sanity runs on 2.1-26 as well