Getting a 503 on GET /policy?path=. but no errors anywhere being outputted

[maclermo]

Hi,

I am running the latest version of opal on K3s.

Right now, my server is connecting to a private Git repository using a keypair.

Here are my env vars:

OPAL_DATA_CONFIG_SOURCES: {"config":{"entries":[{"dst_path":"/static","topics":["policy_data"],"url":"http://opal-server.REDACTED:7002/policy-data"}]}}
OPAL_AUTH_PRIVATE_KEY: -----BEGIN RSA PRIVATE KEY-----_MIIJKQIBAAKCArx[...]Z7yuCpK1CsXZs_-----END RSA PRIVATE KEY----- 
OPAL_AUTH_PUBLIC_KEY: ssh-rsa AAAAB3[...]fklB8VQ== REDACTED@REDACTED
OPAL_AUTH_MASTER_TOKEN: REDACTED
OPAL_POLICY_REPO_URL: git@REDACTED:2222/REDACTED.git
OPAL_POLICY_REPO_SSH_KEY:  -----BEGIN OPENSSH PRIVATE KEY-----_b3Blbn[...]5jYQECAw==_-----END OPENSSH PRIVATE KEY-----
OPAL_POLICY_REPO_MAIN_BRANCH: develop
OPAL_POLICY_REPO_POLLING_INTERVAL:  30
OPAL_LOG_MODULE_EXCLUDE_LIST: []

The client queries the server and outputs this:

|WARNING | Unexpected response code 503: {'detail': 'policy repo was not found'}

Help getting the full logs would be very appreciated.

[orweis]

Hi @maclermo - the error seems pretty straight forward - OPAL tried checking out your repository, and failed.
This is probably a configuration issue - wrong url, key, protocol or otherwise. You can try the parameters with the local git client, or even with git-python, which OPAL uses - to try and figure out what's wrong with the configuration

[maclermo]

Are you suggesting a 503 error without any details is straightforward? Why can't you just output git-python to the console like any other module?

[maclermo]

In all fairness the error is misleading. The git repo was found but there is an error cloning it! It can be interpreted as missing the env var!

[orweis]

Sounds like you've debugged the issue. I'm happy to hear that.

[maclermo]

I have not found the error yet... Cloning from the REPL works fine! See why this is hard to debug?

[orweis]

Can you share the OPAL server log?

[maclermo]

The clone path wasn't writable. I was able to solve the issue by simply changing the BASE_DIR.