Skip to content

bug: Log Analysis flow stops when clusteroperators.json is missing from logs #96

Description

@abraham2512

Some jobs such as the Orion job for telco does not have a cluster operators json in its job artifacts. BugZooka attempts to download and fails, and it is preventing log analyzer from downloading orion xmls for further analysis.

Relevant line:

download_prow_orion_xmls(gcs_path, orion_dir)

This may not need to be contingent on the previous step?

This is error message shown in bugzooka logs.

Somehow couldn't find clusteroperators.json file
Logs for container test in pod e2e-telcov10n-orion-telcov10n-orion-tests:

"e2e-telcov10n-orion" pod "e2e-telcov10n-orion-telcov10n-orion-tests" failed: could not watch pod: the pod ci-op-5z6q4qnq/e2e-telcov10n-orion-telcov10n-orion-tests failed after 41s (failed containers: test): ContainerFailed one or more containers exited

Container test exited with code 2, reason Error

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions