Closed
Description
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:
- Create a catalog containing
foo.v1.0.0
, with a pollInterval set to2s
(or something very short) - Create a cluster extension for
foo
with no channel or version specifications - Wait until
foo.v1.0.0
successfully installs. - Update the catalog to contain
foo.v2.0.0
with an upgrade edge from v1, and push the update to the same tag. - 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, findsfoo.v2.0.0
and installs it.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Done