Issues
- Typo in Configuring Minion via confd READMENMS-15901Resolved issue: NMS-15901
- Upgrade Kafka components to 3.2.0NMS-13953Resolved issue: NMS-13953Sean Torres
- Upgrade Kafka components to 3.0.0NMS-13716Resolved issue: NMS-13716Sean Torres
- Kafka Producer - Enabling causes Trap Processing to haltNMS-13256Resolved issue: NMS-13256Chandra Gorantla
- Add required dependencies to use ZSTD inside Kafka to features.xmlNMS-12639Resolved issue: NMS-12639Sean Torres
- Wait for event forwarder to be readyNMS-11771DIGVEEJA NAIK
- Minion stops sending flow data into KafkaNMS-10831Resolved issue: NMS-10831Chandra Gorantla
7 of 7
Typo in Configuring Minion via confd README
Fixed
Description
Environment
Docker
Acceptance / Success Criteria
Kafka bundle is able to start correctly while configuring minion via confd on docker.
Created July 20, 2023 at 7:33 AM
Updated July 24, 2023 at 8:27 PM
Resolved July 24, 2023 at 8:27 PM
Activity
Show:
Benjamin ReedJuly 24, 2023 at 8:27 PM
thanks for the contribution! good catch
Devesh ChaturvediJuly 20, 2023 at 7:37 AM
Created a PR to address the issue.
As per official guide while setting up minion over docker, if we want to setup Kafka brokers for RPC or IPC using confd, the steps referred in documentation lead to failure to start kafka bundle.
The issue is due to typo in
bootstrap.serverskey name mentioned in the documentation.It is mentioned as
boostrap.serverswhile it should bebootstrap.servers. This leads to failure in starting the kafka bundle as it is not able to find the correct key in configuration.