starting monasca-notification service error

Bug #1591085 reported by Seungkyu Ahn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Monasca
In Progress
Undecided
Seungkyu Ahn

Bug Description

When starting monasca-notification service, you'll meet following error.

========================== log ==========================================================

Jun 10 17:33:30 controller01 systemd[1]: Started Monasca Notification Service.
Jun 10 17:33:31 controller01 python[26848]: Traceback (most recent call last):
Jun 10 17:33:31 controller01 python[26848]: File "/usr/local/bin/monasca-notification", line 10, in <module>
Jun 10 17:33:31 controller01 python[26848]: sys.exit(main())
Jun 10 17:33:31 controller01 python[26848]: File "/opt/stack/monasca-notification/monasca_notification/main.py", line 110, in main
Jun 10 17:33:31 controller01 python[26848]: if 60 in config['kafka']['periodic']:
Jun 10 17:33:31 controller01 python[26848]: KeyError: 'periodic'
Jun 10 17:33:31 controller01 systemd[1]: monasca-notification.service: Main process exited, code=exited, status=1/FAILURE
Jun 10 17:33:31 controller01 systemd[1]: monasca-notification.service: Unit entered failed state.
Jun 10 17:33:31 controller01 systemd[1]: monasca-notification.service: Failed with result 'exit-code'.

Seungkyu Ahn (seungkyua)
Changed in monasca:
assignee: nobody → Seungkyu Ahn (seungkyua)
status: New → In Progress
Revision history for this message
jobrs (joachim-barheine) wrote :

Probably missing "periodic" attribute in your config? It has been added as mandatory recently.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.