Profiler raises an error when it is enabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Low
|
Obed N Munoz | ||
Kilo |
Fix Released
|
Low
|
Ian Cordasco |
Bug Description
Description:
When OSProfiler is enabled in Glance API and Registry, they raise the following exception:
CRITICAL glance [-] AttributeError: 'module' object has no attribute 'messaging'
TRACE glance Traceback (most recent call last):
TRACE glance File "/usr/bin/
TRACE glance sys.exit(main())
TRACE glance File "/usr/lib/
TRACE glance notifier.messaging, {},
TRACE glance AttributeError: 'module' object has no attribute 'messaging'
TRACE glance
Steps to reproduce:
1. Enable profiler in glance-api.conf and glance-
[profiler]
enabled = True
2. Restart API and Registry Services
Expected Behavior:
Start services with profiler enabled
Changed in glance: | |
assignee: | nobody → Obed N Munoz (obed-n-munoz) |
Changed in glance: | |
importance: | Undecided → Low |
tags: | added: kilo-backport-potential |
Changed in glance: | |
status: | In Progress → Fix Committed |
Changed in glance: | |
status: | Fix Committed → Fix Released |
Changed in glance: | |
milestone: | liberty-2 → 11.0.0 |
no longer affects: | glance/liberty |
Change abandoned by Ian Cordasco (<email address hidden>) on branch: master /review. openstack. org/194725
Review: https:/
Reason: Incomplete duplicate. Abandoning in favor of a newer version by the original bug reporter