tor-agent did not connect to TOR on TOR-reboot
Bug #1413092 reported by
Vedamurthy Joshi
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Juniper Openstack |
Fix Committed
|
High
|
Prabhjot Singh Sethi | ||
| R2.1 |
Fix Committed
|
High
|
Prabhjot Singh Sethi | ||
Bug Description
R2.1 Build 6 Ubuntu 14.04 Multi-node setup
TOR qfx1 which was managed by tor-agent was upgraded and rebooted.
It was seen after the TOR came up, tor-agent did not reconnect to TOR at all.
The ovsdb client session was stuck in reconnecting. Prabhjot is aware of this
http://
protocol
TCP
server
10.204.217.38
port
9999
tor_service_node
10.204.217.51
sessions
sessions
status
Reconnecting
| tags: | added: blocker |
Revision history for this message
| OpenContrail Admin (ci-admin-f) wrote A change has been merged | #1 |
Revision history for this message
| OpenContrail Admin (ci-admin-f) wrote | #2 |
| Changed in juniperopenstack: | |
| status: | New → Fix Committed |
To post a comment you must log in.
Reviewed: https:/
Committed: http://
Submitter: Zuul
Branch: R2.1
commit 97a72f72d40b868
Author: Prabhjot Singh Sethi <email address hidden>
Date: Wed Jan 21 05:45:43 2015 -0800
Tor-Agent reconnect failure.
Issue:
reconnect timer and onsessionevent were not running in
exclusion to each other, cause timer start to fail when it is
already in fired state.
Fix:
adding task context to the timer, and moving processing of
session events to a workqueue.
Also correcting task instance for receive work queue and
sandesh callbacks for http introspect.
Closes-bug:#1413092
Change-Id: I6ca60104b73f6d