3.1.3-75:Potential bug in restore_cassandra_db
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.1 |
Fix Committed
|
High
|
Megh Bhatt | |||
R3.2 |
Fix Committed
|
High
|
Megh Bhatt | |||
R4.0 |
Fix Committed
|
High
|
Megh Bhatt | |||
Trunk |
Fix Committed
|
High
|
Megh Bhatt |
Bug Description
Contrail Version: 3.1.3-75~mitaka
We have noticed that whenever we run `fab stop_collector` after `fab stop_database`, at times, the task doesn’t end and contrail-
Connect attempt to <BrokerConnection host=192.168.0.131 port=9092> returned error 111. Disconnecting.
Skipping unconnected connection: <BrokerConnection host=192.168.0.131 port=9092>
Connect attempt to <BrokerConnection host=192.168.0.133 port=9092> returned error 111. Disconnecting.
Skipping unconnected connection: <BrokerConnection host=192.168.0.133 port=9092>
Connect attempt to <BrokerConnection host=192.168.0.132 port=9092> returned error 111. Disconnecting.
Skipping unconnected connection: <BrokerConnection host=192.168.0.132 port=9092>
FailedPayloadsError for -uve-5:0
There are 2 functions in our code that uses this order:
def restore_
def stop_contrail_
So, whenever this is run, there is a manual intervention that is required to get things back up and running. We don’t see this, when we change the order as below:
def restore_
<snip>
try:
execute(stop_cfgm)
execute(
execute(
#execute(
execute(
execute(start_cfgm)
execute(
execute(
root@sv-
(Finished without manual intervention.)
I am in discussion with Megh Bhatt from BU on this. He is aware of this and has the relevant logs and info. This bug is filed for tracking purposes.
information type: | Proprietary → Public |
Changed in juniperopenstack: | |
importance: | Undecided → High |
assignee: | nobody → Megh Bhatt (meghb) |
milestone: | none → r3.1.4.0 |
tags: | added: analytics |
Analytics Team - We need to speed up the progress on this. Can I please get an update?
-Sandeep.