Details
-
Bug
-
Resolution: Unresolved
-
Critical
-
3.38.1, 3.40.0
-
None
-
2
-
NXRM Sentinels Sprint 36, NXRM Sentinels Sprint 37, NXRM Sentinels Sprint 38
-
3
Description
When using the attached curl command to create a (proxy) repository via the REST API, the first attempt is successful. However, running the same command a second command will correctly fail (duplicate key) but then leave the internal model in a corrupt state such that the repository list will fail to load and subsequent API attempts to delete the repository will also fail.
Restarting Nxrm seems to solve the problem.
Initial investigation suggests that the error is caused by the querying of the repository (facet) status, which is annotated with a guard. The state seems to be at INITIALIZED rather than STARTED which then causes all subsequent code to fail.
(Tested on H2)
Attachments
Issue Links
- is related to
-
NEXUS-31674 Race condition in repository status change can leave repository stuck in initialized state
-
- Waiting for Second Review
-
- relates
-
NEXUS-33522 REST API to create a repository does not always log failures
-
- New
-
-
NEXUS-35220 Race condition in npm audit can cause an npm group repository to enter invalid state
-
- Closed
-
- mentioned in
-
Page Loading...