Project

General

Profile

Actions
Copy link

Bug #11051

closed

OS host counters inaccurate after host deletion

Added by Oleg Obleukhov over 9 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Tomer Brisker
Category:
Statistics
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
1.9.0
Red Hat JIRA:

Description

If you remove hosts from Foreman, you will have resynchronization of data:

Related issues 1 (0 open — 1 closed)

Related to Foreman - Bug #5692: Puppet environment counters not updatedClosedTomer Brisker05/13/2014Actions
Actions
Copy link
 #1

Updated by Dominic Cleal over 9 years ago

  • Project changed from Plugins to Foreman
  • Category set to Statistics
  • Status changed from New to Need more information

Which version of Foreman is this? There are some fixes for counters in 1.8.

Actions
Copy link
 #2

Updated by Oleg Obleukhov over 9 years ago

1.9 RC1

Actions
Copy link
 #3

Updated by Dominic Cleal over 9 years ago

  • Subject changed from Recalculate data of OS usage to OS host counters inaccurate after host deletion
  • Status changed from Need more information to New
  • Priority changed from High to Normal
Actions
Copy link
 #4

Updated by Dominic Cleal over 9 years ago

  • Related to Bug #5692: Puppet environment counters not updated added
Actions
Copy link
 #5

Updated by Dominic Cleal over 9 years ago

I wonder if the previous fix, #5692, only covers the case when the OS changes on a host and not when the host is deleted. Thanks for the report.

Could you check if running foreman-rake fix_cached_counters temporarily fixes/resets the counters here?

Actions
Copy link
 #6

Updated by Oleg Obleukhov over 9 years ago

Dominic Cleal wrote:

I wonder if the previous fix, #5692, only covers the case when the OS changes on a host and not when the host is deleted. Thanks for the report.

Could you check if running foreman-rake fix_cached_counters temporarily fixes/resets the counters here?

Yes, this command fixed it.

Actions
Copy link
 #7

Updated by Tomer Brisker over 9 years ago

  • Status changed from New to Assigned
  • Assignee set to Tomer Brisker
Actions
Copy link
 #8

Updated by Tomer Brisker over 9 years ago

  • Status changed from Assigned to Need more information

I could not reproduce this, tried adding and removing hosts to no avail.
Is it possible you had a corrupted DB somehow that had leftovers from before the fix?
If you manage to reproduce this, please let us know the steps to reproduce that lead to mistaken counts.

Actions
Copy link
 #9

Updated by Oleg Obleukhov over 9 years ago

You can close the ticket. I found 1 place where it was modified directly in database. So periodical run of foreman-rake fix_cached_counters fixed the problem.

Actions
Copy link
 #10

Updated by Tomer Brisker over 9 years ago

  • Status changed from Need more information to Rejected

Bug was due to direct modification in database. Closing.

Actions
Copy link

Also available in: Atom PDF