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]1.0 kbcli cluster vscale failed if the cluster is set to a non-default namespace #8478

Closed
tianyue86 opened this issue Nov 19, 2024 · 1 comment · Fixed by apecloud/kbcli#490
Assignees
Labels
kind/bug Something isn't working
Milestone

Comments

@tianyue86
Copy link

Describe the env
Kubernetes: v1.30.4-eks-a737599
KubeBlocks: 1.0.0-beta.2
kbcli: 1.0.0-beta.1

To Reproduce
Steps to reproduce the behavior:

  1. Create two minio clusters under two different namespaces: default and ns-srbgcxycta
NAMESPACE       NAME             CLUSTER-DEFINITION   TERMINATION-POLICY   STATUS    AGE
ns-srbgcxycta   minio-qjfwxc                                             WipeOut                           Running   2m49s
default                minio-ajkwnv                                             DoNotTerminate             Running    5m39s
  1. cluster vscale failed If the cluster is set to a non-default namespace
kbcli cluster vscale minio-qjfwxc --auto-approve --force=true                 --components minio                 --cpu 200m                 --memory 0.6Gi --namespace ns-srbgcxycta
Error from server (NotFound): clusters.apps.kubeblocks.io "minio-qjfwxc" not found
  1. cluster vscale success If the cluster is set to default namespace
    kbcli cluster vscale minio-ajkwnv --auto-approve --force=true --components minio --cpu 200m --memory 0.6Gi --namespace default

OpsRequest minio-ajkwnv-verticalscaling-thmd8 created successfully, you can view the progress:
kbcli cluster describe-ops minio-ajkwnv-verticalscaling-thmd8 -n default

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.

@tianyue86 tianyue86 added the kind/bug Something isn't working label Nov 19, 2024
@tianyue86
Copy link
Author

tianyue86 commented Nov 19, 2024

kbcli cluster stop minio-qjfwxc --auto-approve --force=true --namespace ns-srbgcxycta
kbcli cluster start minio-qjfwxc --force=true --namespace ns-srbgcxycta
kbcli cluster restart minio-qjfwxc --auto-approve --force=true --namespace ns-srbgcxycta
kbcli cluster volume-expand minio-qjfwxc --auto-approve --force=true --components minio --volume-claim-templates data --storage 6Gi --namespace ns-srbgcxycta

---> the above commands have the same problem, please fix them together. Thanks!

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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants