Use logging instead of a backtrace to signal that the eucalyptus-info plugin was disabled

Bug #558494 reported by Andreas Hasenack on 2010-04-08
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Client
Low
Unassigned

Bug Description

Installed landscape-client-1.5.0~bzr229-0ubuntu0.10.04 on an eucalyptus node controller (lucid) and got this in the manager log:

2010-04-08 11:24:59,589 ERROR [MainThread] No module named imagestore.lib.service
Traceback (most recent call last):
  File "/usr/lib/python2.6/dist-packages/landscape/manager/eucalyptus.py", line 94, in send_message
    service_hub = self._service_hub_factory(data_path)
  File "/usr/lib/python2.6/dist-packages/landscape/manager/eucalyptus.py", line 165, in start_service_hub
    from imagestore.lib.service import ServiceHub
ImportError: No module named imagestore.lib.service
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 :

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.

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
Jamu Kakar (jkakar) on 2010-11-22
Changed in landscape-client:
milestone: 10.12 → later

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

Landscape Team

Changed in landscape-client:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers