egeria: IGC connector not loading - user/env error - improve audit msgs

Using the odpi-egeria-vdc helm chart with the following override ie

helm install vdc odpi-egeria-vdc -f ~/etc/cloud_igc.yaml

where the yaml contains: (hostname/ip obfuscated)

ibmigc:
  enabled: true
  internal:
    enabled: false
  external:
    enabled: true
    ip: "111.222.333.444"
    hostname: "igc.openmetadata.mydomain.com"
    ports:
      https: "9446"
      broker: "59092"

results in all the pods etc starting up. However the IGC proxy fails to initialize correctly with:

Fri Jan 03 14:31:48 GMT 2020 ibmigc Exception OMRS-AUDIT-0035 The connector to the local repositorys event mapper failed with a {0} exception and the following error message: {1}

Two issues here a) The audit message is incorrectly formatted - preventing customer PD b) Why the actual failure

The same error was reported on slack at https://odpi.slack.com/archives/CBPRDQPRC/p1578028854030200 – this was running locally, not using containers. I tried the helm chart to get my own environment working for debugging and comparison.

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 15 (15 by maintainers)

Commits related to this issue

#2348 update LOADER_PATH to point to actual jar Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com> — committed to planetf1/egeria by planetf1 4 years ago
Avoids swallowing class-related exceptions when classes are provided at runtime to resolve #2348 Signed-off-by: Christopher Grote <chris@thegrotes.net> — committed to cmgrote/egeria by cmgrote 4 years ago

Most upvoted comments

a) It looks like all of the messages in OMRSAuditCode use numerically-indexed formatters {0}, {1}, etc – whereas our other classes all seem to just use {} with the order implied by the order the arguments are passed to the formatting method (?)

b) This is likely due to either not being able to resolve the address between the host running Egeria and the IGC hostname, or that the IGC host’s Kafka bus believes it is a different hostname than the one it was initially called on.

I’ll try to do some further testing related to (b) on my side and see if I can add more meaningful audit log messages on the IGC event mapper side…

Umm … All auditlog classes should be using the numberically indexed formatters because these are translatable messages and the order can/will change with different languates - which modules are not using number?

mandy-chessell on Jan 3, 2020