Skip to content

Validate conditions at the end of e2e tests #11963

Open
@sbueringer

Description

@sbueringer

We recently noticed that after a CAPI upgrade some conditions didn't look as expected (e.g. Available was false).

We fixed the issue and then added validation of some conditions to the clusterctl upgrade tests in: #11948

So now we are checking Ready and Available conditions on Clusters and Machines.

We should add the same check to the end of other e2e tests as well (maybe even all or most of them).

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions