Details
-
Type:
Bug
-
Status: New
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 3.29.0, 3.30.0
-
Fix Version/s: None
-
Labels:
-
Notability:3
Description
On NXRM 3.29, orphaned maven-metadata.xml, sha1, md5, sha256 and sha512 files brought over from an upgrade are not removed by cleanup policies.
To reproduce
- On NXRM version pre 3.29, run a gradle deploy to a maven repo with a permissive layout.
- Configure and run a cleanup policy against the maven repo e.g. based on published date and confirm that all files except the sha256 and sha512 files are removed.
- Upgrade the instance to 3.29 and run cleanup policy again.
Expected
Orphaned maven-metadata.xml, sha1, md5, sha256 and sha512 files are removed.
Actual
Orphaned maven-metadata.xml, sha1, md5, sha256 and sha512 files are not removed.
Workaround
Manually delete the orphaned files/directories.
Attachments
Issue Links
- relates
-
NEXUS-29523 Search Assets endpoint only returns assets associated with a component even though it is expected some valid assets will not be directly associated with a component
-
- New
-