Project

General

Profile

Actions

Bug #12954

closed

Foreman puppet report status does not work without a puppet proxy

Added by Chuck Schweizer about 8 years ago. Updated over 5 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 about 8 years ago

Actions #2

Updated by Dominic Cleal about 8 years ago

  • Related to Bug #11771: Saving host without particular status fails added
Actions #3

Updated by Dominic Cleal about 8 years ago

  • translation missing: en.field_release set to 104
Actions #4

Updated by Dominic Cleal about 8 years ago

  • Status changed from New to Assigned
  • Assignee set to Dominic Cleal
Actions #5

Updated by The Foreman Bot about 8 years ago

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

Updated by Dominic Cleal about 8 years ago

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

Updated by Dominic Cleal about 8 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 #8

Updated by Dominic Cleal about 8 years ago

  • Related to Bug #13112: N+1 query on hosts#index from last report object added
Actions #9

Updated by Dominic Cleal about 8 years ago

  • translation missing: en.field_release changed from 71 to 104
Actions #10

Updated by rajeev jaggavarapu over 7 years ago

  • Copied to Support #15571: "Invalid keyfile or passphrase" when saving GCE compute resource added
Actions #11

Updated by Dominic Cleal over 7 years ago

  • Copied to deleted (Support #15571: "Invalid keyfile or passphrase" when saving GCE compute resource)
Actions

Also available in: Atom PDF