BackupConfiguration does not work with minikube

[alwinint]

Dear developers,

I am trying my first steps with stash community edition and just wanted to test one backup and one restore, so I tried to modify the tutorial for the Restic server backup to my needs. I therefore used the two attached specs for the Repository and a BackupConfiguration. The Secret for the Repository is installed, and the referenced deployment also exists.

Nevertheless, the deployment is rejected by the Stash pod. This is what I see when I have a look at the configuration:

status: conditions:

• lastTransitionTime: '2020-12-15T15:15:12Z' message: Repository ice-dev/rest-repo exist. reason: RepositoryAvailable status: 'True' type: RepositoryFound
• lastTransitionTime: '2020-12-15T15:15:12Z' message: >- Failed to check whether the backend Secret ice-dev/ exist or not. Reason: resource name may not be empty reason: UnableToCheckBackendSecretAvailability status: Unknown type: BackendSecretFound

And the Stash log matches this as well:

I1215 19:48:22.312717 1 backup_configuration.go:76] Sync/Add/Update for BackupConfiguration deployment-backup E1215 19:48:22.348754 1 worker.go:92] Failed to process key ice-dev/deployment-backup. Reason: resource name may not be empty I1215 19:48:22.348776 1 worker.go:96] Error syncing key ice-dev/deployment-backup: resource name may not be empty I1215 19:48:22.353995 1 backup_configuration.go:76] Sync/Add/Update for BackupConfiguration deployment-backup E1215 19:48:22.372137 1 worker.go:92] Failed to process key ice-dev/deployment-backup. Reason: resource name may not be empty I1215 19:48:22.372157 1 worker.go:96] Error syncing key ice-dev/deployment-backup: resource name may not be empty I1215 19:48:22.382285 1 backup_configuration.go:76] Sync/Add/Update for BackupConfiguration deployment-backup E1215 19:48:22.404851 1 worker.go:92] Failed to process key ice-dev/deployment-backup. Reason: resource name may not be empty I1215 19:48:22.404887 1 worker.go:96] Error syncing key ice-dev/deployment-backup: resource name may not be empty I1215 19:48:22.425320 1 backup_configuration.go:76] Sync/Add/Update for BackupConfiguration deployment-backup E1215 19:48:22.446721 1 worker.go:92] Failed to process key ice-dev/deployment-backup. Reason: resource name may not be empty I1215 19:48:22.446749 1 worker.go:96] Error syncing key ice-dev/deployment-backup: resource name may not be empty I1215 19:48:22.487726 1 backup_configuration.go:76] Sync/Add/Update for BackupConfiguration deployment-backup E1215 19:48:22.518036 1 worker.go:92] Failed to process key ice-dev/deployment-backup. Reason: resource name may not be empty I1215 19:48:22.518064 1 worker.go:96] Error syncing key ice-dev/deployment-backup: resource name may not be empty I1215 19:48:22.598376 1 backup_configuration.go:76] Sync/Add/Update for BackupConfiguration deployment-backup E1215 19:48:22.607795 1 worker.go:92] Failed to process key ice-dev/deployment-backup. Reason: resource name may not be empty E1215 19:48:22.607816 1 worker.go:106] resource name may not be empty I1215 19:48:22.607820 1 worker.go:107] Dropping key "ice-dev/deployment-backup" out of the queue: resource name may not be empty Logs from to UTC

It also looks like this is not a version issue, because I also tried the backup with the newest minikube and kubectl and a simple busybox pod, which showed the same error (the logs are from minikube 1.6.2 and kubernetes 1.16). Can you point out what might be wrong, or is this actually a bug? The spec files are attached.

stash-repository.txt stash-backup-conf.txt

[hossainemruz]

Your Repository is missing storageSecretName field. https://stash.run/docs/v2020.11.17/guides/latest/backends/rest/

[hossainemruz]

Closing for inactivity.