broker can't connect to other processes because the registry setup isn't being imported

Bug #1180584 reported by Christopher Armstrong
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Client
Fix Released
High
Unassigned

Bug Description

Recently some code in landscape-client got refactored to remove an "import" of landscape.broker.amp, which set up a global registry of components that the broker connects to. Now that that import is gone, the registry isn't being set up, and the broker fails to connect to the components on startup.

Related branches

Changed in landscape-client:
milestone: 13.05 → 13.06
Changed in landscape-client:
milestone: 13.06 → 13.07
Changed in landscape-client:
assignee: Christopher Armstrong (radix) → nobody
Changed in landscape-client:
milestone: 13.07 → 13.08
Changed in landscape-client:
milestone: 13.08 → 13.09
Changed in landscape-client:
milestone: 13.09 → 13.09.1
Changed in landscape-client:
milestone: 13.09.1 → 13.10
Changed in landscape-client:
milestone: 13.10 → 13.11
Changed in landscape-client:
milestone: 13.11 → 13.12
Changed in landscape-client:
milestone: 13.12 → 14.01
Changed in landscape-client:
milestone: 14.01 → 14.02
Changed in landscape-client:
status: In Progress → Fix Committed
Changed in landscape-client:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.