Bug 1073408
| Summary: | samples from notifications for autoscaled instances cannot be persisted in mongo | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Eoghan Glynn <eglynn> | ||||
| Component: | openstack-ceilometer | Assignee: | Eoghan Glynn <eglynn> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Ami Jeain <ajeain> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.0 | CC: | ajeain, ddomingo, eglynn, jruzicka, pbrady, sclewis, sdake, yeylon | ||||
| Target Milestone: | z4 | Keywords: | OtherQA, ZStream | ||||
| Target Release: | 4.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | openstack-ceilometer-2013.2.2-5.el6ost | Doc Type: | Bug Fix | ||||
| Doc Text: |
Previously, the structure of user metadata in notifications for autoscales instances were unsuitable for persisting in MongoDB. As a result, any samples generated from such notifications were effectively dropped.
The mapping logic for pollster-originated samples ensures that user metadata is suitable for persisting in MongoDB. With this release, this same mapping logic is used for user metadata for samples derives from instance-related notifications. This, in turn, helps ensure that the data persists in MongoDB, thereby preventing the notifications from being dropped.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-05-29 19:58:34 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: | |||||||
| Attachments: |
|
||||||
|
Description
Eoghan Glynn
2014-03-06 11:46:10 UTC
Fix proposed to master upstream: https://review.openstack.org/77959 adjusting priority/severity to indicate this is something that we should be working on. Fix landed on master upstream: https://github.com/openstack/ceilometer/commit/ddeb54bb and proposed to stable/havana upstream: https://review.openstack.org/84096 also backported internally: https://code.engineering.redhat.com/gerrit/22363 Internal backport has landed on rhos-4.0-rhel-6-patches with SHA: 1e4963cd6fef1c1e9fdec6336baab6f1f37f3fed OtherQA ======= 1. Download rebuilt RPMs: https://brewweb.devel.redhat.com/buildinfo?buildID=348179 2. Upgrade ceilometer packages: $ SUFF=2013.2.2-5.el6ost.noarch.rpm $ for p in openstack-ceilometer-alarm openstack-ceilometer-api openstack-ceilometer-central openstack-ceilometer-collector openstack-ceilometer-common openstack-ceilometer-compute python-ceilometer do sudo yum upgrade -y $p-$SUFF done 3. Stop the ceilometer services: $ CEILO_SVCS='compute central collector api alarm-evaluator alarm-notifier' $ for svc in $CEILO_SVCS ; do sudo service openstack-ceilometer-$svc stop ; done 4. Archive the collector log file: $ sudo gzip -S $(date "+%FT%T").gz /var/log/ceilometer/collector.log 5. Restart the ceilometer services: $ CEILO_SVCS='compute central collector api alarm-evaluator alarm-notifier' $ for svc in $CEILO_SVCS ; do sudo service openstack-ceilometer-$svc start ; done 6. Create a Heat stack with autoscaling enabled and wait for creation to complete: $ heat stack-create test_stack --template-file=./template.yaml --parameters="KeyName=userkey;ImageId=$CIRROS_AMI" $ watch "heat stack-list" 7. Wait for newly spun-up instances to become ACTIVE: $ watch "nova list | grep ACTIVE" 8. Ensure "not okForStorage" error is not emiited $ sudo grep "not okForStorage" /var/log/ceilometer/collector.log 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. http://rhn.redhat.com/errata/RHBA-2014-0577.html |