[NIFI-8182] Nested version control broken by "Single FlowFile Per Node"

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.12.1
• Fix Version/s: 1.13.1
• Component/s: Core Framework
• Assignee: Unassigned
• Reporter: Jens M Kofoed
• Created: 30/Jan/21 08:09
• Updated: 22/Mar/21 10:16
• Resolved: 22/Mar/21 10:16

Description

I have an issue with nested PG where the root PG continuously is showing it
has local changes but it has not.
I have now found why, and how you can reproduce the bug
1. Create an empty Process Group (PG-Root)
2. Add version control to the PG-Root
3. Add an empty PG (PG-Sub) in PG-Root
4. Add version control to PG-Sub
5. Commit changes to PG-Root
6. Check that both PG-Root and PG-Sub are up-to-date with the green check
mark
7. Change "Process Group FlowFile Concurrency" to "Single FlowFile Per
Node" for the PG-Sub
8. Commit changes to PR-Sub
9. Refresh page
10. PG-Sub should have a green check mark, and PG-Root still has local
changes
11. Commit changes to PG-Root
12. PG-Root is still showing it has local changes, but it has not.

Bug is allso created in Nifi registry, as: https://issues.apache.org/jira/browse/NIFIREG-437

Issue Links

• is cloned by: NIFI-8238 Change in a nested, versioned process group's flowfile concurrency / outbound policy results in outer group showing local changes