[NIFI-4863] If changing version of flow and new flow has no connection to RPG Port, can get error saying unable to start components

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.0
• Fix Version/s: 1.6.0
• Component/s: Core Framework
• Assignee: Mark Payne
• Reporter: Mark Payne
• Created: 09/Feb/18 15:36
• Updated: 20/Feb/18 13:47
• Resolved: 09/Feb/18 20:46

Description

When we have a Remote Process Group with multiple ports, we push to the flow registry the ports that we have connections for. I have a connection to Port A and save that to the flow registry, then create a connection to Port B. I have RPG transmitting data. Then I revert local changes. This properly reverts the flow but fails to restart components. This is because it is attempting to start Port B, and there are no connections for that Port.

Issue Links

• is duplicated by: NIFI-4891 Nifi flow version control should ignore (unused) remote ports in RPGs
• links to: GitHub Pull Request #2462