Error When Getting Clusters

[mbentley]

Encountered at least one cluster with unexpected or missing metadata. (@mirantis/lens-extension-cc)

In this case, it might have been related to one of the following:

• a cluster that was created but they had only specified 3 managers and no workers yet so it was still in a pending state as a not yet valid configuration
• A cluster that was defined but it had no nodes in the cluster

Those are the only odd things I can find about the container cloud install at the time. I am almost positive it is the 2nd one - a cluster has been defined but has no nodes in the cluster.

[mbentley]

Ah yeah, I just confirmed that it starts happening after I create a cluster without adding any nodes.

[stefcameron]

Thanks @mbentley . Are you able to reproduce this again, but this time, press CMD+OPT+I while in Lens to open the DevTools and copy/paste any exceptions you see in there here? That would help me to know what part of the cluster spec is missing that my code isn't expecting. Then I could just ignore those clusters, or maybe still support them -- depending on what's missing (i.e. if what's missing isn't required to generate a kubeconfig for it).

[mbentley]

localhost-1608070585843.log

ClustersProvider.js?3e90:127 [@mirantis/lens-extension-cc/ClustersProvider._deserializeClustersList()] ERROR: Cannot read property 'providerStatus' of undefined TypeError: Cannot read property 'providerStatus' of undefined
    at getServerUrl (Cluster.js?8f07:10)
    at new Cluster (Cluster.js?8f07:93)
    at eval (ClustersProvider.js?3e90:124)
    at Array.map (<anonymous>)
    at _deserializeClustersList (ClustersProvider.js?3e90:124)
    at eval (ClustersProvider.js?3e90:178)
    at Array.every (<anonymous>)
    at _fetchClusters (ClustersProvider.js?3e90:177)
    at async _loadData (ClustersProvider.js?3e90:211)
_deserializeClustersList @ ClustersProvider.js?3e90:127
eval @ ClustersProvider.js?3e90:178
_fetchClusters @ ClustersProvider.js?3e90:177
async function (async)
_fetchClusters @ ClustersProvider.js?3e90:156
_loadData @ ClustersProvider.js?3e90:211
async function (async)
_loadData @ ClustersProvider.js?3e90:201
load @ ClustersProvider.js?3e90:266
eval @ View.js?2be1:429
is @ Lens.js:2
gc @ Lens.js:2
t.unstable_runWithPriority @ Lens.js:2
Ui @ Lens.js:2
fc @ Lens.js:2
(anonymous) @ Lens.js:2
_ @ Lens.js:2
v.port1.onmessage @ Lens.js:2

In this case, we should probably just ignore these clusters (as they don't exist yet).

[stefcameron]

Thanks for the log, that helps!

In this case, we should probably just ignore these clusters (as they don't exist yet).

👍

[stefcameron]

This will be fixed in the next release of the extension.