duplicate, incomplete ToR config causing Tor-agent connection to be down
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
High
|
Hari Prasad Killi | |||
Trunk |
Fix Committed
|
High
|
Hari Prasad Killi |
Bug Description
R2.20 Build 108 Ubuntu 14.04 Juno
On this multi-node setup, The tor-agents were not up.
Hari and Ashok analyzed that it was due to the order of configs got for the ToR.
It seems initially, the ToR config was got without the ToR name and got an update (with the name) later.
The later update caused a second tor-config to be created instead of updating the existing one (See attachment)
Gcore will be in http://
root@nodek3:~# contrail-status
== Contrail vRouter ==
supervisor-vrouter: active
contrail-
contrail-
contrail-
contrail-
Review in progress for https:/ /review. opencontrail. org/15335
Submitter: Hari Prasad Killi (<email address hidden>)