planetf1
commented
1 year ago It's a missing key ....
The default security connector is the encrypted file store.
So to get this to work you’d need to also encrypt using google tink, and store the key in the data directory. You could likely copy both the encrypted file and key from where you created the file. See https://github.com/odpi/egeria/tree/main/open-metadata-implementation/adapters/ope[…]n-store-connectors/configuration-encrypted-file-store-connector
Key is generated data/platform/keys/keystore_ or you can create your own
Alternatively you can use the non-encrypted file store, but to use this you have to issue a REST API call to set the appropriate store to use in the platform configuration … (These simple things are what made configuring in k8s tricky, especially for persistence/restart)
It’s also possible there are permissions issues with the image when trying to do this. I suggest ssh’ing into the container & check the required files are readable (minimum - for the key) and writeable (config - as the platform ALSO WRITES to this file — another pain point!)
dwolfson
davidradl
github-actions[bot]
I've been trying to create a docker container with a pre-defined configuration. The strategy that I'm exploring is to:
1) start from an Egeria build (for convenience I am doing this in IntelliJ) 2) Start Egeria normally 3) Configure a single Egeria metadata access server with a repository using commands with Python and/or Postman 4) Test the configured Egeria 5) Stop the server 6) Copy the contents (including the data directory) to/open-metadata-resources/open-metadata-deployment/docker/egeria/build/assembly
7) Use the Dockerfile in /open-metadata-resources/open-metadata-deployment/docker/egeria to build the container
8) Run the container (have tried a variety of arguments) - the image comes up and looks normal
Now at this point, I can query the platform and it indicates it is active - but it doesn't see any configuration for the server. If I then try to configure the server - I get the error:
"class": "VoidResponse", "relatedHTTPCode": 500, "exceptionClassName": "org.odpi.openmetadata.adminservices.ffdc.exception.OMAGConfigurationErrorException", "exceptionCausedBy": "org.odpi.openmetadata.frameworks.connectors.ffdc.OCFRuntimeException", "actionDescription": "setGraphLocalRepository", "exceptionErrorMessage": "OMAG-ADMIN-500-001 Method setGraphLocalRepository for OMAG server DMP_metadataServer returned an unexpected exception of org.odpi.openmetadata.frameworks.connectors.ffdc.OCFRuntimeException with message ENCRYPTED-DOC-STORE-400-010 Unable to find any file containing keys in the secure directory, and unable to remove the directory; exception was java.nio.file.DirectoryNotEmptyException with message data/platform/keys/keystore_zZNlcxGXFuIPtqxEDFPmYspYKRTNW618.", "exceptionErrorMessageId": "OMAG-ADMIN-500-001", "exceptionErrorMessageParameters": [ "DMP_metadataServer", "setGraphLocalRepository", "org.odpi.openmetadata.frameworks.connectors.ffdc.OCFRuntimeException", "ENCRYPTED-DOC-STORE-400-010 Unable to find any file containing keys in the secure directory, and unable to remove the directory; exception was java.nio.file.DirectoryNotEmptyException with message data/platform/keys/keystore_zZNlcxGXFuIPtqxEDFPmYspYKRTNW618." ], "exceptionSystemAction": "The system is unable to work with the OMAG server. No change was made to the server's configuration document.", "exceptionUserAction": "This is likely to be either a configuration, operational or logic error. Look for other errors. Validate the request. If you are stuck, raise an issue." }
I also get this error (or something very similar) if I run the container with Autostart enabled.
I was able to run Egeria in intelliJ, configure it, stop it, and then rerun it and be able to use the saved configuration..
Is it the way that I'm building the container?
Thoughts and ideas welcome..