My Oracle Support Banner

ASAP CN: Unable To Create The Order Balancer Instance Due To CrashLoopBackOff Status (Doc ID 2995266.1)

Last updated on JANUARY 23, 2024

Applies to:

Oracle Communications ASAP - Version 7.4.0.0.0 and later
Information in this document applies to any platform.

Goal

Created the Order Balancer image successfully in customer environment. However, unable to create the instance, getting following error:


Events:
  Type Reason Age From Message
  ---- ------ ---- ---- -------
  Normal Scheduled 10m default-scheduler Successfully assigned <POD_NAME> to <NODE_NAME>
  Normal Pulling 10m kubelet Pulling image "<IMAGE_NAME>"
  Normal Pulled 10m kubelet Successfully pulled image "<IMAGE_NAME>" in 11.238852987s (11.238856373s including waiting)
  Normal Created 8m36s (x5 over 10m) kubelet Created container ob
  Normal Started 8m36s (x5 over 10m) kubelet Started container ob
  Normal Pulled 8m36s (x4 over 9m59s) kubelet Container image "<IMAGE_NAME>" already present on machine
  Warning BackOff 9s (x46 over 9m58s) kubelet Back-off restarting failed container ob in pod <POD_NAME>
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.