Bug #14969
closed
Custom status is not reloaded correctly
Added by Marek Hulán over 8 years ago.
Updated over 6 years ago.
Category:
Plugin integration
|
Description
If a custom status is registered from a plugin and user is running Foreman in development mode, status class is not correctly reloaded in HostStatus.status_registry. When we later iterate over it, status is missing there and is not refreshed. To reproduce, install e.g. remote execution plugin and try to do some change in code. After another job invocation, the status is not updated (good place to observe with pry is finalize method of RunHostJob action)
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3508 added
- Related to Refactor #12747: Provide some kind of central store or consistent way to manage dynamically registered objects from plugins added
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Blocked by Feature #14588: Improve extending template helpers from plugin added
- Translation missing: en.field_release set to 136
Also available in: Atom
PDF