contrail-database not starting after reboot

Bug #1633270 reported by Savithru Lokanath
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Won't Fix
Critical
Raj Reddy
R3.0.3.x
Won't Fix
High
Raj Reddy
R3.1
Won't Fix
High
Raj Reddy
Trunk
Won't Fix
Critical
Raj Reddy

Bug Description

Using Contrail 3.0.3 build 69 as an all-in-one setup & have a control/data separation.

Installation went smooth, but after final reboot, contrail-database service is not started during boot & as a result other services are stuck in init state.

root@a4s9:~# 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

== Contrail Control ==
supervisor-control: active
contrail-control initializing (Number of connections:4, Expected:5 Missing: IFMap:IFMapServer)
contrail-control-nodemgr active
contrail-dns active
contrail-named active

== Contrail Analytics ==
supervisor-analytics: active
contrail-alarm-gen initializing (Collector, Discovery:Collector[Subscribe - Connection Error], Discovery:AlarmGenerator[Publish Error - Status Code 503] connection down)
contrail-analytics-api initializing (Collector, UvePartitions:UVE-Aggregation[None], Discovery:AlarmGenerator[Subscribe - Connection Error], Discovery:Collector[Subscribe - Connection Error], Discovery:OpServer[Publish Error - Status Code 503] connection down)
contrail-analytics-nodemgr active
contrail-collector initializing (Database:a4s9:Global, Discovery:Collector connection down)
contrail-query-engine timeout
contrail-snmp-collector initializing (Collector, Discovery:Collector[Subscribe - Connection Error], Discovery:ApiServer[Subscribe - Status Code 503] connection down)
contrail-topology initializing (Collector, Discovery:Collector[Subscribe - Connection Error] connection down)

== Contrail Config ==
supervisor-config: active
contrail-api:0 initializing (Collector, Discovery:Collector[Subscribe - Connection Error], Database:Cassandra[] connection down)
contrail-config-nodemgr active
contrail-device-manager initializing (Collector, Discovery:Collector[Subscribe - Status Code 503], Database:Cassandra[] connection down)
contrail-discovery:0 initializing (Collector, Discovery:Collector[Subscribe - Connection Error], Database:Cassandra[] connection down)
contrail-schema initializing (Collector, Discovery:Collector[Subscribe - Status Code 503], Database:Cassandra[] connection down)
contrail-svc-monitor initializing (Collector, Database:Cassandra[], Discovery:Collector[Subscribe - Status Code 503] connection down)
ifmap active

== Contrail Web UI ==
supervisor-webui: active
contrail-webui active
contrail-webui-middleware active

== Contrail Database ==
contrail-database: inactive

== Contrail Supervisor Database ==
supervisor-database: active
contrail-database-nodemgr initializing (Cassandra state detected DOWN.)
kafka active

== Contrail Support Services ==
supervisor-support-service: active
rabbitmq-server active

information type: Proprietary → Public
description: updated
description: updated
Revision history for this message
Raj Reddy (rajreddy) wrote :

with dpdk, the ip address assignment on vhost0 takes longer and the apps binding to interface ip address instead 0.0.0.0 or 127.0.0.1, will see this issue.

since dpdk is not expected to be on controller, the fix for this is not required. And the work around is to restart contrail-database

Raj Reddy (rajreddy)
Changed in juniperopenstack:
status: New → Won't Fix
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.