search

FIWARE / load-tests

:chart_with_upwards_trend: Load tests to run against installations of FIWARE Components - NGSI Context Brokers running on scalable test architecture scenarios and installed with and without additional FIWARE microservices.
MIT License
6 stars 2 forks source link

Orion-LD Deployment Fails #84

Open dalxds opened 3 years ago

dalxds commented 3 years ago

Following the config files for deployment, I've created a new Helm Chart that has orion-ld, mongodb and timescale as deps.

The values.yaml of the Chart can be seen below:

mongodb:
  architecture: standalone
  useStatefulSet: true
  auth:
    enabled: false
  tls:
    enabled: false
    autoGenerated: false
  podSecurityContext:
    enabled: false
  containerSecurityContext:
    enabled: false

orion:
  broker:
    troe:
      enabled: true
      dbHost: timescale
      dbUser: postgres
      dbPort: 5432
      dbPassword: gmruukctFW1j93e5r7RI5ZIwLNvG5oxE
    mutexPolicy: none
    reqPoolSize: 32
    db:
      hosts:
        - neptune-eew-mongodb-0.neptune-eew-mongodb.default.svc.cluster.local
    logging:
      level: DEBUG

timescaledb-single:
  replicaCount: 1
  backup:
    enabled: false
  podManagementPolicy: Parallel
  serviceAccount:
    create: false

I followed the guide in the timescaledb charts to create the secrets and then used this command to decrypt and use the db password.

However, Orion-LD failes to connect to the timescale-db. Logs from the broker can be found below:

time=2021-08-31T10:05:07.842Z | lvl=INFO | corr=N/A | trans=N/A | from=N/A | srv=N/A | subsrv=N/A | comp=Orion | op=mongoConnectionPool.cpp[212]:mongoConnect | msg=Successful connection to database
time=2021-08-31T10:05:07.843Z | lvl=INFO | corr=N/A | trans=N/A | from=N/A | srv=N/A | subsrv=N/A | comp=Orion | op=MongoGlobal.cpp[245]:mongoInit | msg=Connected to mongo at neptune-eew-mongodb-0.neptune-eew-mongodb.default.svc.cluster.local:orion
2021/08/31 10:05:07.0848: [    1]:  WARNING:       mongoc: Falling back to malloc for counters.
time=2021-08-31T10:05:07.857Z | lvl=ERROR | corr=N/A | trans=N/A | from=N/A | srv=N/A | subsrv=N/A | comp=Orion | op=pgDatabasePrepare.cpp[49]:pgDatabasePrepare | msg=Database Error (unable to connect to postgres - connection/status: 0x5574573d6700/1)
time=2021-08-31T10:05:07.857Z | lvl=ERROR | corr=N/A | trans=N/A | from=N/A | srv=N/A | subsrv=N/A | comp=Orion | op=troeInit.cpp[41]:troeInit | msg=Basic Postgres Problem - Temporal Representation of Entities is not possible
time=2021-08-31T10:05:07.857Z | lvl=FATAL | corr=N/A | trans=N/A | from=N/A | srv=N/A | subsrv=N/A | comp=Orion | op=orionld.cpp[1015]:main | msg=Database Error (unable to initialize the layer for Temporal Representation of Entities)

Any help would be appreciated. Thanks!

Also, would it be possible to reference the Secret to get the timescaledb password and not provided directly in the values.yaml?

wistefan commented 3 years ago

Hi, sorry for the late response. The error comes through orions incompatibility with TimescaleDB 2.x, we currently only support 1.x. I updated the values in #86, please try again with that(be aware that the timescale helm-chart to be used should be v0.7.1). Directly referencing the secret is currently not possible, its not supported by the orion-chart.

Best, Stefan