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

[BUG] update cluster failed with error: failed calling webhook "vcluster.kb.io" #7234

Open
iziang opened this issue May 6, 2024 · 1 comment · Fixed by #7239
Open

[BUG] update cluster failed with error: failed calling webhook "vcluster.kb.io" #7234

iziang opened this issue May 6, 2024 · 1 comment · Fixed by #7239
Assignees
Labels
kind/bug Something isn't working severity/major Great chance user will encounter the same problem
Milestone

Comments

@iziang
Copy link
Contributor

iziang commented May 6, 2024

Describe the bug

Kubernetes: v1.28.7-gke.1026000
KubeBlocks: 0.9.0-beta.17
kbcli: 0.9.0-beta.4
WARNING: version difference between kbcli (0.9.0-beta.4) and kubeblocks (0.9.0-beta.17)

kbcli cluster update esearch-iuhydm --termination-policy=WipeOut
error: unable to update Cluster default/esearch-iuhydm: Internal error occurred: failed calling webhook "vcluster.kb.io": failed to call webhook: Post "https://kubeblocks.kb-system.svc:9443/validate-apps-kubeblocks-io-v1alpha1-cluster?timeout=10s": dial tcp 10.116.3.5:9443: connect: connection refused

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@iziang iziang added the kind/bug Something isn't working label May 6, 2024
@iziang
Copy link
Contributor Author

iziang commented May 6, 2024

The label selector for the kubeblocks service is incorrect, which resulted in the selection of the dataprotection pod with an IP address of 10.116.3.5, causing the webhook connection failed.

kg pods -n kb-system -owide
NAME                                            READY   STATUS    RESTARTS   AGE   IP            NODE                                    NOMINATED NODE   READINESS GATES
kb-addon-snapshot-controller-7bc7cf9dbf-xqxqm   1/1     Running   0          38m   10.116.2.16   gke-yjtest-default-pool-db1b1327-k7nc   <none>           <none>
kubeblocks-59f654fcbd-pd8vk                     1/1     Running   0          11m   10.116.1.7    gke-yjtest-default-pool-db1b1327-vx5t   <none>           <none>
kubeblocks-59f654fcbd-qc5zx                     1/1     Running   0          11m   10.116.5.5    gke-yjtest-default-pool-db1b1327-x27b   <none>           <none>
kubeblocks-59f654fcbd-v8bbs                     1/1     Running   0          11m   10.116.0.13   gke-yjtest-default-pool-db1b1327-f6f8   <none>           <none>
kubeblocks-dataprotection-74b8859b77-nrftb      1/1     Running   0          11m   10.116.1.6    gke-yjtest-default-pool-db1b1327-vx5t   <none>           <none>
kubeblocks-dataprotection-74b8859b77-pm6bb      1/1     Running   0          11m   10.116.3.5    gke-yjtest-default-pool-db1b1327-fl74   <none>           <none>
kubeblocks-dataprotection-74b8859b77-vj4dh      1/1     Running   0          11m   10.116.4.5    gke-yjtest-default-pool-db1b1327-xmvb   <none>           <none>

@ahjing99 ahjing99 assigned leon-inf and unassigned nayutah May 6, 2024
@ahjing99 ahjing99 added the severity/major Great chance user will encounter the same problem label May 6, 2024
@github-actions github-actions bot added this to the Release 0.9.0 milestone May 6, 2024
@leon-inf leon-inf reopened this May 13, 2024
@leon-inf leon-inf assigned ldming and unassigned leon-inf May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working severity/major Great chance user will encounter the same problem
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants