[jira] [Resolved] (NIFI-11394) If changing flow version and a port is modified and running, will fail to update

["Pierre Villard (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-11394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre Villard resolved NIFI-11394.
-----------------------------------
    Resolution: Feedback Received

Apache NiFi 1.x is no longer maintained and no new release is planned on the 1.x release line. Marking as resolved as part of a cleanup operation. Please open a new one with an updated description if this is still relevant for NiFi 2.x.

> If changing flow version and a port is modified and running, will fail to update
> --------------------------------------------------------------------------------
>
>                 Key: NIFI-11394
>                 URL: https://issues.apache.org/jira/browse/NIFI-11394
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.21.0
>            Reporter: Mark Payne
>            Priority: Major
>
> To replicate:
> Create a Process Group, named Parent
> Within it, create an Input Port, "Input" and connect it to an UpdateAttribute Processor.
> Save this as Version 1
> Then, create a Child PG, "Child". Move the Input Port, the connection, and the UpdateAttribute Processor within the Child. Then, at the Parent level, create a GenerateFlowFile processor and connect it to the Child's Input Port.
> Save this as V2 of the flow.
> Start running the flow at the Parent level.
> Change the flow back to V1.
> It will stop the components and then fail, indicating that it failed while waiting for Processors to stop.
> In the user log, there will be an entry along the lines of:
> {code:java}
> 2023-04-06 16:37:57,898 INFO [NiFi Web Server-27] o.a.n.w.a.c.ResourceNotFoundExceptionMapper org.apache.nifi.web.ResourceNotFoundException: Unable to find processor with id 'fa651d99-e230-3416-95e5-5e5686a9ad41'.. Returning Not Found response.{code}
> The ID listed there is the ID of the Port. The issue appears to be that it is providing the Port ID as the ID of a processor to stop.
> At this point, the flow is stopped (or at least the relevant components are). So a simple work around is attempting the Change Version the second time, which succeeds. The components can be restarted.



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