Skip to main content
  • EN

Dears,

i am facing issue with restoring a namespace showing the below error, can anyone advise, noting that all the pods were restored in running state but not in ready state

phases:
  - attempt: 3
    endTime: 2024-10-22T15:02:43Z
    errors:
      - cause: '{"cause":{"cause":{"cause":{"cause":{"message":"Specified 4 replicas and
          only have 0 available replicas: could not get Deployment{Namespace:
          default-restore, Name:
          dbs-ac-accessgroup-integration-service-accessgroupintegsvc}: client
          rate limiter Wait returned an error: rate: Wait(n=1) would exceed
          context
          deadline"},"fields":r{"name":"deployment","value":"dbs-ac-accessgroup-integration-service-accessgroupintegsvc"}],"file":"kasten.io/k10/kio/kube/workload/workload.go:38","function":"kasten.io/k10/kio/kube/workload.WaitForWorkloadReady","linenumber":38,"message":"Deployment
          not in ready
          state"},"fields":o{"name":"namespace","value":"default-restore"},{"name":"name","value":"dbs-ac-accessgroup-integration-service-accessgroupintegsvc"}],"file":"kasten.io/k10/kio/exec/phases/phase/restore_app.go:845","function":"kasten.io/k10/kio/exec/phases/phase.(*restoreApplicationPhase).waitForWorkload","linenumber":845,"message":"Error
          waiting for workload to be
          ready"},"file":"kasten.io/k10/kio/exec/phases/phase/restore_app.go:396","function":"kasten.io/k10/kio/exec/phases/phase.(*restoreApplicationPhase).restoreApp","linenumber":396,"message":"Failed
          to restore
          workloads"},"file":"kasten.io/k10/kio/exec/internal/runner/phase_runner.go:144","function":"kasten.io/k10/kio/exec/internal/runner.(*phaseRunner).execPlannedPhase","linenumber":144,"message":"Failure
          in planned phase"}'
        message: Job failed to be executed
      - cause: '{"cause":{"cause":{"cause":{"cause":{"message":"Specified 4 replicas and
          only have 0 available replicas: could not get Deployment{Namespace:
          default-restore, Name:
          identity-onespan-auth-service-onespanauthservice}: client rate limiter
          Wait returned an error: context deadline
          exceeded"},"fields":i{"name":"deployment","value":"identity-onespan-auth-service-onespanauthservice"}],"file":"kasten.io/k10/kio/kube/workload/workload.go:38","function":"kasten.io/k10/kio/kube/workload.WaitForWorkloadReady","linenumber":38,"message":"Deployment
          not in ready
          state"},"fields":d{"name":"namespace","value":"default-restore"},{"name":"name","value":"identity-onespan-auth-service-onespanauthservice"}],"file":"kasten.io/k10/kio/exec/phases/phase/restore_app.go:845","function":"kasten.io/k10/kio/exec/phases/phase.(*restoreApplicationPhase).waitForWorkload","linenumber":845,"message":"Error
          waiting for workload to be
          ready"},"file":"kasten.io/k10/kio/exec/phases/phase/restore_app.go:396","function":"kasten.io/k10/kio/exec/phases/phase.(*restoreApplicationPhase).restoreApp","linenumber":396,"message":"Failed
          to restore
          workloads"},"file":"kasten.io/k10/kio/exec/internal/runner/phase_runner.go:144","function":"kasten.io/k10/kio/exec/internal/runner.(*phaseRunner).execPlannedPhase","linenumber":144,"message":"Failure
          in planned phase"}'
        message: Job failed to be executed
      - cause: '{"cause":{"cause":{"cause":{"cause":{"message":"Specified 4 replicas and
          only have 0 available replicas: Context done while polling: context
          deadline
          exceeded"},"fields":s{"name":"deployment","value":"nbb-account-opening-service-accountopening"}],"file":"kasten.io/k10/kio/kube/workload/workload.go:38","function":"kasten.io/k10/kio/kube/workload.WaitForWorkloadReady","linenumber":38,"message":"Deployment
          not in ready
          state"},"fields":f{"name":"namespace","value":"default-restore"},{"name":"name","value":"nbb-account-opening-service-accountopening"}],"file":"kasten.io/k10/kio/exec/phases/phase/restore_app.go:845","function":"kasten.io/k10/kio/exec/phases/phase.(*restoreApplicationPhase).waitForWorkload","linenumber":845,"message":"Error
          waiting for workload to be
          ready"},"file":"kasten.io/k10/kio/exec/phases/phase/restore_app.go:396","function":"kasten.io/k10/kio/exec/phases/phase.(*restoreApplicationPhase).restoreApp","linenumber":396,"message":"Failed
          to restore
          workloads"},"file":"kasten.io/k10/kio/exec/internal/runner/phase_runner.go:144","function":"kasten.io/k10/kio/exec/internal/runner.(*phaseRunner).execPlannedPhase","linenumber":144,"message":"Failure
          in planned phase"}'
        message: Job failed to be executed
    name: Restoring Application Components
    startTime: 2024-10-22T13:26:32Z
    state: failed
    updatedTime: 2024-10-22T15:02:43Z

@ali.k Thank you for creating a topic here.

As you described, K10 waits for the pods to be in ready state before it completes the restore as a successful one by default.

If the pod is not ready, THen it means that it has some dependency or readinessProbes that is failing to get the pod to ready state.

Looking at the pod logs, events and trying to find out the readinessProbe and if it is dependent on an external factor might help you troubleshoot the issue.

Comment


Terms & Conditions