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.

Sign up for GitHub

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

Jump to bottom

[BUG]cluster is always deleting after delete with kb upgrade from 0.8.2 to 0.9 #7118

Closed
ahjing99 opened this issue Apr 22, 2024 · 1 comment
Closed

[BUG]cluster is always deleting after delete with kb upgrade from 0.8.2 to 0.9 #7118

ahjing99 opened this issue Apr 22, 2024 · 1 comment
Assignees
@free6om
Labels
kind/bug Something isn't working severity/major Great chance user will encounter the same problem
Milestone
Release 0.9.0

Comments

@ahjing99
Copy link
Collaborator

  1. Install kb 0.8.2
  2. Create clusters
  `kbcli cluster create  kafka kafka-szkmli                 --mode='combined'                 --cpu=0.5                 --memory=0.5                 --storage=1                 --availability-policy=none --termination-policy=WipeOut --monitoring-interval=0 --version=kafka-3.3.2  --storage-enable=true                 --meta-storage=1 --replicas=3  --namespace default `

Cluster kafka-szkmli created
  1. Upgrade kb
➜  ~ kbcli kubeblocks upgrade --version 0.9.0-beta.10
Current KubeBlocks version 0.8.2.
Kubernetes version 1.28.7
Kubernetes provider GKE
kbcli version 0.9.0-beta.1
Upgrade KubeBlocks from 0.8.2 to 0.9.0-beta.10
Please type 'Yes/yes' to confirm your operation: yes
Add and update repo kubeblocks                     OK
Keep addons                                        OK
Stop KubeBlocks 0.8.2                              OK
Stop DataProtection                                OK
Upgrade CRDs                                       OK
Upgrading KubeBlocks to 0.9.0-beta.10              OK

KubeBlocks has been upgraded to 0.9.0-beta.10 SUCCESSFULLY!

-> Basic commands for cluster:
    kbcli cluster create -h     # help information about creating a database cluster
    kbcli cluster list          # list all database clusters
    kbcli cluster describe <cluster name>  # get cluster information

-> Uninstall KubeBlocks:
    kbcli kubeblocks uninstall
  1. Delete cluster
➜  ~ kbcli cluster delete kafka-szkmli
clusters to be deleted:[kafka-szkmli]
Please type the name again(separate with white space when more than one): kafka-szkmli
Cluster kafka-szkmli deleted
  1. cluster is always deleting
➜  ~ k describe cluster kafka-szkmli
Name:         kafka-szkmli
Namespace:    default
Labels:       app.kubernetes.io/instance=kafka-szkmli
              app.kubernetes.io/version=3.3.2
              clusterdefinition.kubeblocks.io/name=kafka
              clusterversion.kubeblocks.io/name=kafka-3.3.2
              helm.sh/chart=kafka-cluster-0.8.1
Annotations:  kubeblocks.io/enabled-pod-ordinal-svc: broker
              kubeblocks.io/extra-env:
                {"KB_KAFKA_ENABLE_SASL":"false","KB_KAFKA_BROKER_HEAP":"-XshowSettings:vm -XX:MaxRAMPercentage=100 -Ddepth=64","KB_KAFKA_CONTROLLER_HEAP":...
API Version:  apps.kubeblocks.io/v1alpha1
Kind:         Cluster
Metadata:
  Creation Timestamp:             2024-04-22T05:53:36Z
  Deletion Grace Period Seconds:  0
  Deletion Timestamp:             2024-04-22T07:00:43Z
  Finalizers:
    cluster.kubeblocks.io/finalizer
  Generation:  3
  Managed Fields:
    API Version:  apps.kubeblocks.io/v1alpha1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .:
          f:kubeblocks.io/enabled-pod-ordinal-svc:
          f:kubeblocks.io/extra-env:
        f:labels:
          .:
          f:app.kubernetes.io/instance:
          f:app.kubernetes.io/version:
          f:helm.sh/chart:
      f:spec:
        .:
        f:affinity:
          .:
          f:podAntiAffinity:
          f:tenancy:
        f:clusterDefinitionRef:
        f:clusterVersionRef:
        f:services:
        f:terminationPolicy:
    Manager:      kbcli
    Operation:    Update
    Time:         2024-04-22T05:53:36Z
    API Version:  apps.kubeblocks.io/v1alpha1
    Fields Type:  FieldsV1
    fieldsV1:
      f:metadata:
        f:finalizers:
          .:
          v:"cluster.kubeblocks.io/finalizer":
        f:labels:
          f:clusterdefinition.kubeblocks.io/name:
          f:clusterversion.kubeblocks.io/name:
      f:spec:
        f:componentSpecs:
    Manager:      manager
    Operation:    Update
    Time:         2024-04-22T06:24:06Z
    API Version:  apps.kubeblocks.io/v1alpha1
    Fields Type:  FieldsV1
    fieldsV1:
      f:status:
        .:
        f:clusterDefGeneration:
        f:components:
          .:
          f:broker:
            .:
            f:phase:
            f:podsReady:
            f:podsReadyTime:
        f:conditions:
        f:observedGeneration:
        f:phase:
    Manager:         manager
    Operation:       Update
    Subresource:     status
    Time:            2024-04-22T07:00:44Z
  Resource Version:  262782
  UID:               cfa94ddc-c08c-4918-bb9d-be578c78462c
Spec:
  Affinity:
    Pod Anti Affinity:     Preferred
    Tenancy:               SharedNode
  Cluster Definition Ref:  kafka
  Cluster Version Ref:     kafka-3.3.2
  Component Specs:
    Component Def:      kafka-combine
    Component Def Ref:  kafka-server
    Monitor:            false
    Name:               broker
    Replicas:           3
    Resources:
      Limits:
        Cpu:     500m
        Memory:  512Mi
      Requests:
        Cpu:          500m
        Memory:       512Mi
    Service Version:  3.3.2
    Volume Claim Templates:
      Name:  data
      Spec:
        Access Modes:
          ReadWriteOnce
        Resources:
          Requests:
            Storage:  1Gi
      Name:           metadata
      Spec:
        Access Modes:
          ReadWriteOnce
        Resources:
          Requests:
            Storage:  1Gi
  Services:
    Component Selector:  broker
    Name:                bootstrap
    Service Name:        bootstrap
    Spec:
      Ports:
        Name:          kafka-client
        Port:          9092
        Protocol:      TCP
        Target Port:   9092
      Type:            ClusterIP
  Termination Policy:  WipeOut
Status:
  Cluster Def Generation:  2
  Components:
    Broker:
      Phase:            Running
      Pods Ready:       true
      Pods Ready Time:  2024-04-22T06:25:08Z
  Conditions:
    Last Transition Time:  2024-04-22T05:53:36Z
    Message:               The operator has started the provisioning of Cluster: kafka-szkmli
    Observed Generation:   2
    Reason:                PreCheckSucceed
    Status:                True
    Type:                  ProvisioningStarted
    Last Transition Time:  2024-04-22T05:53:36Z
    Message:               Successfully applied for resources
    Observed Generation:   2
    Reason:                ApplyResourcesSucceed
    Status:                True
    Type:                  ApplyResources
    Last Transition Time:  2024-04-22T06:25:08Z
    Message:               all pods of components are ready, waiting for the probe detection successful
    Reason:                AllReplicasReady
    Status:                True
    Type:                  ReplicasReady
    Last Transition Time:  2024-04-22T06:25:08Z
    Message:               Cluster: kafka-szkmli is ready, current phase is Running
    Reason:                ClusterReady
    Status:                True
    Type:                  Ready
  Observed Generation:     2
  Phase:                   Deleting
Events:
  Type     Reason                    Age                    From                Message
  ----     ------                    ----                   ----                -------
  Normal   PreCheckSucceed           40m                    cluster-controller  The operator has started the provisioning of Cluster: kafka-szkmli
  Normal   ApplyResourcesSucceed     40m                    cluster-controller  Successfully applied for resources
  Normal   ComponentPhaseTransition  39m                    cluster-controller  component is Updating
  Warning  ReplicasNotReady          39m                    cluster-controller  pods are not ready in Components: [broker], refer to related component message in Cluster.status.components
  Warning  ComponentsNotReady        39m                    cluster-controller  pods are unavailable in Components: [broker], refer to related component message in Cluster.status.components
  Normal   ComponentPhaseTransition  39m                    cluster-controller  component is Running
  Normal   AllReplicasReady          39m                    cluster-controller  all pods of components are ready, waiting for the probe detection successful
  Normal   ClusterReady              39m                    cluster-controller  Cluster: kafka-szkmli is ready, current phase is Running
  Normal   Running                   39m                    cluster-controller  Cluster: kafka-szkmli is ready, current phase is Running
  Normal   DeletingCR                20s (x188 over 3m50s)  cluster-controller  Deleting : kafka-szkmli

➜ ~ kbcli report cluster --with-logs --all-containers kafka-szkmli
reporting cluster information to report-cluster-kafka-szkmli-2024-04-22-15-04-58.zip
processing manifests OK
processing events OK
process pod logs OK
➜ ~ kbcli report kubeblocks --with-logs --all-containers --output yaml
reporting KubeBlocks information to report-kubeblocks-2024-04-22-15-05-10.zip
processing manifests OK
processing events OK
process pod logs OK
report-kubeblocks-2024-04-22-15-05-10.zip
report-cluster-kafka-szkmli-2024-04-22-15-04-58.zip
@ahjing99 ahjing99 added kind/bug Something isn't working severity/major Great chance user will encounter the same problem labels Apr 22, 2024
@ahjing99 ahjing99 added this to the Release 0.9.0 milestone Apr 22, 2024
@free6om
Copy link
Contributor

free6om commented Apr 22, 2024

fixed by #7087

@free6om free6om closed this as completed Apr 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@free6om free6om

Labels
kind/bug Something isn't working severity/major Great chance user will encounter the same problem
Projects
None yet
Milestone
Release 0.9.0
Development

No branches or pull requests
2 participants
@free6om @ahjing99