Skip to content

Fix: e2e test for re-reconcile on catalog change is not valid #945

Closed
@joelanford

Description

@joelanford

The TestClusterExtensionInstallReResolvesWhenNewCatalog test is not valid because it sets up a cluster extenstion that fails to resolve. This results in an exponential backoff where retries will occur whether or not a new catalog appears.

To correct this test, we need to:

  1. Create a catalog containing foo.v1.0.0, with a pollInterval set to 2s (or something very short)
  2. Create a cluster extension for foo with no channel or version specifications
  3. Wait until foo.v1.0.0 successfully installs.
  4. Update the catalog to contain foo.v2.0.0 with an upgrade edge from v1, and push the update to the same tag.
  5. After step (4) the following should happen all automatically:
    • Catalogd polls and sees a new SHA for the digest, pulls it and makes it available
    • Operator-controller sees the new catalog and re-reconciles all ClusterExtensions
    • The foo cluster extension re-resolves, finds foo.v2.0.0 and installs it.

Metadata

Metadata

Assignees

Labels

kind/bugCategorizes issue or PR as related to a bug.v1.0Issues related to the initial stable release of OLMv1

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions