Import Job Fails with "No kopia manifests found in the repository"

Import jobs fail with the error:

No kopia manifests found in the repository

Full error:

{
  "cause": {
    "file": "kasten.io/k10/kio/collections/kopia/operations.go:144",
    "function": "kasten.io/k10/kio/collections/kopia.GetLatestSnapshot",
    "linenumber": 144,
    "message": "No kopia manifests found in the repository"
  },
  "file": "kasten.io/k10/kio/exec/phases/phase/migrate.go:359",
  "function": "kasten.io/k10/kio/exec/phases/phase.(*migrateReceivePhase).Run",
  "linenumber": 359,
  "message": "Failed to import latest collection"
}

Currently, the Kopia server user is created based on the name of the Veeam Kasten for Kubernetes namespace. If the secondary cluster where the application is to be imported has Veeam Kasten for Kubernetes installed in a namespace with a different name, then a wrong kopia server user is set, causing the error `No kopia manifests found in the repository`. This means that Veeam Kasten for Kubernetes couldn’t find the data from the export location profile with the current user. 

For example, if the source cluster namespace is kasten-io and the secondary namespace is k10, a different Kopia server user (e.g., k10-admin@migration.k10.export-xxxxxxxxxxxx) is set in the server during the import, causing it to fail with the above error.

However, the correct server user should be the same as a primary cluster (e.g., k10-admin@migration.kasten-io.export-xxxxxxxxxxxx).

The solution is to install Veeam Kasten for Kubernetes with an identical namespace in both source and target clusters with the same version of Veeam Kasten for Kubernetes.

Please refer to the Veeam Kasten for Kubernetes release notes.