Skip to content
This repository has been archived by the owner on Dec 4, 2023. It is now read-only.

Agent watches may not reconnect in response to certain connection problems #4131

Closed
k-wall opened this issue Mar 17, 2020 · 0 comments · Fixed by #4132 or #4157
Closed

Agent watches may not reconnect in response to certain connection problems #4131

k-wall opened this issue Mar 17, 2020 · 0 comments · Fixed by #4132 or #4157
Labels
component/agent kind/bug
Milestone
0.31.0

Comments

@k-wall
Copy link
Member

k-wall commented Mar 17, 2020 •
edited

Describe the bug

The Agent uses Kubernetes 'watches' to track the state of kubernetes resources such as pods, addresses, etc. The intent is that the watches automatically reestablish in the event of a connection error or timeout.

There is a defect in the connection error handling that means the watch is not reestablished in all situations.

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.
k-wall added a commit to k-wall/enmasse that referenced this issue Mar 17, 2020
@k-wall
Fix EnMasseProject#4131: Ensure the watch is restarted on all paths (…
b8ac3d9 
…including initial connection refused etc).
@k-wall k-wall linked a pull request Mar 17, 2020 that will close this issue
Fix #4131: Ensure the watch is restarted on all paths #4132
Merged
7 tasks
lulf pushed a commit to lulf/enmasse that referenced this issue Mar 17, 2020
@k-wall @lulf
Fix EnMasseProject#4131: Ensure the watch is restarted on all paths (…
aa60073 
…including initial connection refused etc).
k-wall added a commit that referenced this issue Mar 18, 2020
@k-wall
Fix #4131: Ensure the watch is restarted on all paths (#4132)
34f83b7 
* Fix #4131: Ensure the watch is restarted on all paths (including initial connection refused etc).
* add unit test
@k-wall k-wall added this to the 0.31 milestone Mar 18, 2020
k-wall added a commit that referenced this issue Mar 18, 2020
@k-wall
Fix #4131: Ensure the watch is restarted on all paths (#4132)
95b3072 
* Fix #4131: Ensure the watch is restarted on all paths (including initial connection refused etc).
* add unit test
k-wall added a commit that referenced this issue Mar 18, 2020
@k-wall
Fix #4131: Ensure the watch is restarted on all paths (#4132)
a463c8d 
* Fix #4131: Ensure the watch is restarted on all paths (including initial connection refused etc).
* add unit test
@k-wall k-wall modified the milestones: 0.31, 0.30.3 Mar 18, 2020
@k-wall k-wall linked a pull request Mar 20, 2020 that will close this issue
Test verifying Agent's behaviour when connection to the Kubernetes API server is lost #4157
Merged
7 tasks
jbtrystram pushed a commit to jbtrystram/enmasse that referenced this issue Mar 30, 2020
@k-wall @jbtrystram
Fix EnMasseProject#4131: Ensure the watch is restarted on all paths (E…
e6884d7 
…nMasseProject#4132)

* Fix EnMasseProject#4131: Ensure the watch is restarted on all paths (including initial connection refused etc).
* add unit test
drcoolsanjeev pushed a commit to drcoolsanjeev/enmasse that referenced this issue Apr 6, 2020
@k-wall @drcoolsanjeev
Fix EnMasseProject#4131: Ensure the watch is restarted on all paths (E…
82c651a 
…nMasseProject#4132)

* Fix EnMasseProject#4131: Ensure the watch is restarted on all paths (including initial connection refused etc).
* add unit test
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
component/agent kind/bug
Projects
None yet
Milestone
0.31.0
1 participant
@k-wall