[NIFI-10816] Nested versioning not working after upgrading to 1.18.0

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.18.0
• Assignee: Nathan Gough
• Reporter: Bryan Bende
• Created: 14/Nov/22 15:36
• Updated: 17/Nov/22 18:09
• Resolved: 17/Nov/22 18:09

Description

Reported in Apache NiFi Slack...

 
We have just upgraded to NiFi 1.18 and we have an issue with Nested Process Groups. We are using NiFi registry for versioning.Prior to the upgrade 1.17.0 has produced the following snapshots when versioning PGs. Below is the part that references the nested PG.
json
"versionedFlowCoordinates" : {
"bucketId" : "c0ad0d17-9b50-4dff-8fca-fd6504cfee50",
"flowId" : "8acc6ce2-e425-4b91-a089-b7efc6afed8a",
"registryUrl" : "https:/my-domain:18443",
"version" : 3
}
After the update we concluded that the registryUrl field is not part of the PG in the snapshot.
json
"versionedFlowCoordinates" : {
"bucketId" : "c0ad0d17-9b50-4dff-8fca-fd6504cfee50",
"flowId" : "8acc6ce2-e425-4b91-a089-b7efc6afed8a",
"version" : 4
}
Hence when importing to NiFi we get the following exception:org.apache.nifi.registry.flow.FlowRegistryException: No applicable registry found for storage location null

Issue Links

• relates to: NIFI-10787 Cannot commit flows to nifi registry after updating our nifi release to 1.18.0