Actions
Bug #22918
closedmgr sends early beacon with no modules reported
% Done:
0%
Source:
Tags:
Backport:
luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Description
Sends beacon before PyModuleRegistry::init has been called -- if admin quickly does a "mgr module enable" after daemon start, it can fail with "all mgrs do not have module xyz". Manifests as intermittent automated test failure.
Updated by John Spray about 6 years ago
- Copied to Backport #22919: luminous: mgr sends early beacon with no modules reported added
Updated by Nathan Cutler about 6 years ago
Updated by Nathan Cutler about 6 years ago
- Copied to deleted (Backport #22919: luminous: mgr sends early beacon with no modules reported)
Updated by Nathan Cutler about 6 years ago
Deleted the "copied to" link because it was created by mistake, and we might want to backport this fix in the future.
Updated by Kefu Chai about 6 years ago
- Status changed from In Progress to Pending Backport
- Backport set to luminous
Updated by Nathan Cutler about 6 years ago
- Copied to Backport #23416: luminous: mgr sends early beacon with no modules reported added
Updated by Nathan Cutler about 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions