Bug #22918
closed
mgr sends early beacon with no modules reported
Added by John Spray about 6 years ago.
Updated over 3 years ago.
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.
- Copied to Backport #22919: luminous: mgr sends early beacon with no modules reported added
- Copied to deleted (Backport #22919: luminous: mgr sends early beacon with no modules reported)
Deleted the "copied to" link because it was created by mistake, and we might want to backport this fix in the future.
- Status changed from In Progress to Pending Backport
- Backport set to luminous
- Copied to Backport #23416: luminous: mgr sends early beacon with no modules reported added
- Pull request ID set to 20321
- 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".
Also available in: Atom
PDF