Good point Russell, we upgraded NiFi Registry last time in March 2020, since then two new versions came out, that’s correct. We plan to upgrade to NiFi Registry 0.7.0 together with NiFi v.1.12.0.
To be honest, I don’t expect that the issue is on Registry side. But I’m curious what other people think. I’m not even able to troubleshoot the issue… I searched for Jira Bugtickets and found some context related issues which will be fixed on NiFi 1.12.0 (<https://issues.apache.org/jira/browse/NIFI-7536>NIFI-7536 / NIFI-7627). However nothing exactly matched to my issue. Cheers Josef From: Russell Bateman <[email protected]> Reply to: "[email protected]" <[email protected]> Date: Monday, 17 August 2020 at 15:27 To: "[email protected]" <[email protected]> Subject: Re: Change Version not possible due to setting a Parameter Context for a Process Group Forgive me for asking, but I'm curious. NiFi Registry 0.5.0 is fully two versions behind the current one. Wouldn't using the latest be a precursor to sorting out problems? Bugs may have been fixed. Or, is there something good known to be expected from the older Registry that the newest one doesn't offer in terms of migrating from variables to parameters? On 8/17/20 6:04 AM, [email protected]<mailto:[email protected]> wrote: Hi guys We are using NiFi 1.11.4 with NiFi Registry 0.5.0. We are trying to migrate from variables to parameters. As soon as we are adding a “Process Group Parameter Context” to an existing process group and change something else to be able to commit it to the NiFi Registry, it seems that the commit gets corrupt. We can’t pull the new version on the other NiFI cluster, error message is below: «Failed to update flow to new version due to org.apache.nifi.web.util.LifecycleManagementException: Failed to update Flow on all nodes in cluster due to An unexpected error has occurred. Please check the logs for additional details.» [A screenshot of a social media post Description automatically generated] Where can we find the log messages mentioned in the error messages? nifi-app.log shows not more than what the GUI shows. How can we troubleshoot this or is there any known bug? We already added some Parameter Context to other Process Groups in the past (may be in another NiFi Version?), so in general it was working. Thanks in advance, Josef
smime.p7s
Description: S/MIME Cryptographic Signature
