[VOL-1995] Device monitoring for setting affinity to the backend is broken in arouterd - OpenCORD JIRA

XML

Word

Printable

Details

Type: Bug
Status: Resolved (View Workflow)
Priority: Medium
Resolution: Fixed
Affects Version/s: None
Fix Version/s: VOLTHA v2.1
Component/s: api-server
Labels:
- stabilization

Story Points:
2
Epic Link:
Maintenance

Description

The device monitoring thread is not started now in afrouter daemon because of a failure in starting kafka client for receiving device create notifications.

This results in no backend affinity being set on device creation in afrouter.

Attachments

Options
- Issue Only
- Show All Reviews
- Show Open Reviews
- Show All Issues
- Show Open Issues

Gerrit Reviews

No reviews matched the request. Check your Options in the drop-down menu of this sections header.

Activity

People

Assignee:: Karthick Ramanarayanan

Reporter:: Karthick Ramanarayanan

Watchers:: 1 Start watching this issue

Dates

Created:: 2019/09/30 4:17 PM

Updated:: 2019/10/01 1:31 PM

Resolved:: 2019/10/01 1:31 PM

Gerrit Reviews

There are no open Gerrit changes

Show There are 3 closed Gerrit changes

Hide There are 3 closed Gerrit changes

VOL-1995: Enable device monitoring in arouterd. It was skipped when kafka wasn't ready to listen to device notifications during startup. Bumping version to dev for jenkins tag-collision test. Keep trying to connect to kafka forever on failure. Try connecting to kafka as soon as possible without delaying even for first time. This will ensure faster restarts when api-server pod is restarted with kafka pod already up. Change-Id: I7433f3bd7d038e41388c84003b7db26a8eda17e6: Gerrit Review:

VOL-1995: Set kafka topic env used to subscribe to device discovery notifications. Update Chart version. Provide value overrides for the kafka topic in api-server Remove stale editor backup file. Change-Id: I6be300875b414c1731323ee826358769766dc581: Gerrit Review:

VOL-1995: Enable device monitoring in arouterd. It was skipped when kafka wasn't ready to listen to device notifications during startup. Bumping version to dev for jenkins tag-collision test. Keep trying to connect to kafka forever on failure. Try connecting to kafka as soon as possible without delaying even for first time. This will ensure faster restarts when api-server pod is restarted with kafka pod already up. Change-Id: I7433f3bd7d038e41388c84003b7db26a8eda17e6: Gerrit Review: