You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running e2e tests there is an error, which prevents test to run
AWS Templates [It] should work with an AWS provider [provider:cloud, provider:aws]
/home/runner/work/kcm/kcm/test/e2e/provider_aws_test.go:75
[FAILED] failed to create ClusterDeployment
Unexpected error:
<*errors.StatusError | 0xc0006dcc80>:
admission webhook "validation.clusterdeployment.hmc.mirantis.com" denied the request: the ClusterDeployment is invalid: the template is not valid: one or more required providers are not deployed yet: [bootstrap-k0smotron control-plane-k0smotron]
{
ErrStatus: {
TypeMeta: {Kind: "Status", APIVersion: "v1"},
ListMeta: {
SelfLink: "",
ResourceVersion: "",
Continue: "",
RemainingItemCount: nil,
},
Status: "Failure",
Message: "admission webhook \"validation.clusterdeployment.hmc.mirantis.com\" denied the request: the ClusterDeployment is invalid: the template is not valid: one or more required providers are not deployed yet: [bootstrap-k0smotron control-plane-k0smotron]",
Reason: "Forbidden",
Details: nil,
Code: 403,
},
}
occurred
In [It] at: /home/runner/work/kcm/kcm/test/e2e/provider_aws_test.go:85 @ 01/07/25 00:05:08.459
So it appears that we're trying to create ClusterDeployment before all other components are ready.
Possible solution
Before applying ClusterDeployment we should check that all other objects (like Management, ClusterTemplate, ProviderTemplates and provider themselves) are ready. Currently we're relying on providers' Deployment status to figure that out, which isn't reliable and can't be used to detect k0rdent readiness.
P.S.: Since it was fixed before ( in #622 )it looks like the regression could be related to #847, since it significantly delays the deployment time of all components. Which actually emphasizes on how unreliable current readiness detection mechanism is.
The text was updated successfully, but these errors were encountered:
Issue
When running e2e tests there is an error, which prevents test to run
So it appears that we're trying to create
ClusterDeployment
before all other components are ready.Possible solution
Before applying
ClusterDeployment
we should check that all other objects (like Management, ClusterTemplate, ProviderTemplates and provider themselves) are ready. Currently we're relying on providers' Deployment status to figure that out, which isn't reliable and can't be used to detect k0rdent readiness.P.S.: Since it was fixed before ( in #622 )it looks like the regression could be related to #847, since it significantly delays the deployment time of all components. Which actually emphasizes on how unreliable current readiness detection mechanism is.
The text was updated successfully, but these errors were encountered: