[jira] [Created] (NIFI-10973) NiFi Registry Client with Nested PGs - sync issue (again)

["Josef Zahner (Jira)" <ji...@apache.org>]

Josef Zahner created NIFI-10973:
-----------------------------------

             Summary: NiFi Registry Client with Nested PGs - sync issue (again)
                 Key: NIFI-10973
                 URL: https://issues.apache.org/jira/browse/NIFI-10973
             Project: Apache NiFi
          Issue Type: Bug
          Components: NiFi Registry
    Affects Versions: 1.19.1
            Reporter: Josef Zahner
         Attachments: Nested_PG_Test.xml, Sync_issue_State.png, Sync_issue_local_changes.png

We just upgraded to NiFi 1.19.1 and we have an issue with the NiFi Registry Client in combination with nested PGs (parent PG and child PGs are both commited as NiFi Registry flows).

Steps to reproduce the issue (based on the attached template xml):

Hint: {color:#57d9a3}Green Color {color}-> NiFi Registry flow Master; {color:#4c9aff}Blue Color{color} -> Secondary NiFi/Canvas where you import the flow from Registry
 * {color:#57d9a3}Import the XML template{color}
 * {color:#57d9a3}Start Version Control for "Child PG"{color}
 * {color:#57d9a3}Start Version Control for "Parent PG"{color}
 * {color:#4c9aff}On an independent canvas/nifi click "Add Process Group" and "Import from Registry", select the "Parent PG" flow{color}
 * {color:#57d9a3}On the original "Child PG" rename the only existing processor, eg. to "UpdateCounter New"{color}
 * {color:#57d9a3}Commit the change for the "Child PG" (Processor Rename){color}
 * {color:#57d9a3}Commit the change for the "Parent PG" (Version change of "Child PG"){color}
 * {color:#4c9aff}Now click "Change Version" on the other NiFi/Canvas and switch to the newest version for the "Parent PG", which seems to be successful. *However* *now we are hitting the issue, NiFi shows a successful change, but NiFi shows as well "Local Changes" for the "Child PG" (not for the "Parent PG"). To get a good state you have to click to "Revert Local Changes" on the "Child PG" which makes no sense, it should directly sync the "Child PG" according to the commited version. At least the version number of the "Child PG" has been changed but not the real configuration as you see below in the screenshots. It shows that there has been a component name change, which is true for the version but to get to the new version we have to revert the local changes*{color}

 

Screenshots with the Failure State below, "Parent PG" is in sync, but not the "Child PG". The only thing I've done is to change the Version on the "Parent PG":

{color:#4c9aff}*!Sync_issue_State.png!*{color}

 

{color:#4c9aff}*!Sync_issue_local_changes.png!*{color}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)