This message was deleted.
# opal
s
This message was deleted.
r
I see same for sample repo
Copy code
|ERROR  | cannot clone policy repo: Cmd('git') failed due to: exit code(128)
  cmdline: git clone -v --branch=master -- <https://github.com/permitio/opal-example-policy-repo> /opal/regoclone/opal_repo_clone
  stderr: 'Cloning into '/opal/regoclone/opal_repo_clone'...
fatal: unable to access '<https://github.com/permitio/opal-example-policy-repo/>': Could not resolve host: <http://github.com|github.com>
'
o
The error you are getting seems to indicate some DNS resolving issue. Are you able to run the git command manually from the container, or where it's running?
r
Looks like a DNS issue, my kind cluster somehow not able to make connections
@Or Weis is
OPAL_SERVER_URL
not a mandatory field in
client.extraEnv
in values.yaml https://github.com/permitio/opal-helm-chart/blob/master/values.yaml
I am seeing error in the client logs
Copy code
RPC Connection failed - [Errno -2] Name or service not known
2023-05-28T06:40:52.040181+0000 | fastapi_websocket_rpc.websocket_rpc_c...| INFO  | Trying server - <ws://opal-server:7002/ws>
2023-05-28T06:40:54.064353+0000 | fastapi_websocket_rpc.websocket_rpc_c...| INFO  | RPC Connection failed - [Errno -2] Name or service not known
Copy code
image:
  registry: <http://docker-master.cdaas.cloud.com|docker-master.cdaas.cloud.com>
postgresImageRegistry: <http://docker-master.cdaas.cloud.com|docker-master.cdaas.cloud.com>
imagePullSecrets: [ ]

server:
  port: 7002
  policyRepoUrl: "<https://username:6>-pat@gitlab-odx.com/code/titan/opa-policies-and-data.git"
  policyRepoClonePath: null
  policyRepoMainBranch: main
  pollingInterval: 10
  dataConfigSources:
    config:
      entries: 
      - url: <http://opal-server:7002/policy-data>
        topics: ["policy_data"]
        dst_path: "/static"
  broadcastUri: null
  broadcastPgsql: true
  uvicornWorkers: 4
  replicas: 1

client:
  port: 7000
  opaPort: 8181
  replicas: 1
  extraEnv:
    OPAL_OPA_HEALTH_CHECK_POLICY_ENABLED: True
    OPAL_DATA_UPDATER_ENABLED: True
    OPAL_SERVER_URL: <http://opal-server:7002>
o
Hi @raghanag you still need to configure your client to find the server at the address you set it at up at. The error you got clearly states that the address you used
<http://opal-server:7002|http://opal-server:7002>
could not be resolved
r
you meant the
OPAL_SERVER_URL: <http://opal-server:7002>
is not enough or the client unable to connect?
o
It's enough. But the address you set can't be resolved
r
may i ask why
it use to work only after upgrading to 0.6.1 charts it stopped working
o
This has nothing to do with OPAL
The address doesn't exist in your network, or dns doesn't work