Actions
Bug #14401
closedHost#refresh_global_status not persisting changes to the db
Description
related to http://projects.theforeman.org/issues/14372
Refreshing the global_status here [1] does not persist changes to the database, which is causing problems in Katello when calling global_status (see above bug).
Updated by The Foreman Bot almost 9 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3380 added
Updated by Marek Hulán almost 9 years ago
- Related to Bug #14372: Content Host shows green status with "Warning" added
Updated by Marek Hulán almost 9 years ago
- Translation missing: en.field_release set to 152
Updated by John Mitsch almost 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset b3d3d65de79153baf85641ce4005b7bc171050fb.
Updated by Dominic Cleal over 8 years ago
- Related to Bug #14518: unable to save report due to a host os misconfiguration added
Updated by Dominic Cleal over 8 years ago
- Translation missing: en.field_release changed from 152 to 136
Bumping due to linked regression, possibly also linked to #14516.
Updated by Dominic Cleal over 8 years ago
- Related to Bug #14516: Host::Base#domain_id= delegated to primary_interface.domain_id=, but primary_interface is nil added
Updated by Tomer Brisker over 8 years ago
- Related to Refactor #15849: Improve performance of host global status updates added
Actions