Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.29.0, 3.30.0
-
Fix Version/s: 3.30.0
-
Labels:
-
Notability:2
Description
A customer was upgrading from NXRM 2.14.19-01 -> NXRM 3.29.0-02 -
Stack traces were noticed in the NXRM 3 nexus.log during step 8 of 9 ( migrating content ):
2020-12-11 13:09:12,620+0100 ERROR [plan-executor-13-thread-2] admin com.sonatype.nexus.migration.repository.ProcessChangesStep - Failed processing of CREATE ext-thirdparty-maven2-proxy-snapshots:/com/fasterxml/jackson/core/jackson-databind/maven-metadata.xml, will ignore and move on. Missing: {attributes::checksum} sha256
java.lang.IllegalStateException: Missing: {attributes::checksum} sha256
at com.google.common.base.Preconditions.checkState(Preconditions.java:508)
at org.sonatype.nexus.common.collect.AttributesMap.require(AttributesMap.java:211)
at org.sonatype.nexus.common.collect.AttributesMap.require(AttributesMap.java:229)
at org.sonatype.nexus.common.collect.AttributesMap.require(AttributesMap.java:238)
at com.sonatype.nexus.migration.repository.migrators.RepositoryMigratorSupport.getHashCodes(RepositoryMigratorSupport.java:322)
at com.sonatype.nexus.migration.repository.migrators.RepositoryMigratorSupport.getHashCodes(RepositoryMigratorSupport.java:332)
at com.sonatype.nexus.migration.repository.migrators.orient.Maven2RepositoryMigratorSupport.hardLinkContent(Maven2RepositoryMigratorSupport.java:195)
at com.sonatype.nexus.migration.repository.migrators.RepositoryMigratorSupport.ingestContent(RepositoryMigratorSupport.java:174)
at com.sonatype.nexus.migration.repository.migrators.orient.Maven2ProxyRepositoryMigrator.ingestContent(Maven2ProxyRepositoryMigrator.java:63)
at com.sonatype.nexus.migration.repository.migrators.RepositoryMigratorSupport.createOrUpdate(RepositoryMigratorSupport.java:153)
This types of ERROR messages suggest that the referenced content was not successfully migrated into NXRM3. Initial investigation suggests this could be related to changes from NEXUS-25490.
Workaround
Upgrade to a version without this problem - 3.28.1.
Expected
Migrate Maven assets and all their attributes from NXRM 2 successfully even if they lack sha256 checksums.
