Hi all, I have Airbyte installed on-prem using doc...
# help-api-cli-orchestration
g
Hi all, I have Airbyte installed on-prem using docker with 0.50.19 version. when I'm trying to list jobs using GET /v1/jobs I receive {"type":"about:blank","status":500} (even though I have some jobs in airbyte). the request:
Copy code
curl --request GET \   
     --url 'localhost:8006/v1/jobs' \
     --header 'accept: application/json' \
     -u '<user>:<pass>'
In the logs of airbyte-api-server docker, I see an uncaught exception with a long trace: 2023-08-23 171734 ERROR i.m.h.s.RouteExecutor(logException):444 - Unexpected error occurred: Unexpected value 'CREATEDAT' java.lang.IllegalArgumentException: Unexpected value 'CREATEDAT' .... It is worth mentioning that other API calls work OK Can anyone help me with that?
m
Same for me, @Riley Brook (Airbyte) fyi
r
ℹ️ <!subteam^S04732XH5SA|@dev-platform-enablement-group>
t
thanks for bringing this up Gilad! we found the issue and the fix should be in the next version which we hope to release sometime tomorrow
g
Thank you!
e
Hey guys, it happens to me as well, any updates about the new version?
t
This fix should be out in
v0.50.23
, lmk if you’re still seeing the issue in that version
g
The issue was fixed thank you very much! 🙏 but now when I'm getting back the list of jobs and trying to get the job status using one of the job_ids in the list I always get 404. I didn't see anything strange in the logs. I'm sending the requests this way (I'm using version 0.50.26 in docker on-prem in EC2) curl --request GET --url 'localhost:8006/v1/jobs/<job_id>' --header 'Accept: application/json' -u 'user:pass'
b
I get the same issue when hitting the
job/{job_id}
endpoint. A valid
job_id
that was just provided returns a 404
j
Same here. For now the old API still works:
Copy code
job_id = 38
url = "<http://localhost:8000/api/v1/jobs/get>"
data = {
    "id": job_id
}
job_response = <http://requests.post|requests.post>(url=url, json=data, headers=headers)
j
Thanks for the detail here - we’re looking into the 404s on the jobs endpoint.
Hi all, this should be resolved with version v0.50.28. Please let us know if you run into additional issues!