Use logging instead of a backtrace to signal that the eucalyptus-info plugin was disabled
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Landscape Client |
Invalid
|
Low
|
Unassigned | ||
Bug Description
Installed landscape-
2010-04-08 11:24:59,589 ERROR [MainThread] No module named imagestore.
Traceback (most recent call last):
File "/usr/lib/
service_hub = self._service_
File "/usr/lib/
from imagestore.
ImportError: No module named imagestore.
2010-04-08 11:24:59,590 INFO [MainThread] Couldn't start service hub. 'eucalyptus-info' plugin has been disabled.
Do we have a missing dependency in the package?
| Changed in landscape: | |
| milestone: | none → 1.5.0 |
| affects: | landscape → landscape-client |
| Changed in landscape-client: | |
| milestone: | 1.5.0 → none |
| visibility: | private → public |
| Changed in landscape-client: | |
| milestone: | none → 1.5.0 |
| importance: | Undecided → Medium |
| Changed in landscape-client: | |
| importance: | Medium → Low |
| Andreas Hasenack (ahasenack) wrote | #1 |
| tags: | added: testing |
| tags: | removed: testing |
| tags: | added: needs-testing |
| Changed in landscape-client: | |
| milestone: | 1.5.0 → 1.5.1 |
| tags: | removed: needs-testing |
| summary: |
- eucalyptus-info plugin disabled due to missing module + Use logging instead of a backtrace to signal eucalyptus-info plugin was + disabled |
| summary: |
- Use logging instead of a backtrace to signal eucalyptus-info plugin was - disabled + Use logging instead of a backtrace to signal that the eucalyptus-info + plugin was disabled |
| Changed in landscape-client: | |
| milestone: | 1.5.1 → 1.5.2 |
| Changed in landscape-client: | |
| milestone: | 1.5.2 → 1.5.3 |
| Changed in landscape-client: | |
| milestone: | 1.5.3 → 1.5.4 |
| Changed in landscape-client: | |
| milestone: | 1.5.4 → 1.5.5 |
| Changed in landscape-client: | |
| milestone: | 1.5.5 → 1.5.6 |
| Changed in landscape-client: | |
| milestone: | 1.5.6 → 1.6.0 |
| Changed in landscape-client: | |
| milestone: | 1.6.0 → 10.11 |
| Changed in landscape-client: | |
| milestone: | 10.11 → 10.12 |
| Changed in landscape-client: | |
| milestone: | 10.12 → later |
| 🤖 Landscape Builder (landscape-builder) wrote | #2 |
| Changed in landscape-client: | |
| status: | New → Invalid |
Therve explained that this is expected, and that the plugin should really be disabled on that machine. So this bug is now about not having a backtrace in the logs when this happens, but just perhaps a warning message saying that the plugin was automatically disabled because this is not a cloud controller or something like that.