Juniper Openstack

DiscoveryClient Subscribes not sent on hitting an error condition

Bug #1563002 reported by Nipa
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R2.20
Fix Committed
High
Nipa
Juniper Openstack r2.23 "r2.23"
R2.21.x
Fix Committed
High
Nipa
Juniper Openstack r2.21.2
R2.22.x
Fix Committed
High
Nipa
Juniper Openstack r2.22.2
R3.0
Fix Committed
High
Nipa
Juniper Openstack r3.0.2.0
Trunk
Fix Committed
High
Nipa
Juniper Openstack r3.1.0.0-fcs

Bug Description

Subscribes are not sent even after ttl expiry as verified by tcpdump. This happens when there is no error from Discovery Server as reported by the curl library and also there is not response to a http request.

Tags: discovery
Nipa (nipak)
Changed in juniperopenstack:
importance: Undecided → High
assignee: nobody → Nipa (nipak)
milestone: none → r3.0.1.0
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/18835
Submitter: Nipa Kumar (<email address hidden>)

Nischal Sheth (nsheth)
tags: added: discovery
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] R2.21.x

Review in progress for https://review.opencontrail.org/18913
Submitter: Nipa Kumar (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/18835
Submitter: Nipa Kumar (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/18835
Committed: http://github.org/Juniper/contrail-controller/commit/82e41b53aaf22ad0d6eab91534f2f48d53ea74d3
Submitter: Zuul
Branch: master

commit 82e41b53aaf22ad0d6eab91534f2f48d53ea74d3
Author: Nipa Kumar <email address hidden>
Date: Mon Mar 28 16:45:08 2016 -0700

DiscoveryClient stops resusbcribing even after ttl period.

On no response from discovery server and no error, subscribe timer is not restarted as
the subscribe_cb_called_ flag was not reset. Setting the flag appropriately on every
subscribe request, so subscribe timer can be restarted during the case above.

Remove unnecessary curl timeout traces, use stats counters.

Change-Id: I7afb827fe9bb8a393481bd521d02c216b711329c
Closes-Bug:1563002

Changed in juniperopenstack:
milestone: none → r3.1.0.0-fcs
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] R3.0

Review in progress for https://review.opencontrail.org/18985
Submitter: Nipa Kumar (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/18913
Committed: http://github.org/Juniper/contrail-controller/commit/5450c6af394936a9f431b52a5dd1e3df3f2fb2be
Submitter: Zuul
Branch: R2.21.x

commit 5450c6af394936a9f431b52a5dd1e3df3f2fb2be
Author: Nipa Kumar <email address hidden>
Date: Wed Mar 30 16:14:15 2016 -0700

DiscoveryClient stops resusbcribing even after ttl period.

On no response from discovery server and no error, subscribe timer is not restarted as
the subscribe_cb_called_ flag was not reset. Setting the flag appropriately on every
subscribe request, so subscribe timer can be restarted during the case above.

HeartBeat will not be effected as heartbeat timer is periodic and is
started on succesful publish.

Remove unnecessary curl timeout traces, use stats counters.

Change-Id: Iddd5a3b4f09a6c9c6fbce14878624ada622b3174
Closes-Bug:1563002

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] R2.22.x

Review in progress for https://review.opencontrail.org/18987
Submitter: Nipa Kumar (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] R2.20

Review in progress for https://review.opencontrail.org/18998
Submitter: Nipa Kumar (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/18985
Committed: http://github.org/Juniper/contrail-controller/commit/167ee74d9c1b160e0d7bc0b1ea1b9e99d4c68876
Submitter: Zuul
Branch: R3.0

commit 167ee74d9c1b160e0d7bc0b1ea1b9e99d4c68876
Author: Nipa Kumar <email address hidden>
Date: Mon Mar 28 16:45:08 2016 -0700

DiscoveryClient stops resusbcribing even after ttl period.

On no response from discovery server and no error, subscribe timer is not restarted as
the subscribe_cb_called_ flag was not reset. Setting the flag appropriately on every
subscribe request, so subscribe timer can be restarted during the case above.

Remove unnecessary curl timeout traces, use stats counters.

Change-Id: I7afb827fe9bb8a393481bd521d02c216b711329c
Closes-Bug:1563002

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote :

Reviewed: https://review.opencontrail.org/18998
Committed: http://github.org/Juniper/contrail-controller/commit/ec1df710d86cab7f86eb7895a38f2a6b5084098b
Submitter: Zuul
Branch: R2.20

commit ec1df710d86cab7f86eb7895a38f2a6b5084098b
Author: Nipa Kumar <email address hidden>
Date: Fri Apr 1 10:36:13 2016 -0700

DiscoveryClient stops resusbcribing even after ttl period.

On no response from discovery server and no error, subscribe timer is not restarted as
the subscribe_cb_called_ flag was not reset. Setting the flag appropriately on every
subscribe request, so subscribe timer can be restarted during the case above.

Remove unnecessary curl timeout traces, use stats counters.

Change-Id: Ief95c50ee91c47f8d12f6390d28c8cabca8c5ffd
Closes-Bug:1563002

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote :

Reviewed: https://review.opencontrail.org/18987
Committed: http://github.org/Juniper/contrail-controller/commit/a86a888ab355727e37790e0996b87009d6c8e16b
Submitter: Zuul
Branch: R2.22.x

commit a86a888ab355727e37790e0996b87009d6c8e16b
Author: Nipa Kumar <email address hidden>
Date: Fri Apr 1 00:02:55 2016 -0700

DiscoveryClient stops resusbcribing even after ttl period.

On no response from discovery server and no error, subscribe timer is not restarted as
the subscribe_cb_called_ flag was not reset. Setting the flag appropriately on every
subscribe request, so subscribe timer can be restarted during the case above.

Remove unnecessary curl timeout traces, use stats counters.

Change-Id: I7e35ab562896a1314c1ff30de06e673fa9e90e97
Closes-Bug:1563002

Ashish Ranjan (aranjan-n)
information type: Proprietary → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.