Juniper Openstack

DPDK: After a crash agent is stuck in init state

Bug #1569639 reported by Vinod Nair on 2016-04-13

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Juniper Openstack	Fix Committed	High	Raja Sivaramakrishnan	Juniper Openstack r3.1.0.0-fcs
	R3.0	Fix Committed	High	Raja Sivaramakrishnan	Juniper Openstack r3.0.2.0

Bug Description

After a agent crash , agent is stuck in init state

root@cs-scale-6:/var/crashes# contrail-status
== Contrail vRouter ==
supervisor-vrouter: active
contrail-vrouter-agent initializing (Collector, Discovery:Collector, Discovery:dns-server, Discovery:xmpp-server connection down)
contrail-vrouter-dpdk active
contrail-vrouter-nodemgr active

Cluster has dpdk on bond / vlans

Agent log is attached

Version: 3.0.2.0-26~kilo

See original description

Tags:

Revision history for this message

Vinod Nair (vinodnair) wrote on 2016-04-13:

agent log Edit (541.0 KiB, text/html)

description:

updated

Jeba Paulaiyan (jebap) on 2016-04-15

Changed in juniperopenstack:
milestone:	none → r3.1.0.0-fcs
tags:	added: blocker vrouter

Jeba Paulaiyan (jebap) on 2016-05-04

information type:

Proprietary → Public

Revision history for this message

Vinod Nair (vinodnair) wrote on 2016-05-27:

This issue is not seen in build 3.0.2.43 Kilo, after manually crashing the agent with kill -3

Changed in juniperopenstack:
status:	New → Fix Committed
tags:	removed: blocker

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

agent log Edit

Add attachment

Remote bug watches

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