Description
When a user attempts to start version control for a ProcessGroup, NiFi makes two NiFi Registry API requests, one for creating a new Flow, and the other is creating a new snapshot in the registry.
If NiFi Registry returns error for the 2nd request for some reason (e.g. Git repository is used and its local repo is in a dirty state, having uncommitted files), NiFi loses the information about the created versioned Flow, that is returned by the 1st response.
After that happens, if a user retries starting version control for the same ProcessGroup, NiFi sends the 1st request again, to create the Flow in NiFi Registry. Then NiFi Registry returns error response because a Flow with the same name already exists in the bucket.
NiFi should remember the created versioned Flow information in case snapshot creation failure, so that the snapshot can be committed later when the NiFi Registry side issue gets addressed.
Attachments
Issue Links
- blocks
-
NIFIREG-205 NiFi Registry DB gets out of sync with git repository, no apprent remediation
-
- Resolved
-
- links to
