The e2term component does not get deployed and keeps restarting with status "CrashLoopBackOff".

Looking at the RIC logs, it seems that the e2mgr pod does not have routing rules for message type 1101. I am suspecting that this could be the reason why e2term keeps restarting.

Another possibility could be on helm charts. I found some routing rules inconsistencies on e2mgr while running the following command:

$ ~/user/dep/ric-dep/helm/e2mgr$ helm install --debug --dry-run e2mgr . -n ricplt

—

Source: e2mgr/templates/configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: configmap-ricplt-e2mgr-router-configmap
  namespace: ricplt
data:
  rmr_verbose: |
    0
  router.txt: |
    newrt|start
    ... omitted ...
    rte|1101|service-ricplt-e2term-rmr.ricplt:38000
    ... omitted ...
    newrt|end

—

Should not message type 1101 be service-ricplt-e2term-rmr-alpha.ricplt as shown in the attached log file "e2term.txt" ?
But, what puzzles me is that the log collected from e2mgr (file "e2mgr.txt") suggests that the routing rule for message type 1101  is not available on e2mgr's routing table.

I followed the instructions available at: https://docs.o-ran-sc.org/projects/o-ran-sc-it-dep/en/latest/installation-guides.html#ric-platform

Thank you.