redpanda-data / redpanda-data/console

Failed to get schemas from apicurio

Open
#1,743 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

backend feature
Dominant language
TypeScript
Stars
4.3k
Forks
432
Avg merge
3d 6h
Merged PRs (30d)
40

Description

Hello, redpanda console is throwing 502 when retrieving the schemas from apicuruo registry without using the confluent compatibility endpoint.
Failed to retrieve schema registry types from the schema registry: failed to get compatibility: RESTEASY003210: Could not find resource for full path: http://<URL>/apis/registry/v2/config

Logs
{"level":"error","ts":"2025-04-27T11:29:36.828Z","msg":"Sending REST error","route":"/api/schema-registry/schemas/types","method":"GET","status_code":502,"remote_address":"127.0.0.1:56350","public_error":"Failed to retrieve schema registry types from the schema registry: RESTEASY003210: Could not find resource for full path: http:///apis/registry/v2/schemas/types","error":"RESTEASY003210: Could not find resource for full path: http:///apis/registry/v2/schemas/types"}
{"level":"error","ts":"2025-04-27T11:29:36.830Z","msg":"Sending REST error","route":"/api/schema-registry/config","method":"GET","status_code":502,"remote_address":"127.0.0.1:56368","public_error":"Failed to retrieve schema registry types from the schema registry: failed to get compatibility: RESTEASY003210: Could not find resource for full path: http:///apis/registry/v2/config","error":"failed to get compatibility: RESTEASY003210: Could not find resource for full path: http:///apis/registry/v2/config"}
{"level":"error","ts":"2025-04-27T11:29:36.833Z","msg":"Sending REST error","route":"/api/schema-registry/mode","method":"GET","status_code":502,"remote_address":"127.0.0.1:56372","public_error":"Failed to retrieve schema registry mode from the schema registry: failed to get mode: RESTEASY003210: Could not find resource for full path: http:///apis/registry/v2/mode","error":"failed to get mode: RESTEASY003210: Could not find resource for full path: http:///apis/registry/v2/mode"}
{"level":"error","ts":"2025-04-27T11:29:36.835Z","msg":"Sending REST error","route":"/api/schema-registry/subjects","method":"GET","status_code":502,"remote_address":"127.0.0.1:56392","public_error":"Failed to retrieve subjects from the schema registry: RESTEASY003210: Could not find resource for full path: http:///apis/registry/v2/subjects","error":"RESTEASY003210: Could not find resource for full path: http:///apis/registry/v2/subjects"}

Redpanda Console version
3.0.0

Redpanda Chart config version
This is the schema registry config of the redpanda console chart
schemaRegistry:
enabled: true
urls: ["http:///apis/registry/v2"]

Redpanda version
Redpanda Console (Platform Version v25.1) - (built April 07, 2025) - 56482c3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the 502 responses from the listed schema-registry routes: /api/schema-registry/schemas/types, /config, /mode, and /subjects, using the Apicurio URL configuration shown. Trace how these routes request /apis/registry/v2/config, /schemas/types, /mode, and /subjects; done means they retrieve the corresponding data from Apicurio without requiring the Confluent compatibility endpoint.

Written by the indexing model from the issue text.

Assessment

Tech stack
kafka
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.