contrail-analytics-api in initializing (ApiServer connection down) after upgrade from r3.1.2.0
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Juniper Openstack | Status tracked in Trunk | |||||
| R3.2 |
Invalid
|
High
|
wenqing liang | |||
| Trunk |
Invalid
|
High
|
wenqing liang | |||
Bug Description
After upgrade of a centos 7.2 cluster from r3.1.2.0-62 to r3.2.3.0-37~mitaka, a collector core was seen and contrail-
[root@b7s32 log]# contrail-status
== Contrail Control ==
supervisor-control: active
contrail-control active
contrail-
contrail-dns active
contrail-named active
== Contrail Analytics ==
supervisor-
contrail-
contrail-
contrail-
contrail-collector active
contrail-
contrail-
contrail-topology active
== Contrail Config ==
supervisor-config: active
contrail-api:0 active
contrail-
contrail-
contrail-
contrail-schema backup
contrail-
ifmap active
== Contrail Database ==
contrail-database: active
== Contrail Supervisor Database ==
supervisor-
contrail-
kafka active
========Run time service failures=
/var/crashes/
[root@b7s32 log]#
[root@b4s44 1687123]# pwd
/cs-shared/
[root@b4s44 1687123]# ls
core.contrail-
[root@b4s44 1687123]#
| description: | updated |
| Jeba Paulaiyan (jebap) wrote | #1 |
| wenqing liang (wliang) wrote | #2 |
There was an user error while executing this test. The cluster was provisioned with SSL+Keystone v3 mode. However, while upgrading proper env variables are not passed to the fab script. Due to this the upgrade fab command executed in non-SSL mode. Wenqing is re-executing the test.