Project

General

Profile

Actions
Copy link

Bug #12954

closed

Foreman puppet report status does not work without a puppet proxy

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

Status:
Closed
Priority:
Normal
Assignee:
Dominic Cleal
Category:
Reporting
Target version:
1.10.1
Difficulty:
trivial
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman/pull/3028
Fixed in Releases:
Found in Releases:
1.10.0
Red Hat JIRA:

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 open — 2 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
Copy link
 #1

Updated by Ohad Levy almost 9 years ago

Actions
Copy link
 #2

Updated by Dominic Cleal almost 9 years ago

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

Updated by Dominic Cleal almost 9 years ago

  • Translation missing: en.field_release set to 104
Actions
Copy link
 #4

Updated by Dominic Cleal almost 9 years ago

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

Updated by The Foreman Bot almost 9 years ago

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

Updated by Dominic Cleal almost 9 years ago

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

Updated by Dominic Cleal almost 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
Copy link
 #8

Updated by Dominic Cleal almost 9 years ago

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

Updated by Dominic Cleal almost 9 years ago

  • Translation missing: en.field_release changed from 71 to 104
Actions
Copy link
 #10

Updated by rajeev jaggavarapu over 8 years ago

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

Updated by Dominic Cleal over 8 years ago

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

Also available in: Atom PDF