Project

General

Profile

Actions

Bug #17245

open

global_status = error filter does not show hosts with no "configuration" status

Added by Julien Pivotto over 7 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Reporting
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

I have several hosts that have the "token expired" status. As they were meant to be rebuild, the foreman erased their configuration status.

The status of the hosts is show as errored in the hosts list.

However, the filter global_status = error does not show them.

It does however show a node with "token expired" AND configuration = OK.

So:

Expected:

global_status = error returns hosts with:

- Configuration = OK and build = ERROR
- Configuration = ERROR and build = OK
- Configuration = nil and build = ERROR

Actual result:

global_status = error returns hosts with:

- Configuration = OK and build = ERROR
- Configuration = ERROR and build = OK

global_status = error does NOT return hosts with:
- Configuration = nil and build = ERROR


Files

globstatus.png View globstatus.png 5.17 KB Julien Pivotto, 11/07/2016 04:15 AM
globstatus2.png View globstatus2.png 8.6 KB Julien Pivotto, 11/07/2016 04:15 AM
globstatus3.png View globstatus3.png 10.3 KB Julien Pivotto, 11/07/2016 04:16 AM
Actions #1

Updated by Julien Pivotto over 7 years ago

  • Subject changed from global_status = error filter does not show hosts bith no "configuration" status to global_status = error filter does not show hosts with no "configuration" status
Actions #2

Updated by Dominic Cleal over 7 years ago

  • Category set to Reporting
Actions

Also available in: Atom PDF