[NIFI-8238] Change in a nested, versioned process group's flowfile concurrency / outbound policy results in outer group showing local changes

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.14.0, 1.13.1
• Assignee: Mark Payne
• Reporter: Mark Payne
• Created: 18/Feb/21 20:34
• Updated: 12/Mar/21 16:42
• Resolved: 19/Feb/21 10:45

Description

As reported on the mailing list:

 
to reproduce this issue:
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. Update 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.

Issue Links

• is a clone of: NIFI-8182 Nested version control broken by "Single FlowFile Per Node"
• is duplicated by: NIFIREG-437 NIFI show version changed *, but versioncontrol show no local changes
• links to: GitHub Pull Request #4831
• links to: GitHub Pull Request #4831