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]official-pg is always in Abnormal status after hscale #8126

Closed
tianyue86 opened this issue Sep 11, 2024 · 0 comments
Closed

[BUG]official-pg is always in Abnormal status after hscale #8126

tianyue86 opened this issue Sep 11, 2024 · 0 comments
Assignees
Labels
kind/bug Something isn't working
Milestone

Comments

@tianyue86
Copy link

Describe the bug

Kubernetes: v1.29.7-gke.1274000
KubeBlocks: 0.9.1-beta.24
kbcli: 0.9.1-beta.10

To Reproduce
Steps to reproduce the behavior:

  1. create cluster
    kbcli cluster create offpg-nuqnwn --termination-policy=DoNotTerminate --cluster-definition=official-postgresql --enable-all-logs=false --cluster-version=official-postgresql-14.7 --set cpu=100m,memory=0.5Gi,replicas=1,storage=3Gi --namespace default

  2. hscale
    kbcli cluster hscale offpg-nuqnwn --auto-approve --force=true --components postgresql --replicas 3 --namespace default

  3. see error
    kubectl describe cluster offpg-nuqnwn --namespace default

phase: Abnormal

Events:
Type Reason Age From Message


Normal ComponentPhaseTransition 20m cluster-controller component is Creating
Normal ClusterReady 18m (x2 over 19m) cluster-controller Cluster: offpg-nuqnwn is ready, current phase is Running
Normal Running 18m (x2 over 19m) cluster-controller Cluster: offpg-nuqnwn is ready, current phase is Running
Normal AllReplicasReady 18m (x2 over 19m) cluster-controller all pods of components are ready, waiting for the probe detection successful
Normal ApplyResourcesSucceed 17m (x5 over 20m) cluster-controller Successfully applied for resources
Warning ComponentsNotReady 17m (x2 over 18m) cluster-controller pods are unavailable in Components: [postgresql], refer to related component message in Cluster.status.components
Warning ReplicasNotReady 17m (x2 over 18m) cluster-controller pods are not ready in Components: [postgresql], refer to related component message in Cluster.status.components
Normal ComponentPhaseTransition 16m (x3 over 19m) cluster-controller component is Running
Normal ComponentPhaseTransition 10m (x3 over 18m) cluster-controller component is Updating
Normal PreCheckSucceed 10m (x5 over 20m) cluster-controller The operator has started the provisioning of Cluster: offpg-nuqnwn
Normal HorizontalScale 9m34s component-controller start horizontal scale component postgresql of cluster offpg-nuqnwn from 0 to 1
Normal HorizontalScale 8m48s (x2 over 8m49s) component-controller start horizontal scale component postgresql of cluster offpg-nuqnwn from 1 to 3
Warning BackOff 3m36s (x2 over 7m52s) event-controller Pod offpg-nuqnwn-postgresql-2: Back-off restarting failed container postgresql in pod offpg-nuqnwn-postgresql-2_default(640d4e32-fd51-4958-a93d-f12181ed4e6e)
Warning BackOff 3m28s event-controller Pod offpg-nuqnwn-postgresql-1: Back-off restarting failed container postgresql in pod offpg-nuqnwn-postgresql-1_default(546a4884-00d6-4e3a-89a8-8b4863fd17e2)
5. 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.

@tianyue86 tianyue86 added the kind/bug Something isn't working label Sep 11, 2024
@tianyue86 tianyue86 added this to the Release 0.9.1 milestone Sep 11, 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
Projects
None yet
Development

No branches or pull requests

2 participants