Project

General

Profile

Bug #14969

Custom status is not reloaded correctly

Added by Marek Hulán over 4 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Plugin integration
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

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)


Related issues

Related to Foreman - Refactor #12747: Provide some kind of central store or consistent way to manage dynamically registered objects from pluginsResolved2015-12-08
Blocked by Foreman - Feature #14588: Improve extending template helpers from plugin Closed2016-04-12

Associated revisions

Revision 670184e1 (diff)
Added by Marek Hulán over 4 years ago

Fixes #14969 - correctly reload custom statuses

History

#1 Updated by The Foreman Bot over 4 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/3508 added

#2 Updated by Dominic Cleal over 4 years ago

  • Related to Refactor #12747: Provide some kind of central store or consistent way to manage dynamically registered objects from plugins added

#3 Updated by Marek Hulán over 4 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#4 Updated by Dominic Cleal over 4 years ago

  • Blocked by Feature #14588: Improve extending template helpers from plugin added

#5 Updated by Dominic Cleal over 4 years ago

  • Legacy Backlogs Release (now unused) set to 136

Also available in: Atom PDF