[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

#	Subject	Branch	Project	Status	CR	V
15483,4	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	voltha-2.1	voltha-go	Status: MERGED	+2	+1
15484,4	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	master	voltha-helm-charts	Status: MERGED	+2	+1
15500,1	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	master	voltha-go	Status: MERGED	+2	+1