[NIFI-11028] Handle controller service 'Scheduled State' after upgrade to NiFi 1.16

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.16.0
• Fix Version/s: 1.20.0
• Component/s: NiFi Registry
• Assignee: Zsihovszki Krisztina
• Reporter: Zsihovszki Krisztina
• Created: 06/Jan/23 17:01
• Updated: 17/Jan/23 23:41
• Resolved: 17/Jan/23 23:41

Description

It is not possible to revert local changes on an upgraded flow if the controller services are enabled. The following error is reported: "Cannot modify Controller Service configuration because it is currently enabled. Please disable the Controller Service first."

The "Scheduled State" of a controller service was not stored prior to 1.16.
When NiFi is upgraded from an earlier version to 1.16, the stored "Scheduled State" of  controller services in the flow is "null", while the actual (local) scheduled state is ENABLED/DISABLED (both is mapped to DISABLED at comparison).

When "Revert local changes" is selected, the "Scheduled State" change is noted as a difference between the proposed and currently loaded flow. 

 

Controller Service 10f21a4c-194f-34c2-8cfc-97892f73d3ec has a Scheduled State of null in Proposed Flow but DISABLED in Currently Loaded Flow

Since it's considered a local change, the controller service is not disabled before the flow is synchronized and when synchronization takes place, the "Cannot modify Controller Service configuration because it is currently enabled. Please disable the Controller Service first." occurs.

 

 

Issue Links

• links to: GitHub Pull Request #6831
• links to: Pull Request