contrail-database not starting after reboot
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-
contrail-
contrail-
== Contrail Control ==
supervisor-control: active
contrail-control initializing (Number of connections:4, Expected:5 Missing: IFMap:IFMapServer)
contrail-
contrail-dns active
contrail-named active
== Contrail Analytics ==
supervisor-
contrail-alarm-gen initializing (Collector, Discovery:
contrail-
contrail-
contrail-collector initializing (Database:
contrail-
contrail-
contrail-topology initializing (Collector, Discovery:
== Contrail Config ==
supervisor-config: active
contrail-api:0 initializing (Collector, Discovery:
contrail-
contrail-
contrail-
contrail-schema initializing (Collector, Discovery:
contrail-
ifmap active
== Contrail Web UI ==
supervisor-webui: active
contrail-webui active
contrail-
== Contrail Database ==
contrail-database: inactive
== Contrail Supervisor Database ==
supervisor-
contrail-
kafka active
== Contrail Support Services ==
supervisor-
rabbitmq-server active
information type: | Proprietary → Public |
description: | updated |
description: | updated |
Changed in juniperopenstack: | |
status: | New → Won't Fix |
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