Customer ran SHA256 Migration on Artifactory 5.5.1, and the migration completed with errors, and generated a file named: sha2_migration_badFiles-1509834733505.list
Inside, this file contained two artifacts that failed migration:
Paths that failed conversion:
repo:.index/nexus-maven-repository-index.gz --> Repository 'repo' not local, cache or virtual
repo:.index/nexus-maven-repository-index.properties --> Repository 'repo' not local, cache or virtual
After consulting around, these two artifacts are likely system remnants of the cache of the global repo 'repo', where the virtual had contained a maven repository (possibly maven indexer related) with these files, so when repo was deprecated, the artifacts had their path removed, but remained in the filestore, causing issues with the migration.
Arti 3.x, have repo enabled in maven indexer, upgrade to 5.5.1 and enable migration. (TBD)
1) Ensure maven indexer does not have the repository 'repo' under included repositories.
2) Create virtual generic repository named 'repo', restart Artifactory to trigger migration. Migration should complete successfully. Afterwards, delete the virtual repository.