-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Medium
-
Resolution: Fixed
-
Affects Version/s: VOLTHA v2.7
-
Fix Version/s: VOLTHA v2.8
-
Component/s: kafka
-
Labels:None
-
Environment:
kind voltha with external kafka access via EXTRA helm flags:
EXTRA_HELM_FLAGS=" --set externalAccess.enabled=true,externalAccess.service.type=NodePort,externalAccess.service.nodePorts[0]=30201,externalAccess.service.domain=127.0.0.1 "
and port forwarding:
kubectl port-forward --address 0.0.0.0 --namespace default svc/kafka-0-external 30201:9094
kind voltha with external kafka access via EXTRA helm flags: EXTRA_HELM_FLAGS=" --set externalAccess.enabled=true,externalAccess.service.type=NodePort,externalAccess.service.nodePorts [0] =30201,externalAccess.service.domain=127.0.0.1 " and port forwarding: kubectl port-forward --address 0.0.0.0 --namespace default svc/kafka-0-external 30201:9094
-
Story Points:3
Timestamp of kafka records contain wrong timestamp:
'timestamp': '1969-12-31 23:59:59.999000',
'timestamp_sec': -1,
'topic': 'voltha.events'},
This is valid for all records.
- blocks
-
VOL-3703
Performance Monitoring Attributes test
-
- Resolved
-
