Required Feature or Behavior

Oct 13, 2025 by miodeya.com 43 views

Problem Statement

We are currently trying to migrate from a Nexus OSS 3.69.0 with OrientDB datasource to version 3.78.0 with Postgres datasource. We are using a docker-based setup and host various types of artefacts like docker, helm, maven, npm, composer or python. With the help of sonatype documentation, we followed this upgrade path:

Upgrade to 3.70.4
Migration to H2
Upgrade to 3.71.0
Upgrade to 3.78.0
Migration to Postgres

However, after migration to Postgres database, docker push commands fail with the following exception in nexus.log:

org.sonatype.nexus.blobstore.api.BlobStoreException: BlobId: path$nexus-repository-docker/ea1b9200-8702-4a52-abcf-282dfda808cc/0, org.sonatype.nexus.datastore.api.DuplicateKeyException: Duplicate key, Cause: Duplicate key
        at org.sonatype.nexus.blobstore.file.FileBlobStore.doDelete(FileBlobStore.java:601)
        at org.sonatype.nexus.blobstore.BlobStoreSupport.delete(BlobStoreSupport.java:173)
        at org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:39)
        at org.sonatype.nexus.common.stateguard.StateGuard$GuardImpl.run(StateGuard.java:298)
        at org.sonatype.nexus.common.stateguard.GuardedInterceptor.invoke(GuardedInterceptor.java:54)
        at org.sonatype.nexus.repository.docker.internal.Upload.lambda$cleanup$1(Upload.java:155)
        at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1625)
        at java.base/java.util.stream.ReferencePipeline$Head.forEachRemaining(ReferencePipeline.java:762)
        at org.sonatype.nexus.repository.docker.internal.Upload.cleanup(Upload.java:155)

Workaround

We postponed migration to version 3.78.0 until a solution is found. We do not want to use H2-based version because performance issues were reported.

Required Feature or Behavior

Nexus should work correctly after migration to version 3.78.0 and migration to Postgres database.

Analysis of the Issue

The issue seems to be related to the migration of the schema from H2 to Postgres. The error message indicates that there is a duplicate key exception, which suggests that there is a conflict between the existing data in the H2 database and the new schema in the Postgres database.

Possible Causes

Inconsistent Data: The data in the H2 database may not be consistent with the new schema in the Postgres database. This could be due to the fact that the data was not properly migrated or that there were changes made to the schema that were not reflected in the data.
Missing Descriptor: The error message also mentions a missing descriptor for the task with type-id: nexus.blobstore.metrics.migration.task. This suggests that there may be a problem with the configuration of the task or that there is a missing dependency.
Flyway Migration: The error message also mentions a Flyway migration failure. This suggests that there may be a problem with the Flyway migration process or that there are conflicts between the Flyway migrations and the existing data.

Solution

To solve this issue, we need to investigate the possible causes and take the necessary steps to resolve them. Here are some possible solutions:

Re-migrate the Data: We need to re-migrate the data from H2 to Postgres, making sure that the data is consistent with the new schema.
Update the Configuration: We need to update the configuration of the task to include the missing descriptor.
Resolve Flyway Migration Conflicts: We need to resolve any conflicts between the Flyway migrations and the existing data.

Conclusion

In conclusion, the issue of migrating to Postgres database is a complex one that requires a thorough analysis of the possible causes and a careful approach to resolving them. We need to investigate the possible causes, take the necessary steps to resolve them, and test the solution to ensure that it works correctly.

Recommendations

Based on our analysis, we recommend the following:

Re-migrate the Data: We recommend re-migrating the data from H2 to Postgres, making sure that the data is consistent with the new schema.
Update the Configuration: We recommend updating the configuration of the task to include the missing descriptor.
Resolve Flyway Migration Conflicts: We recommend resolving any conflicts between the Flyway migrations and the existing data.

Q: What is the issue when migrating to Postgres database?

A: The issue is that after migration to Postgres database, docker push commands fail with the following exception in nexus.log:

org.sonatype.nexus.blobstore.api.BlobStoreException: BlobId: path$nexus-repository-docker/ea1b9200-8702-4a52-abcf-282dfda808cc/0, org.sonatype.nexus.datastore.api.DuplicateKeyException: Duplicate key, Cause: Duplicate key
        at org.sonatype.nexus.blobstore.file.FileBlobStore.doDelete(FileBlobStore.java:601)
        at org.sonatype.nexus.blobstore.BlobStoreSupport.delete(BlobStoreSupport.java:173)
        at org.sonatype.nexus.common.stateguard.MethodInvocationAction.run(MethodInvocationAction.java:39)
        at org.sonatype.nexus.common.stateguard.StateGuard$GuardImpl.run(StateGuard.java:298)
        at org.sonatype.nexus.common.stateguard.GuardedInterceptor.invoke(GuardedInterceptor.java:54)
        at org.sonatype.nexus.repository.docker.internal.Upload.lambda$cleanup$1(Upload.java:155)
        at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1625)
        at java.base/java.util.stream.ReferencePipeline$Head.forEachRemaining(ReferencePipeline.java:762)
        at org.sonatype.nexus.repository.docker.internal.Upload.cleanup(Upload.java:155)

Q: What are the possible causes of this issue?

A: The possible causes of this issue are:

Inconsistent Data: The data in the H2 database may not be consistent with the new schema in the Postgres database.
Missing Descriptor: The error message also mentions a missing descriptor for the task with type-id: nexus.blobstore.metrics.migration.task.
Flyway Migration: The error message also mentions a Flyway migration failure.

Q: How can we resolve this issue?

A: To resolve this issue, we need to investigate the possible causes and take the necessary steps to resolve them. Here are some possible solutions:

Re-migrate the Data: We need to re-migrate the data from H2 to Postgres, making sure that the data is consistent with the new schema.
Update the Configuration: We need to update the configuration of the task to include the missing descriptor.
Resolve Flyway Migration Conflicts: We need to resolve any conflicts between the Flyway migrations and the existing data.

Q: What are the recommendations for resolving this issue?

A: Based on our analysis, we recommend the following:

Re-migrate the Data: We recommend re-migrating the data from H2 to Postgres, making sure that the data is consistent with the new schema.
Update the Configuration: We recommend updating the configuration of the task to include the missing descriptor.
Resolve Flyway Migration Conflicts: We recommend resolving any conflicts between the Flyway migrations and the existing data.

Q: What are the benefits of resolving this issue?

A: The benefits of resolving this issue are:

Improved Performance: Resolving this issue will improve the performance of Nexus after migration to Postgres database.
Reduced Errors: Resolving this issue will reduce the number of errors that occur after migration to Postgres database.
Increased Reliability: Resolving this issue will increase the reliability of Nexus after migration to Postgres database.

Q: How can we ensure that the issue is resolved?

A: To ensure that the issue is resolved, we need to:

Test the Solution: We need to test the solution to ensure that it works correctly.
Verify the Results: We need to verify the results to ensure that the issue is resolved.
Monitor the System: We need to monitor the system to ensure that the issue does not recur.