Bug 1284058
| Summary: | swift is using deprecated ceilometer middleware | |||
|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Derek Higgins <derekh> | |
| Component: | openstack-puppet-modules | Assignee: | Pradeep Kilambi <pkilambi> | |
| Status: | CLOSED ERRATA | QA Contact: | Yurii Prokulevych <yprokule> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | 7.0 (Kilo) | CC: | dnavale, egafford, fbaudin, hbrock, jcoufal, jschluet, mburns, mfuruta, nkrishna, pkilambi, rhel-osp-director-maint, sacpatil, srevivo | |
| Target Milestone: | rc | Keywords: | Triaged | |
| Target Release: | 10.0 (Newton) | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | openstack-tripleo-heat-templates-5.0.0-0.9.0rc3.el7ost | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, Object Storage service deployed using the director used ceilometer middleware that had been deprecated since the Red Hat OpenStack Platform 8 (liberty) release.
With this update, the Object Storage service has been fixed to use the ceilometer middleware from python-ceilometermiddleware which is the supported version for this release.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1374871 (view as bug list) | Environment: | ||
| Last Closed: | 2016-12-14 15:18:35 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: | ||||
| Bug Blocks: | 1374871 | |||
|
Description
Derek Higgins
2015-11-20 16:44:14 UTC
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10. This is the reason why following meters are not displayed/available? - storage.objects.outgoing.bytes - storage.objects.incoming.bytes -- Sachin @Hugh, I don't see much activity, are you still working on this bug? 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://rhn.redhat.com/errata/RHEA-2016-2948.html |