Skip to content

Flake in operator-developer-e2e: unexpected status conditions for the operator #481

Closed
@m1kola

Description

@m1kola

As of a00a93f I see an uptick in operator-developer-e2e job flakes which look like this:

[FAILED] Timed out after 120.000s.
The function passed to Eventually failed at /home/runner/work/operator-controller/operator-controller/test/operator-framework-e2e/operator_framework_test.go:825 with:
Unexpected error:
    <*errors.errorString | 0xc0004c8af0>: 
    Status conditions for the operator plain-operator for the version 0.2.0 is not as expected:Expected status: True, but got: False
    {
        s: "Status conditions for the operator plain-operator for the version 0.2.0 is not as expected:Expected status: True, but got: False",
    }
occurred
In [It] at: /home/runner/work/operator-controller/operator-controller/test/operator-framework-e2e/operator_framework_test.go:826 @ 10/24/23 11:06:46.447
[FAILED] Timed out after 120.000s.
The function passed to Eventually failed at /home/runner/work/operator-controller/operator-controller/test/operator-framework-e2e/operator_framework_test.go:825 with:
Unexpected error:
    <*errors.errorString | 0xc00043bc60>: 
    Status conditions for the operator registry-operator for the version 0.1.0 is not as expected:Expected status: True, but got: False
    {
        s: "Status conditions for the operator registry-operator for the version 0.1.0 is not as expected:Expected status: True, but got: False",
    }
occurred
In [It] at: /home/runner/work/operator-controller/operator-controller/test/operator-framework-e2e/operator_framework_test.go:826 @ 10/24/23 11:09:20.027

Example:

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/flakeCategorizes issue or PR as related to a flaky test.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions