Skip to content

Review current Errored rule results #694

@AleksandarSavchev

Description

@AleksandarSavchev

What would you like to be added:
The description of Errored rule checks is as follows: Errored: Rule check has errored during runtime. It cannot be determined whether the check is fulfilled or not.

However currently we have rule checks that are with Errored status but the rule has not errored during runtime. E.g. rule 2005:

if containerStatusIdx < 0 {
checkResults = append(checkResults, rule.ErroredCheckResult("containerStatus not found for container", containerTarget))
continue
}

We should review all Errored rules and find a better categorization for rule checks that do not fit the Errored description

Why is this needed:
Users determine Errored rule results as findings. We should aim to minimise the cases we
categorize as Errored and stick to current description of errored rule check: Rule check has errored during runtime

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/enhancementEnhancement, improvement, extensionpriority/3Priority (lower number equals higher priority)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions