Bug 1559093
Summary: | ceilometer event-list empty with event_dispatchers=gnocchi | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Serena Cortopassi <scortopa> |
Component: | openstack-tripleo-heat-templates | Assignee: | Pradeep Kilambi <pkilambi> |
Status: | CLOSED ERRATA | QA Contact: | Sasha Smolyak <ssmolyak> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 10.0 (Newton) | CC: | jruzicka, mburns, pkilambi, rhel-osp-director-maint, srevivo |
Target Milestone: | z8 | Keywords: | Reopened, Triaged, ZStream |
Target Release: | 10.0 (Newton) | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | openstack-tripleo-heat-templates-5.3.8-10.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-17 15:40:56 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Serena Cortopassi
2018-03-21 16:53:56 UTC
In OSP10, ceilometer still uses mongodb to store events. So you should include event_dispatcher=database for ceilometer api to get the events. Thanks, so if I understand I have to add event_dispatcher=database in ceilometer.conf and restart all ceilometer services? Something else? Why did the director not include that config in deployment if it is required in OSP10? Thanks a lot (In reply to Serena Cortopassi from comment #2) > Thanks, so if I understand I have to add event_dispatcher=database in > ceilometer.conf and restart all ceilometer services? Something else? > > Why did the director not include that config in deployment if it is required > in OSP10? > > Thanks a lot Interesting, director should have defaulted to database. Seems like this was recently changed, causing this issue you're seeing. I'm re-opening this bug and we can fix the director accordingly. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:1593 |