Bug 1515969
| Summary: | Ceilometer can't find nova instance because of name differences | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Pradeep Kilambi <pkilambi> |
| Component: | openstack-tripleo-heat-templates | Assignee: | Pradeep Kilambi <pkilambi> |
| Status: | CLOSED ERRATA | QA Contact: | Sasha Smolyak <ssmolyak> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 10.0 (Newton) | CC: | berrange, cchen, dasmith, djuran, dvd, eglynn, ipilcher, jdanjou, jniu, jruzicka, jschluet, kchamart, marjones, mburns, mlopes, mzheng, owalsh, pablo.iranzo, pkilambi, pkundal, rhel-osp-director-maint, sbauza, sferdjao, sgordon, srevivo, ssmolyak, svanders, tvignaud, vromanso |
| Target Milestone: | z7 | Keywords: | Triaged, ZStream |
| Target Release: | 10.0 (Newton) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-tripleo-heat-templates-5.3.3-3.el7ost, puppet-ceilometer-9.5.0-3.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Previously, Ceilometer would not set the hostname in its configuration file, and used the default detected one. Consequently, in certain cases, Nova would override the default detected hostname with a custom hostname which would not match the Ceilometer auto-detected one. This would leave Ceilometer unable to poll for Nova instances statistics. With this update, Ceilometer now sets the same hostname that Nova sets. As a result, Ceilometer is now able to poll Nova instances correctly.
|
Story Points: | --- |
| Clone Of: | 1483456 | Environment: | |
| Last Closed: | 2018-02-27 16:50:40 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: | |||
| Bug Depends On: | 1483456 | ||
| Bug Blocks: | |||
|
Comment 6
Meiyan Zheng
2018-02-09 01:10:46 UTC
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/RHBA-2018:0364 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days |