Project

General

Custom queries

Profile

Actions

Bug #12954

closed

Foreman puppet report status does not work without a puppet proxy

Added by Chuck Schweizer over 9 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Reporting
Target version:
Difficulty:
trivial
Triaged:
Fixed in Releases:
Found in Releases:

Description

As of foreman 1.10.0 the host_status table is not updated with puppet report status if your puppet masters are not official puppet proxy servers.

https://github.com/theforeman/foreman/blob/1.10-stable/app/models/host_status/configuration_status.rb#L81

This breaks configurations that use foreman as a report backend but do not make use of the foreman proxy code.


Related issues 2 (0 open2 closed)

Related to Foreman - Bug #11771: Saving host without particular status failsClosedDominic Cleal09/10/2015Actions
Related to Foreman - Bug #13112: N+1 query on hosts#index from last report objectClosedDominic Cleal01/11/2016Actions
Actions #1

Updated by Ohad Levy over 9 years ago

Actions #6

Updated by Dominic Cleal over 9 years ago

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

Updated by Dominic Cleal over 9 years ago

  • Translation missing: en.field_release changed from 104 to 71

#13112 is a regression, moving to 1.11 until resolved - and it may require an internal API change to fix. Will move it back if it turns out not to.

Actions

Also available in: Atom PDF