Actions
Bug #14969
closed
Custom status is not reloaded correctly
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)
Updated by The Foreman Bot over 8 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3508 added
Updated by Dominic Cleal over 8 years ago
- Related to Refactor #12747: Provide some kind of central store or consistent way to manage dynamically registered objects from plugins added
Updated by Marek Hulán over 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 670184e1f4705e610a48edf42a3001ca2cf2f011.
Updated by Dominic Cleal over 8 years ago
- Blocked by Feature #14588: Improve extending template helpers from plugin added
Updated by Dominic Cleal over 8 years ago
- Translation missing: en.field_release set to 136
Actions