Bug #14401
Host#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).
Related issues
Associated revisions
History
#1
Updated by The Foreman Bot about 6 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/3380 added
#2
Updated by Marek Hulán about 6 years ago
- Related to Bug #14372: Content Host shows green status with "Warning" added
#3
Updated by Marek Hulán about 6 years ago
- Category set to Plugin integration
#4
Updated by Marek Hulán about 6 years ago
- Legacy Backlogs Release (now unused) set to 152
#5
Updated by John Mitsch about 6 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset b3d3d65de79153baf85641ce4005b7bc171050fb.
#6
Updated by Dominic Cleal about 6 years ago
- Related to Bug #14518: unable to save report due to a host os misconfiguration added
#7
Updated by Dominic Cleal about 6 years ago
- Legacy Backlogs Release (now unused) changed from 152 to 136
Bumping due to linked regression, possibly also linked to #14516.
#8
Updated by Dominic Cleal about 6 years ago
- Related to Bug #14516: Host::Base#domain_id= delegated to primary_interface.domain_id=, but primary_interface is nil added
#9
Updated by Tomer Brisker almost 6 years ago
- Related to Refactor #15849: Improve performance of host global status updates added
Fixes #14401 - Refreshing Host's global status not persisting to the database