This message was deleted.
# opals
Slackbot
11/23/2022, 1:56 PMThis message was deleted.
f
Filip
11/23/2022, 1:58 PMHey @Sumesh Sukumaran - is this the only error you are getting from the PDP when running the webhook?
s
Sumesh Sukumaran
11/23/2022, 2:02 PMYeah this error and some warnings
Sumesh Sukumaran
11/23/2022, 2:05 PMDo I need to configure polling and webhook simultaneously?
a
Asaf Cohen
11/23/2022, 2:07 PMHi @Sumesh Sukumaran is the webhook secret defined in the docker compose the same one you use in github?
Asaf Cohen
11/23/2022, 2:08 PMAlso, we would need the full OPAL server logs to understand what went wrong.
Typically 503 means that OPAL server did not yet clone the policy repo or could not clone it.
s
Sumesh Sukumaran
11/23/2022, 2:10 PMYeah @Asaf Cohen I am using the same secret in both the places.
a
Asaf Cohen
11/23/2022, 2:11 PM(you can send the logs privately to us if you prefer)
Asaf Cohen
11/23/2022, 2:17 PMthe issue is a race condition between the opal server and opal client
Asaf Cohen
11/23/2022, 2:18 PMsince you started them at the very same time, OPAL server took time to clone the policy repo, and in the meanwhile correctly returned 503.
if you would start OPAL client 20 seconds after OPAL server it would not happen
🤘 1
Asaf Cohen
11/23/2022, 2:19 PMi know this because this line in the logs shows after the 503 error:
Copy code
opal_common.git.repo_cloner | INFO | Clone succeededs
Sumesh Sukumaran
11/23/2022, 2:23 PMThanks @Asaf Cohen. Yeah now its working when I restarted the OPAL client 👍
❤️ 1
2 Views