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
Describe the bug
postgresql cluster restart error.
kbcli version
Kubernetes: v1.25.10-eks-c12679a
KubeBlocks: 0.6.0-alpha.23
kbcli: v0.6.0-alpha.23
To Reproduce
Steps to reproduce the behavior:
create cluster
restart
See error
kubectl get ops,pod,cluster,sts,pvc -l app.kubernetes.io/instance=cluster-hkjsxx
NAME TYPE CLUSTER STATUS PROGRESS AGE
opsrequest.apps.kubeblocks.io/cluster-hkjsxx-restart-rg6z4 Restart cluster-hkjsxx Running 0/3 13m
NAME READY STATUS RESTARTS AGE
pod/cluster-hkjsxx-postgresql-0 4/5 Running 0 13m
pod/cluster-hkjsxx-postgresql-1 4/5 Running 0 12m
pod/cluster-hkjsxx-postgresql-2 4/5 Running 0 12m
NAME CLUSTER-DEFINITION VERSION TERMINATION-POLICY STATUS AGE
cluster.apps.kubeblocks.io/cluster-hkjsxx postgresql postgresql-12.15.0 DoNotTerminate Updating 22m
NAME READY AGE
statefulset.apps/cluster-hkjsxx-postgresql 0/3 22m
describe cluster
kubectl describe cluster cluster-hkjsxx
Name: cluster-hkjsxx
Namespace: default
Labels: app.kubernetes.io/instance=cluster-hkjsxx
clusterdefinition.kubeblocks.io/name=postgresql
clusterversion.kubeblocks.io/name=postgresql-12.15.0
Annotations: kubeblocks.io/ops-request: [{"name":"cluster-hkjsxx-restart-rg6z4","type":"Restart"}]
kubeblocks.io/reconcile: 2023-06-26T13:31:44.807853849Z
API Version: apps.kubeblocks.io/v1alpha1
Kind: Cluster
Metadata:
Creation Timestamp: 2023-06-26T13:12:01Z
Finalizers:
cluster.kubeblocks.io/finalizer
Generation: 7
Resource Version: 115732
UID: 8ded0b09-4416-495d-898d-138e3f61d145
Spec:
Affinity:
Pod Anti Affinity: Preferred
Tenancy: SharedNode
Cluster Definition Ref: postgresql
Cluster Version Ref: postgresql-12.15.0
Component Specs:
Class Def Ref:
Class:
Component Def Ref: postgresql
Monitor: false
Name: postgresql
No Create PDB: false
Replicas: 3
Resources:
Limits:
Cpu: 300m
Memory: 966367641600m
Requests:
Cpu: 300m
Memory: 966367641600m
Service Account Name: kb-sa-cluster-hkjsxx
Switch Policy:
Type: Noop
Volume Claim Templates:
Name: data
Spec:
Access Modes:
ReadWriteOnce
Resources:
Requests:
Storage: 15Gi
Storage Class Name: kb-default-sc
Termination Policy: DoNotTerminate
Status:
Cluster Def Generation: 2
Components:
Postgresql:
Phase: Updating
Pods Ready: false
Replication Set Status:
Primary:
Pod: cluster-hkjsxx-postgresql-0
Secondaries:
Pod: cluster-hkjsxx-postgresql-1
Pod: cluster-hkjsxx-postgresql-2
Conditions:
Last Transition Time: 2023-06-26T13:20:35Z
Message: Restart opsRequest: cluster-hkjsxx-restart-rg6z4 is processing
Reason: Restarting
Status: False
Type: LatestOpsRequestProcessed
Last Transition Time: 2023-06-26T13:12:01Z
Message: The operator has started the provisioning of Cluster: cluster-hkjsxx
Observed Generation: 7
Reason: PreCheckSucceed
Status: True
Type: ProvisioningStarted
Last Transition Time: 2023-06-26T13:20:05Z
Message: Successfully applied for resources
Observed Generation: 7
Reason: ApplyResourcesSucceed
Status: True
Type: ApplyResources
Last Transition Time: 2023-06-26T13:20:05Z
Message: pods are not ready in Components: [postgresql], refer to related component message in Cluster.status.components
Reason: ReplicasNotReady
Status: False
Type: ReplicasReady
Last Transition Time: 2023-06-26T13:20:05Z
Message: pods are unavailable in Components: [postgresql], refer to related component message in Cluster.status.components
Reason: ComponentsNotReady
Status: False
Type: Ready
Observed Generation: 7
Phase: Updating
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal ComponentPhaseTransition 20m cluster-controller Create a new component
Normal AllReplicasReady 19m cluster-controller all pods of components are ready, waiting for the probe detection successful
Normal ClusterReady 19m cluster-controller Cluster: cluster-hkjsxx is ready, current phase is Running
Normal SysAcctCreate 19m system-account-controller Created accounts for cluster: cluster-hkjsxx, component: postgresql, accounts: kbmonitoring
Normal SysAcctCreate 19m system-account-controller Created accounts for cluster: cluster-hkjsxx, component: postgresql, accounts: kbreplicator
Normal SysAcctCreate 19m system-account-controller Created accounts for cluster: cluster-hkjsxx, component: postgresql, accounts: kbadmin
Normal SysAcctCreate 19m system-account-controller Created accounts for cluster: cluster-hkjsxx, component: postgresql, accounts: kbprobe
Normal SysAcctCreate 19m system-account-controller Created accounts for cluster: cluster-hkjsxx, component: postgresql, accounts: kbdataprotection
Normal Reconfiguring 18m ops-request-controller Start to process the Reconfiguring opsRequest "cluster-hkjsxx-reconfiguring-jcptq" in Cluster: cluster-hkjsxx
Normal Running 18m (x2 over 19m) cluster-controller Cluster: cluster-hkjsxx is ready, current phase is Running
Normal Processed 18m cluster-controller Reconfiguring opsRequest: cluster-hkjsxx-reconfiguring-jcptq has been processed
Normal ComponentPhaseTransition 18m (x2 over 18m) cluster-controller Component workload updated
Warning VerticalScaling 18m cluster-controller VerticalScaling opsRequest: cluster-hkjsxx-verticalscaling-qgldj is processing
Normal VerticalScaling 18m ops-request-controller Start to process the VerticalScaling opsRequest "cluster-hkjsxx-verticalscaling-qgldj" in Cluster: cluster-hkjsxx
Normal PreCheckSucceed 18m (x2 over 20m) cluster-controller The operator has started the provisioning of Cluster: cluster-hkjsxx
Warning ComponentsNotReady 18m cluster-controller pods are unavailable in Components: [postgresql], refer to related component message in Cluster.status.components
Normal WaitingForProbeSuccess 18m (x5 over 18m) cluster-controller Waiting for probe success
Warning ReplicasNotReady 18m cluster-controller pods are not ready in Components: [postgresql], refer to related component message in Cluster.status.components
Warning ApplyResourcesFailed 17m cluster-controller Operation cannot be fulfilled on statefulsets.apps "cluster-hkjsxx-postgresql": the object has been modified; please apply your changes to the latest version and try again
Normal ApplyResourcesSucceed 17m (x3 over 20m) cluster-controller Successfully applied for resources
Normal VolumeExpansion 17m ops-request-controller Start to process the VolumeExpansion opsRequest "cluster-hkjsxx-volumeexpansion-fxpt8" in Cluster: cluster-hkjsxx
Normal Stop 16m ops-request-controller Start to process the Stop opsRequest "cluster-hkjsxx-stop-g25md" in Cluster: cluster-hkjsxx
Normal Start 15m ops-request-controller Start to process the Start opsRequest "cluster-hkjsxx-start-6425x" in Cluster: cluster-hkjsxx
Normal ComponentPhaseTransition 15m (x5 over 19m) cluster-controller Running: true, PodsReady: true, PodsTimedout: false
Normal Reconfiguring 15m ops-request-controller Start to process the Reconfiguring opsRequest "cluster-hkjsxx-reconfiguring-wgrrd" in Cluster: cluster-hkjsxx
Normal HorizontalScaling 13m ops-request-controller Start to process the HorizontalScaling opsRequest "cluster-hkjsxx-horizontalscaling-xf9hj" in Cluster: cluster-hkjsxx
Normal Restart 12m ops-request-controller Start to process the Restart opsRequest "cluster-hkjsxx-restart-rg6z4" in Cluster: cluster-hkjsxx
Warning Unhealthy 106s (x4 over 11m) event-controller Pod cluster-hkjsxx-postgresql-0: Readiness probe failed: 127.0.0.1:5432 - no response
Warning Unhealthy 96s (x5 over 19m) event-controller Pod cluster-hkjsxx-postgresql-1: Readiness probe failed: 127.0.0.1:5432 - no response
Warning Unhealthy 66s (x6 over 10m) event-controller Pod cluster-hkjsxx-postgresql-2: Readiness probe failed: 127.0.0.1:5432 - no response
Describe the bug
postgresql cluster restart error.
To Reproduce
Steps to reproduce the behavior:
describe cluster
logs pod
logs kubeblocks
Expected behavior
postgresql cluster restart success.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: