Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexplained "dryRun is not supported" error for deploying Application targetted at OCM cluster #5361

Open
vyta opened this issue Jan 19, 2023 · 12 comments
Labels
area/multi-cluster multi-cluster management related issue type/bug Something isn't working

Comments

@vyta
Copy link

vyta commented Jan 19, 2023

Describe the bug

Application workflow fails with "cannot create object: dryRun is not supported)" with OCM managedclusters

To Reproduce

  1. Create hub cluster w/ vela + OCM hub + gateway manager
  2. Create member cluster and join
  3. Create Application definition with membercluster listed in topology
  4. Observe application workflow fail with:
Message: run step(provider=multicluster,do=deploy): Found 1 errors. [(error encountered in cluster cluster1: Dispatch: pre-dispatch dryrun failed: Found 1 errors. [(cannot create object: dryRun is not supported)])]

Expected behavior

Should detect cluster and deploy application

KubeVela Version

CLI Version: v1.7.0
Core Version: 1.7.0

Cluster information

1.24.0

@Somefive
Copy link
Collaborator

Could you see what cluster-gateway image version are you using? You could run kubectl get deployment -n vela-system -owide and see it.

@Somefive Somefive added type/bug Something isn't working area/multi-cluster multi-cluster management related issue labels Jan 20, 2023
@vyta
Copy link
Author

vyta commented Jan 20, 2023

Could you see what cluster-gateway image version are you using? You could run kubectl get deployment -n vela-system -owide and see it.

v1.7.0-alpha.3

@Somefive
Copy link
Collaborator

I guess it might be because the OCM cluster proxy does not support the dryrun request proxy. Could you try to add --set featureGates.preDispatchDryRun=false to the helm install process. It will let the KubeVela controller skip the dryrun phase for dispatching resources.

@testinfected
Copy link

testinfected commented Apr 22, 2024

We're still getting that error with Vela 1.9.9

Our cluster gateway is 1.9.0-alpha2. @Somefive Any idea where to look to understand/fix this issue?

Thanks

@testinfected
Copy link

We saw that Cluster Gateway 1.9.0 was released, but that does not solve the issue.

Would any of the Kubela maintainers ( @FogDong ? @wonderflow ? @Somefive ?) please give a clue on how to solve this issue.

Thanks guys,

@FogDong
Copy link
Member

FogDong commented Apr 24, 2024

Hi, have you tried adding --set featureGates.preDispatchDryRun=false to the helm install process?

@testinfected
Copy link

Hey @FogDong yes that works although we'd like to keep the pre-dispatch dry run if possible. Are you telling me it's not compatible with multicluster deployment?

@FogDong
Copy link
Member

FogDong commented Apr 25, 2024

Yeah I think right now OCM cluster proxy still does not support the dryrun request proxy. Any insights from @Somefive ?

@testinfected
Copy link

@FogDong to clarify we're not using OCM ManagedCluster, just regular cluster join. Is it still expected that dryRun does not work?

@FogDong
Copy link
Member

FogDong commented Apr 26, 2024

In a standard cluster setup, the dryRun option should indeed function as expected. I will investigate this issue further if it is not working as expected.

@testinfected
Copy link

@FogDong it's not working correctly for us. We use normal vela join and don't have any OCM addons installed.

We have to disable dry runs unfortunately. Any clues on what could be the problem here?

@testinfected
Copy link

Bump, any idea @FogDong? Thanks in advance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/multi-cluster multi-cluster management related issue type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants