Issue With Pod Scaling In PS5 OCOMC CNE With FSS Based PVs
(Doc ID 2943080.1)
Last updated on OCTOBER 22, 2024
Applies to:
Oracle Communications Offline Mediation Controller - Version 12.0.0.5.0 and laterInformation in this document applies to any platform.
Symptoms
Customer is trying to setup OCOMC CNE (patch set 5) with hostpath based PVs (backend for PVs is FSS and this FSS is mounted on all worker nodes). When try to scale up the node manager pods and pods status is CrashLoopBackOff and getting the error like compDef.xml: No such file or directory.
The difference between NFS and FSS is that there is no dynamic provisioning of PVs with FSS. Directories required for PVs are pre-created in FSS mount point and Persistent Volume blocks were added for all PVCs.
Snippet of error message:
Abbreviations:
OCOMC: Oracle Communication Offline Mediation Controller
CNE: Cloud Native Environment
PV: Persistent Volume
FSS: File Storage Service
NFS: Network File Sharing protocol
PS: Patch Set
SLF4J: Simple Logging Facade for Java
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |