How to Troubleshoot the Apicurio v3 Upgrade

This guide shows you how to fix the known failures of the Apicurio Registry v2 to v3 upgrade: a non-empty registry on import, artifacts without versions, a crashing v3 pod, an unreachable UI and an Auth Proxy port conflict.

Type

How-to guide

Goal

Get a failed step of the Apicurio v3 upgrade working again.

Audience

Platform Operator with Helm and kubectl access to the Axual Streaming release in the kafka namespace.

When to use

Use this guide when a step in Upgrade Apicurio Registry from v2 to v3 fails.

Contents

The sections below cover each task in this guide:

Prerequisites

You need Helm and kubectl access to the Axual Streaming release in the kafka namespace, and the upgrade guide of the step that failed, so you can re-run that step.

Known upgrade failures

Find the symptom in the table below and apply the fix:

Symptom Cause Solution

Registry is not empty on import

Data from a previous import exists

Restore the Apicurio v3 topics (delete the three v3 topics and restart the v3 pod), then re-run the import

Artifacts imported but show 0 versions

Events topic missing, or no ACLs (Access Control Lists)

Verify the events topic exists and ACLs are set for the Apicurio principal

v3 pod stuck in CrashLoopBackOff

Kafka topics missing or wrong cleanup policy

Check the init container logs

UI shows "Unable to connect"

registryApiUrl not set, or not reachable from the browser

Set ui.config.registryApiUrl to the public HTTPS URL

Auth Proxy or backend crashes on startup

Port 8081 conflict between the Auth Proxy and the backend

Set authProxy.port and authProxy.config.server.port to 8082, and backend-service to http://localhost:8081

Verify the fix

Re-run the step that failed and check its result with the verification in the same guide: