Creation of new db from backup not possible - more than 63 characters

Hi folks,

I have a interesting issue:

I’ve created a recurring backup job of my pxc db with name backup-apr (generated by everest).
I’ve also created a backup location with name hetzner-fsn-prod
This backup job now creates backups every hour with names cron-<db_name>-hetzner-fsn-prod-2025125570-3hb2e

The Name of my db is 13 characters long which leads in a backup job name of 66 characters.

Now, if I try to create a new DB from one of those backups, I can see the following error in the logs:

2025-01-02T06:00:35Z	ERROR	Reconciler error	{"controller": "databasecluster", "controllerGroup": "everest.percona.com", "controllerKind": "DatabaseCluster", "DatabaseCluster": {"name":"restored-<DB_NAME>","namespace":"db-<DB_NAME>"}, "namespace": "db-<DB_NAME>", "name": "restored-<DB_NAME>", "reconcileID": "fdb2087f-a9c1-4ad8-9ecb-5051e9052df4", "error": "DatabaseCluster.everest.percona.com \"restored-<DB_NAME>\" is invalid: metadata.labels: Invalid value: \"backupStorage-cron-<DB_NAME>-hetzner-fsn-prod-2025125570-3hb2e\": name part must be no more than 63 characters"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).reconcileHandler
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.19.0/pkg/internal/controller/controller.go:316
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.19.0/pkg/internal/controller/controller.go:263
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller[...]).Start.func2.2
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.19.0/pkg/internal/controller/controller.go:224

Which is totally correct, as the value of an annotation must not be longer than 63 characters.

This seems to be a bug for me, as the name of a db and the name of a backup-location can definitely be longer than the names, I’ve used.

Hey @balu,
Please open a bug report on this at https://jira.percona.com/ under the Percona Everest category.

Hi @matthewb,

unfortunately I’m not allowed to file a bug in the everest project:

Greetings, Balu

Ok. I’ll forward this post to one of our Everest managers.

Hi @balu !

There’s a ticket already open for this issue here: Jira

It is currently scheduled to be fixed in 1.5.0 version, but we will try to update the docs with this limitation until the fix is provided.

I’m a bit concerned because you are not able to open ticket in our Jira, can you share your account name so it can be checked (I don’t see it in your picture)?

Hi @Tomislav_Plavcic

Good to here :slight_smile:

I’ve wrote you a DM

Greetings, balu

1 Like