redhat-osp10-mainline3073:contrail-status shows api failed
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R4.0 |
Fix Committed
|
High
|
Nagendra Prasath | |||
Trunk |
Fix Committed
|
High
|
Nagendra Prasath |
Bug Description
Even after restart service didn't come up.
controller, analytics and analyticsdb are in containers and redhat openstack on separate node
[root@a5s10 ~]# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
d67332db3872 68844dbde56a "/lib/systemd/
8970ef3a4f43 247625e51067 "/lib/systemd/
fe9cc2180f85 d7587cd3943b "/lib/systemd/
[root@a5s10 ~]#
[root@a5s10 ~]#
[root@a5s10 ~]# docker exec -it d67332db3872 bash
root@a5s10(
root@a5s10(
exit
[root@a5s10 ~]# docker exec -it fe9cc2180f85 bash
root@a5s10(
root@a5s10(
== Contrail Control ==
supervisor-control: active (disabled on boot)
contrail-control active
contrail-
contrail-dns active
contrail-named active
== Contrail Config ==
supervisor-config: active (disabled on boot)
contrail-api:0 failed
contrail-
contrail-
contrail-schema active
contrail-
== Contrail Web UI ==
supervisor-webui: active (disabled on boot)
contrail-webui active
contrail-
== Contrail Database ==
contrail-database: active (disabled on boot)
supervisor-
unix://
root@a5s10(
Package Version Build-ID | Repo | RPM Name
-------
contrail-config 4.0.0.0-3073.el7 @contrail-
contrail-
contrail-control 4.0.0.0-3073.el7 @contrail-
contrail-database 4.0.0.0-3073.el7 @contrail-
contrail-
contrail-dns 4.0.0.0-3073.el7 @contrail-
contrail-lib 4.0.0.0-3073.el7 @contrail-
root@a5s10(
● contrail-
Loaded: loaded (/etc/systemd/
Active: active (running) since Mon 2017-05-08 21:38:19 UTC; 52min ago
Process: 29455 ExecStop=/bin/kill -s TERM $MAINPID (code=exited, status=1/FAILURE)
Main PID: 29464 (contrail-api)
CGroup: /docker/
└─29464 /usr/bin/python /usr/bin/
‣ 29464 /usr/bin/python /usr/bin/
May 08 22:29:41 a5s10 contrail-
May 08 22:29:41 a5s10 contrail-
May 08 22:30:06 a5s10 contrail-
May 08 22:30:07 a5s10 contrail-
May 08 22:30:07 a5s10 contrail-
May 08 22:30:07 a5s10 contrail-
May 08 22:30:14 a5s10 contrail-
May 08 22:30:14 a5s10 contrail-
May 08 22:30:15 a5s10 contrail-
May 08 22:30:15 a5s10 contrail-
Hint: Some lines were ellipsized, use -l to show in full.
root@a5s10(
● cassandra.service - SYSV: Starts and stops Cassandra
Loaded: loaded (/etc/rc.
Active: active (exited) since Mon 2017-05-08 20:47:38 UTC; 1h 43min ago
Docs: man:systemd-
May 08 20:47:37 a5s10 systemd[1]: Starting SYSV: Starts and stops Cassandra...
May 08 20:47:37 a5s10 su[2563]: (to cassandra) root on none
May 08 20:47:38 a5s10 cassandra[2556]: Starting Cassandra: OK
May 08 20:47:38 a5s10 systemd[1]: Started SYSV: Starts and stops Cassandra.
information type: | Proprietary → Public |
description: | updated |
tags: | added: blocker |
tags: | removed: blocker |
tags: | added: blocker |
I looked at the setup. It seems the api server and cassandra are both running, but systemd still tried to launch them again and then it failed with addres 8084 already bound.